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.
Check to make sure your .htaccess file (in the root) is writable by WordPress, if it isn’t then you may need to manually set this up to get the permalinks working correctly.
Headers are sent long before you try to alter them. Headers are sent by actions associated with get_header(), so by the time your code executes, it is too late to alter the headers. You can demonstrate this with a simple experiment. Try each of the following: get_header(); status_header( 404 ); and status_header( 404 ); get_header(); … Read more
You don’t need to add anything special to the top of 404.php. WordPress will know to use 404.php automatically when it tries to get a post or page and fails. To create a custom 404 page for a theme, the simplest way is to: Copy the index.php file from the current theme to a file … Read more