I have a custom theme that worked over months, now for some reasons without any update it shows blank pages on all website even with WP_debug active and php display error it doesnt shows any error, now to debug the problem?
If you can access the backend:
Switch to any of the WP default themes and check if you still have the issue.
then deactivate all plugins and check for issues.
then activate plugin 1 by 1 and check for issues (activate the base plugin first then it's the add-on/dependent plugin)
if all these don't work, replace core files from FTP
at last contact a developer ask him to debug the issue
If you can't access the backend:
hire/contact a developer for debugging or ask hosting for help in this case.
Related
On the Wordpress dashboard under Woocommerce > Settings > Advanced there are normally fields where you can link a page to a function (Cart, Checkout, My Account etc.)
For some reason mine have disappeared and all my old links now return a 404.
See what I mean?
I can't find an answer anywhere on the web and I've tried everything I can think of. Anyone had a similar issue?
The issue seemed to appear after installing one of these plugins:
Woocommerce Upload My File
Easy File Upload
I have deactivated both but the issue persists.
I've tried:
Other browsers
De/Reactivating Woocommerce
Restarting the Web Server
Is it possible for plugins to make modifications that remain even after they are deactivated?
Please help!
Edit: I've isolated it to being an error in the database. I exported my site with WP All-In-One Migration Tool and exported everything besides the database. Does anybody know which database entries relate to woocommerce settings?
I am using WooCommerce in conjunction with the Ark theme (a third-party theme) on our WordPress website. Things were working perfectly up until the last week or so when I noticed the issue of the checkout page being rendered as a blank page.
This error can be replicated through these series of steps:
Navigate to the store
Add any item(s) to the basket
When you've added an item from the storefront, you then hover over the basket icon in the header and click Checkout.
If you chose to view the basket instead when adding an item, just scroll down and click Proceed to Checkout.
After chatting with my server provider, it was brought to my attention that some PHP errors were being thrown up. Here is an example of the errors in question.
It seems like there is a plugin conflict with Fresh Framework (a plugin required by the theme to work as intended). Disabling this particular plugin shows the checkout page fine, albeit with much of the styling of the website gone (which is not how I want things).
I have contacted both WooCommerce and the theme's developers for assistance. The former unwilling to help due to the use of a third party theme. The latter being particular slow in responding to my queries.
The theme and all plugins are up-to-date. I did notice the issue upon applying some updates to certain plugins but not the ones in question (WooCommerce/Fresh Framework). Additionally, bringing up the browser's developer console does show a JQuery error (Uncaught Error: Syntax error, unrecognized expression:...) which I believe is related to the issue.
Any type of assistance would be greatly appreciated as the critical error is occurring on a live website and it is particularly crippling our chances of doing business.
At a first glimpse it s most probable that the plugin (fresh-framework) was recently updated...
Deactivating removes its functions,
enabling it includes the functions but breaks the page
Suggest to check the plugin's history and restore to a previous version.
If that's not possible you probably have to wait until they get the error fixed (or try to fix it yourself)
But as you see most probably the problem comes frm the fresh-framework update
PD: PHP Notice are not errors, the errors are only PHP Warning & PHP Error
As you see from the PHP warnings it seems that there is a problem with the filepath where it's trying to write
freshizer.php line 248
you can temporary check which path it tries to write to by adding a wordpress log message or echoing the path....
I have a WordPress multisite build with 9 different themes running. Everything is working okay, I've used Redux Framework on most of them but I'm not able to use the native WordPress customizer, I receive the generic, "Cheatin’ uh? Sorry, you are not allowed to customize this site." error. I am a super admin so I don't believe it's a permissions issue. I'm not able to use the customizer on any of the sites, so I'm thinking it's a core issue but I'm not sure where to look. Any suggestions would be greatly appreciated.
Many people have same issue after update to WordPress 4.7x.
I see someone fixed this issue using this method:
install the plug-in [User Role Editor][1]
go to Users->User Role Editor
select Role: Administrator at the top
check the row edit_theme_options
click on Update
confirm the message box
I uploaded a child theme to my wordpress site and activated it and it's completely broken my site now. Every time I try to go to the site (on Google Chrome) I get the message that "It's now working and is currently unable to handle this request." and also the error is "http error 500" is there any way to fix this? On Safari it just shows a blank white page, nothing else. I'm really nervous that I won't be able to access my site anymore which would be detrimental. I really really really need to be able to fix this.
Try renaming the child themes folder to gain access the /wp-admin. If you are still seeing a message that something is working then make sure the .maintenance file is removed from the root of the website. As another option to access the wp-admin you can login to the database and edit the wp_options table which will have two rows for the theme. These 2 rows will currently have the name of the child theme, switching this back to the parent theme name should revert the change that you made.
Once you have successfully re-enabled the parent theme then you will want to make sure that you created the child theme properly and figure out which core theme files were edited to cause the child theme activation to break the site. You could also enable php error reporting from within a php.ini and/or the wp-config.php file currently so you can get a more detailed error to troubleshoot the cause of the issue.
I'm trying to activate a Wordpress theme but all I got is a blank page, also the admin page goes blank.
Version of WP is 3.9.1, Mysql 5.1 compatible and PHP 5.2.4 compatible too with WP. The theme in question is MH Magazine and I have it in another server with the same configuration and is working ok.
Even I tried to do a backup of the working site and place it in the production server and still goes blank.
I tried uploading the max_memory_limit in php and no luck. Error log and show php errors doesnt show anything, when I check only says the site name HTTP 1.1 500 - If I set wp_debug to true says HTTP 1.1 200.
File permissions are ok too.
A SIMPLE FIX FOR NON TECHIES (Like me really)
Loads of forums recommend various code changes and things to try, non of which worked, so I logically worked through the process more simply and solved it myself (in my case). White screen for everything, including front end and Admin. I tried everything going!
Essentially I'd asked Wordpress to link to a theme, which it did, but now I can't change it back. As it wouldn't automatically switch back to default themes, as suggested by others as a result of simply deleting the theme folder via ftp, I would have to force that myself. Without access to the admin panel, how would I change the link (easily)?. Well I can't, so instead I need to force the change of what it links to instead!
In the end I basically logged in via FTP, went to the wp-content folder, then to themes, located my list of theme folders and changed the theme folder name of the one recently selected and causing the issue, by just adding an x at the end (random letter). Then I changed the theme folder 'default' to the name of the theme which was causing the issue, then refreshed my site in the other window, at which point it displayed again. So the hard coded link never changed, but the basic files it links to now have.
The site was now back up, thank god! I then logged into the Wordpress admin panel and updated my version of Wordpress, as to be honest it had been a while and it was a little out of date, so a likely culprit for the cause of the error. Once updated, I then went back into the FTP window, renamed the folder back to 'default', and then removed the 'x' character from the end of the actual theme folder that I wanted to use. And ta dah, it now works beautifully with the theme I wanted! Without any fancy code changes or messing around with reinstalling or removing etc. BOSH!!
Hope this helps a few people out. (obviously it's different strokes for different folks)
To get this out of comments --- this is a community wiki answer.
Are your two servers running on the same platform (Linux? Win?) or different ones?
Do you have the same collection of plugins on both platforms?
Here are some things to try.
do View Source on your white screen of death and see if there's anything in the source view that can help you diagnose your problem.
deactivate all your plugins, then try the theme.
if it doesn't work, then this theme is broken on this server setup.
reactivate the plugins one by one. One of them will probably give you the white screen of death. Then you know that plugin is incompatible with that theme.