I have it working now. The file, ivevents.js, has an error in it. Rather than the console identifying the error, it gives the 404 error, as if the file doesn’t exist. When I corrected the error in the js file, the console error goes away. Now, if I could only figure out how to use … Read more
Here is the answer I was looking for. Staring me right in the face. I have managed to fix this issue with a simple addition to the code. &value_field=slug So final code which works and maybe of help in the future. <form action=”<?php bloginfo(‘url’); ?>/” method=”get”> <label for=””>Search.</label> <?php $select = wp_dropdown_categories( ‘taxonomy=YOURTAXONOMY &name=YOURTAXONOMY &show_option_all=Please … Read more
You need to enable the error logging in WordPress from the wp-config.php define( ‘WP_DEBUG_LOG’, true ); After that, you will probably get some feedback inside: wp-content/debug.log Above that, you can try to get the exact feedback you get from 404 page. Check the console in the inspector, and the response from te webserver. curl -I … Read more
Are you using pretty permalinks? If so try to go to wp-admin > Settings > Permalinks and press the ‘Save Settings’ button. The second form URL is only used when you dont have the Url rewriting enabled. But that is not recommend for SEO.
As @Milo said, I’d suspect the folks at your hosting place. You might also look in your hosting ‘cpanel’ for the ‘404’ settings.
Sometimes pagination will break and give unexpected results, redirect you to the wrong page or give you a 404 (page not found) on the “paged” pages. This is usually due to your theme altering (querying) the main loop wrong. Try updating your .htaccess file by updating the permalink.
your .htaccess likely wasn’t inited. You can go into your settings/permalinks and hit save and this will flush the settings for you and it should work.
404 error next-page [2] PageNavi custom type taxonomy
Numbers work because single posts can have pagination, and there is a rewrite rule to support that. If you want to add an additional parameter after a permalink, add a rewrite endpoint. add_rewrite_endpoint( ‘show’, EP_PERMALINK ); EDIT- Here’s an internal rewrite example, assuming your custom post type slug is type1: add_rewrite_rule( ‘c/([^/]+)/([^/]+)/([^/]+)/?$’, ‘index.php?type1=$matches[1]&type2=$matches[3]’, ‘top’ );
WordPress .htaccess should fix this. It checks wether the file exists before doing any redirects. Are you sure your installation is correct?