Looks like you have 2 WordPress installations. One for the main site, other for the Blog. http://parlourdc.com/wp-content/plugins/akismet/readme.txt http://parlourdc.com/blog/wp-content/plugins/akismet/readme.txt If that’s not on purpose, you have a blog folder in your site root that should be renamed/deleted as it contains a blank WordPress. If you made a page on your main site titled Blog (and with … Read more
Turn off all plugins. Switch to TwentyTen. Then install the debug bar and helpers. Then switch back to custom theme – reload. Turn one plugin on – reload, next plugin – reload, etc.
Could be a problem with your .htaccess. Check the permalink settings, change to something else and hit save. If there is an error, there’s your problem. It could also be with the theme. Try out another theme (such as the default) to see if any error appears.
I figured it out. Turns out that using the field name was the culprit. It appears that name and other field names like attachment, attachment_id, etc will cause WordPress to produce a 404 error. There’s a whole list of reserved terms in the Codex.
One way to do this is to use the status_header filter. Adding the following to the functions.php file or your theme (or an appropriate plugin file) would do the trick: add_filter( ‘status_header’, ‘your_status_header_function’, 10, 2 ); /** * Substitutes a 202 Accepted header for 404s. * * @param string $status_header The complete status header string … Read more
The $post global is not set on 404 pages, which leads to the error you are getting. You can either check if $post is set or bail if the current page is a 404 page or do all of the above EXAMPLE /** * enqueue scripts used in frontend * */ function sama_enqueue_scripts() { global … Read more
The problem, as pointed out in the php error, is on line 7 of the “chat.php” file: add_action( ‘init’, ic_show_chat_bar()); This line has two problems: The correct syntax for a valid callback function should be without the parenthesis and wrapped in single quotes. Since the function is declared inside a php class, it won’t be … Read more
I think you are misusing shutdown hook. WP attaches it to use with register_shutdown_function() and it’s meant to process end of script execution, not log/process errors. If you want to handle errors in a custom way you are better off using generic PHP set_error_handler() which is meant for that.
As described in this SO answer – https://stackoverflow.com/questions/8028957/how-to-fix-headers-already-sent-error-in-php whitespace before the opening <?php tag of a file can cause a “headers already sent error”. In particular, if the error message is indicating the problem is on line one of the file, this can point to leading whitespace before the first <?php tag (mentioned in point … Read more
So the issue in this case was that PHP wasn’t displaying correct UTC Time. Thanks to @TomJNowell for pointing me in the right way. It seems to be a bug/error in some Plesk installation: https://talk.plesk.com/threads/utc-time-issue-plesk-php-7-3-7-4-on-centos7.356169/ To solve the issue we have replaced the UTC file usr/share/zoneinfo/UTC with another copy from another server. After that, UTC … Read more