Your permalink structure is global; it is not a property of individual posts. There is no way to indicate that one post uses a certain permalink structure while another uses a different one. This makes sense when you think about how WordPress processes requests. Using the new structure, WordPress maps the request to index.php?name=$1 where … Read more
There are a number of ways to do this, Install WordPress on new host, export, then import post data (via Dashboard) XML file Install WordPress on new host, export, then import MySQL database file Use a back up plugin that allows you to clone your site from host-to-host (1:1) In both cases 1 and 2, … Read more
Try using the following for your rewrite rules: location / { try_files $uri $uri/ /index.php$is_args$args; } Using that schema, you can manually remove index.php from your Permalinks settings without breaking anything. Nginx will now check any URI for its existence as a file on the filesystem, and then a directory on the filesystem, and if … Read more
WordPress doesn’t know that you want the path /searchmyblog/ as search result base. So when it sees the a it tries to find the best match – in your case a post starting with this letter. To fix that you could modify my code for the pagination base to change the search base: if ( … Read more
It’s not your permalink settings, it’s the fact that foo.jpg was uploaded first and “stole” the slug foo – you need to change it to something else, then set your page slug. Go to Media > foo.jpg > Edit (if you are in grid view, you need to go to “Edit more details”) From this … Read more
Have you tried something simple to ensure it is actually rewriting? Something like… RewriteEngine On RewriteRule ^.*$ verified.php Then create a verified.php page… <?php print ‘mod_rewrite works!’; ?> Now you should hit that page no matter where you try to go on the site. If you don’t mod_rewrite isn’t working. You can also turn on … Read more
From the top of my head, yes. URL has to uniquely identify target post (or set of posts) to load. One of the (often annoying) issues is that as result WordPress treats hierarchical and non–hierarchical post types differently. In a nutshell hierarchical posts are identified by the whole path in URL, not just their individual … Read more
If you want to remove the index.php from your URL structure, then using this rewrite rule (assuming you’re using Apache, from your question) in your .htaccess will help. # BEGIN WordPress RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress Then, flush permalinks by either using WP-CLI … Read more
First of all there isn’t any default way of doing this as far as I’m aware. If you use the ‘Rewrite rule inspector plugin‘ you’ll see that there isn’t any default rule that combines the category, the date and the feed as parameters. An example date rule is ([0-9]{4})/([0-9]{1,2})/?$ index.php?year=$matches[1]&monthnum=$matches[2] and an example category rule … Read more
It depends on what you’re talking about. If you’re talking about using just <a href=”https://wordpress.stackexchange.com/page-title”>Page Title</a>, then no. It’s better to use the full link. However, instead of using http://www.domain.com/page-title, it’s better to use <?php echo bloginfo(‘url’); ?>/page-title. The reason you don’t want to use relative links is the way wordpress permalinks work. If you’re … Read more