I'm using wordpress 3.4 and i just register a custom post type and taxonomies for it and its working fine but the problem is sometimes some pages shows blank including front-end and back-end
Blank pages are usually caused by PHP errors. Something makes WordPress to crash, and if error display is disabled on your server, all you get is a blank page.
Check your PHP error log for any recent messages. They should point you to the file that contains the problematic code. Usually it will either be a buggy plugin or theme. Alternatively, the error might be caused by WordPress running out of memory. If it's a plugin or theme, you can fix the problem by deactivating it. If it's an "out of memory" error, increase the PHP memory limit.
See also:
3 Ways to Monitor PHP Errors in WordPress
Error Log Monitor plugin
Increasing memory allocated to PHP
Related
I am getting a "response is not a valid json response" error when trying to save Block widgets. I have tried everything I can think of; reset permalinks, deactivated all plugins, reset to a default theme (TwentyTwenty-One), and deleted all widgets, but get the same
{"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}
error when checking in Inspect. Tried in Edge and Chrome.
Using Ubuntu 20.04 and PHP 7.4.3 with WP 6.0, although it was happening in previous WP versions. Nothing unusual in wp-config.php, and nothing in sites-enabled that I can see. I do have multiple wordpress instances (3 total) running on the server.
Saving a post in the block editor works fine, it's only in trying to save widgets.
It's either something in the database(s), or something in Nginx, probably, but I'm hitting a wall. Any suggestions?
I took up my hard drive space but it didn't work And that I also upgraded the php version but it didn't work
Common Reason: Not Enough Memory Allocated
Sometimes, this error message is received because of a memory limit issue. The memory limit has to be set to at least 128MB according to elementor requirements. To be sure that this is a memory issue, you can ask your hosting company to send you the PHP error logs of your server.
How To Troubleshoot a 500 Error
As mentioned above, the first step in troubleshooting is to see what issue is shown in the PHP error logs. If the logs don’t give you precise clues, you can try this troubleshooting technique next: Deactivate your plugins (besides Elementor and Elementor Pro) and switch to a default theme of WordPress such as Twenty Nineteen to rule out a conflict with a third-party product.
Why 500 Internal Error Comes ?
500 Server Error Comes when memory limits of the site are less than 128MB or sometimes because of Plugins Conflicts, So for that be sure about that memory limit should not be less than 128MB as per elementor prerequisites (Memory Limit: Greater than 128MB & 256MB is preferred) and PHP should have the latest version(7 or Greater).
How Can you Resolve Error
As an Error Occurs so the changes made will not get updated, for that firstly Save your changes in the template or the draft format then
Reload the page and try to update.
Go to your PHP version and upgrade it to the latest after that in all options change your memory limit if it is less than 128MB. Then reload your elementor page update the changes that you've saved earlier.
If still error is showing then deactivate your all plugins besides elementor and reload the page or Contact Server provider Support regarding the issue to resolve.
I have a WordPress site and now for some reason it no longer allows me to make changes via the admin backend. I just have this blank GUI, none of which make any change if you click on them
I just added a plugin called Monster insights to align the site with google analytics and since then I get this result. I have tried to rename the plugins folder to manually remove them out of the equation and still no luck. I have reviewed the Log file with little luck as well.
[04-Jun-2019 08:57:05 UTC] PHP Fatal error: Call to undefined function wp_is_recovery_mode() in /home/erwinb411/public_html/wp-admin/includes/update.php on line 840
[04-Jun-2019 08:18:10 UTC] PHP Warning: include_once(): Failed opening '/home/erwinb411/public_html/wp-content/themes/theme52521/includes/register-plugins.php' for inclusion (include_path='.:/opt/alt/php56/usr/share/pear:/opt/alt/php56/usr/share/php') in
i think is a problem of plugin's compatibility in your site.
Have you try to update wordpress core, plugin and theme?
if after update all you have the same problem is an compatibility issue.
Let me know.
I just moved a Wordpress site from one URL to the other. The website itself seems to work fine except when I try to login via /wp-admin I get the following error:
Fatal error: Allowed memory size of 100663296 bytes exhausted (tried
to allocate 122880 bytes) in
/home/deb52080/domains/r2blog.nl/public_html/wp-admin/includes/media.php
on line 2840
I allready run some tests by disabling a plugin and that seemed to have solved the problem (except that I need this plugin and I use it all the time). But the moment I clicked one a function from any other plugin I get the same error.
Hope somebody is able to help me. These are plugins that I use regularly (Smart Slider 3 and Fusion Builder from the Avada thema) and they never give any problem.
Did you happen to move your new site to Siteground as the host? There is a known conflict between the Avada theme and Siteground.
The suggested workaround is to simply go to the Avada menu in the admin panel, choose Register and then remove your API key and save it as blank. Be warned that doing so will eliminate the automatic theme updates Avada provides.
If that doesn't work this thread from the Avada community site provides some solutions on how to increase your memory limit in the wp-config file:
https://theme-fusion.com/forums/topic/fatal-error-allowed-memory-size-of-805306368-bytes-exhausted-tried-to-allocate/
I have setup the AMP plugin in WordPress but while going to see the AMP pages (Appearence->AMP), I saw an error "Non-existent changeset UUID".
Also there is message in console says,
"Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://test.com') does not match the recipient window's origin ('https://test.ve.staging.wpengine.com')."
Please help me to resolved it out.
I've recently taken over administration of a website that has historically been ... poorly managed, and upon trying to use WordPress' built in theme customizer, I was greeted with the same message: "Non-existent changeset UUID.", although I didn't get any related messages in the console.
Apparently my issue was caused by the fact that one of the people who set up the site to begin with had decided to put the public site at www.example.com and the WordPress admin pages at example.com/__wp.
If this is your issue, you basically have two options.
Make sure to log in at both domains.
This may be a little difficult since WordPress' login page is part of the admin portion of the site and thus only logs you in to the admin portion of the site, however this proved to be a good temporary solution for me as there was a plugin installed which added a login widget on the public portion of the site.
Change the WordPress Address to be on the same domain as your Site Address.
The Option appears under Settings > General, but in my case I couldn't change the WordPress Address setting there and had to go into the WordPress database in our company's MySQL server.
After dealing with the above issues, I discovered that this issue had also caused a bunch of resources to be incorrectly loaded from example.com that should have been loading from www.example.com, as well as a number of leftovers from the site's development that were causing some resources not to load because the database thought they were at localhost.
With the help of another Stack Overflow answer I found a Database Search and Replace Script in PHP by interconnect/it (also available on GitHub) which allowed me to repair the mess previous people had made of the website without making a new mess with incorrectly serialized data, or all of the work of manually, correctly serializing the data I needed to change.