While I don’t see particular problem with this, you do kind of break out of code flow at early point. I would try to go for setting query to is_404 instead and let it reach template processing and 404 in template hierarchy naturally.
Why did you want to alter the URI here? SEO optimization? An URI has a limited number of allowed chars, defined in an RFC. That’s the reason WordPress uses utf8_uri_encode to generate a permalink based on the posttitle. You can find more information in this stackoverflow question: Which characters make a URL invalid? EDIT I’ve … Read more
First check if custom post type + taxonomy archive displaying correct posts by visiting a url structure like this – mysite.com/?post_type=products&products-category=monitors If it’s working then you can do some custom rewrite rules to show them just like you want. Here are some recommended answers on WPSE describing same Mixing custom post type and taxonomy rewrite … Read more
Problem solved. It was because I had the Custom Post Type and the Page name the same, “Portfolio” for both. Once I changed this, I went to Settings > Permalinks and flushed. Re-Saved Links. Then checked all the posts links that was using the CPT, and everything went fine after that. I did use the … Read more
Instead of getting stuff from the database, access the site via its feed. http://example.com/?p=POST-ID&feed=rss2 will give you information about the post, including the permalink (in the <link> tag).
The attachment page generally gets the “title” value as it’s slug. Are you not filling in the image information like title, caption, etc? Might give that a try.
WordPress doesn’t catch all old URLs, you have to help it. Add the following code to your .htaccess above the WordPress rewrite rules: RedirectMatch permanent /\d+/\d+/\d+/(.+)$ /?pagename=$1
Try updating your permalinks in the backend under Settings -> Permalinks. Be sure to “Save Changes” even if you don’t make any changes. It seems to refresh the permalinks. Also verify the “slug” is set properly when you’re setting up your post type.
Your setup is all over the place. Lets refer to the visual overview here: http://codex.wordpress.org/Template_Hierarchy#Visual_Overview Your page is going to use the page.php template. Your custom post type weine will use single-weine.php Your custom taxonomy sorte ( probably not the best name as it might clash ) will use the template taxonomy-sorte.php So we can … Read more
Because it is looking for the page 404, which is a child of the page /error. Try just doing this: function show_404($message=”page not found”){ wp_redirect(home_url() . ‘/error?m=’ . urlencode($message)); exit(); } But your doing it wrong. You should just use WordPress’s internal 404 page, it will save a lot more headaches that will arise in … Read more