Mmmm, I think that if you are thinking on a major change for the project, you could proceed as follow: Of course, create a development snapshot of your site, somewhere else. Fork files and database, You can even fool the development vhost and the developer client so you dont even need to change the url-related … Read more
If you can log into your host with SSH or FTP, it’s an easy fix. Like the comments said before, check your permissions for the WordPress directory. For example, if you check the hosting directory with ls -al (typically /var/www, as on DigitalOcean), they should look something like this: drwxrwxr-x 6 www-data www-data 4096 Nov … Read more
Read User Access paragraph on the Codex here: Multisite Network Administration
When you look at the source code, the tag template is loaded as follow in template hierarchy elseif ( is_tag() && $template = get_tag_template() ) : in wp-includes/template-loader.php get_tag_template() uses get_query_template() which uses locate_template() which loads the tag template according to hierarchy from the theme root folder So, moving your templates to a sub-folder will … Read more
You may want to look at the TwentySixteen theme, which does it this way: In single.php: get_template_part( ‘template-parts/content’, ‘single’ ); Several templates are grouped in the ‘template-parts’ folder. You could use a similar logic for your custom post type. It seems that the technique comes from _underscores.
Yes, you can do that. It won’t affect any of the installation. I have already done this for few sites. Works without issue.
Standard file/folder permission for WordPress: 755 for folders 644 for files
Short answer is no. WordPress defines plugin paths allowing plugins authors to use plugin content functions to locate their files, and these are controlled by the WordPress content constants which are set in the file wp-includes/default-constants.php However, although the path are customisable, WordPress only searches this one location. The only exception to this is network … Read more
The $1 is grabbing the value from (.*)$, so to remove the subcategory, you’ll need to remove the flag RewriteRule ^category/symptoms/(.*)$ https://my-site/com/list/ [L,R=301]
The file needs a template header and will only behave as a user-selectable custom page template. True special templates like page-$slug.php that match the post’s slug will only work when they live in the root theme directory.