That’s not what’s happening, when you visit /contacts–/ it doesn’t return a 200 code, but instead it returns a 301 redirect code. The browser then follows this redirect and heads to /contact and it’s /contact that returns 200 code. This is because /contact is the canonical URL of that page, and WordPress redirects to canonical … Read more
After doing some research I found the reason causing this. Before I moved the client’s website to its domain, they had their previous website in the old server. As we started using the new website, we started using another server. It seems that the previous website used Google’s Service Worker. My browser (and some others’ … Read more
Try using the pre_handle_404 hook instead: add_filter( ‘pre_handle_404’, ‘wpse_383506’, 10, 2 ); function wpse_383506( $preempt, $wp_query ) { if ( ! empty( $_GET[‘page_id’] ) && ‘342’ === $_GET[‘page_id’] ) { // Throw a 404 error. $wp_query->set_404(); // And prevent redirect to the page permalink (pretty URL). remove_action( ‘template_redirect’, ‘redirect_canonical’ ); } return $preempt; // always … Read more
You don’t appear to have allowed .htaccess overrides in the <VirtualHost *:443> container, so .htaccess is effectively disabled. Without .htaccess you’ll naturally get 404s for anything other than the homepage if you are using “pretty” permalinks. (.htaccess is not required for requests to the homepage, since index.php is served by mod_dir which is no doubt … Read more
Turns out this was being caused by a Chrome browser extension. I use an extension installed called “CrxMouse Chrome Gestures.” This extension is the cause of this error. I have turned off the extension and notified the author of this bug.
Save your existing .htaccess file by renaming it to backup.htaccess & then re-save your permalinks which will create a new .htaccess file. That solves issues most of the time.
what have you set the “has_archive” option to in your CPT? Also, make sure to reset your permalinks. As for putting a customized message, you can create an archive template specific to that CPT. If the CPT is “portfolio”, then you can create a template called “archive-portfolio.php” and customize it as you see fit.
You’re probably using an input field that contains name=”name”. A lot of generic words are used by WordPress itself (incl. name, so a best practise is to always prefix_ your fields, like name=”prefix_name”.
You can use the following code to dump the HTTP Api response, will help you figure out the cause of error. function dump_http_api_response($response, $type=””, $transport=null ) { if ( $type == “response” ) var_dump ( $response ); } add_action(‘http_api_debug’, ‘dump_http_api_response’, 1, 3); Example Output: object(WP_Error)#15 (2) { [“errors”]=> array(1) { [“http_request_failed”]=> array(1) { [0]=> string(41) … Read more
What it does: It offers an action handler, a moment in run time to execute other functions. So it is a hook for plugins and core functions. Removing all hooked functions or changing the core file will break WordPress. If your plugin fails to work with it – fix the plugin.