To understand why 404 erros occur with pagination, you have to first understand the process WordPress follows when a page is requested. The query is parsed and the results are queried from the database before the template is loaded. When you create a new query in the template, these results are unrelated to the original … Read more
When you add a custom post type, WordPress doesn’t know that it needs to regenerate it’s permalinks/rewrite rules. Visit the permalinks settings page to flush and regenerate the links and your custom post type permalinks will start to work, else you’ll get 404 messages. A word of warning: Some people will advise you call flush_rewrite_rules … Read more
I had the same issue and found a solution. From what I learned so far, there might be two causes to this problem: WP doesn’t recognize your rewrite rules because they are not cached yet. You can check this by dumping get_option( ‘rewrite_rules’ ); and if your rules did get cached, then they’ll be in … Read more
It sounds like you need to copy the file /blog/index.php to /index.php and modify a line in the new copy you create: require(‘./wp-blog-header.php’); to require(‘./wordpress/wp-blog-header.php’); Here is a complete guide to moving WordPress into a separate folder: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
If in your template you create a 404.php all not-found requests will be handled by this template file, and there you can put whatever you want. Just as example, in the 404.php file is possible to use something like (it’s just a draft): <?php get_header(); ?> <h3> <?php $slug = get_query_var(‘name’); if ( $slug ) … Read more
If you look in the database in the $wpdb->postmeta table you will see a meta_key named _wp_old_slug. That is how WordPress tracks slug changes. By editing the database directly you bypassed the mechanisms that create that postmeta entry. You never want to edit the database directly if you can use WordPress Core functions instead. Attempting … Read more
change input name for name field to contactName or cName etc. <input type=”text” name=”cName” id=”name” placeholder=”Your name” autocomplete=”off” tabindex=”1″ class=”txtinput” value=””/>
I am about 99% sure the reason for much of this is that someone has used relative links in the post body. A link that looks like this: <a href=”www.whufc.com/”>Some link Test</a> Will end up looking like this: 2010/premiership-forecast-title-race-hots-up-gunners-prepare-for-adebayor/www.whufc.com/ If it shows up on this page of the site: 2010/premiership-forecast-title-race-hots-up-gunners-prepare-for-adebayor/ You need to have the … Read more
some time it’s most likely the permalink structure is missing or something went wrong after migration from localhost to live server, the solution is reflush permalink rules to avoid 404 errors.
The domain didn’t have www. in the wordpress settings. Adding this worked. No idea what the problem was exactly, but this solved it. Edit: Not yet fixed. It was mod_security which blocked ‘WordPress.com.’ (I’m at Namecheap which uses mod_security)