Moderator
t-p
(@t-p)
To troubleshoot if it’s caused by an active plugin or the current theme, try:
– deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
– switching to the unedited default Theme (Twenty Seventeen.) for a moment using the WP dashboard to rule out any theme-specific issue (theme functions can interfere like plugins).
-
This reply was modified 8 years, 9 months ago by
t-p.
Thread Starter
valsc
(@valsc)
I will try that, thanks, the odd thing is nothing has changed since the site went live, and it just started happening. I will try those troubleshooting steps though, just in case something got updated that I don’t know about.
If I switch themes and then go back will everything stay the same? I am not the person who created the site, but I maintain it, but if I mess anything up by changing themes and going back I can’t get what I messed up fixed.
Thanks!
-
This reply was modified 8 years, 9 months ago by
valsc.
Check the log files for errors. It will help you diagnose the problem and you can either fix the problem yourself or contact someone knowledgeable to help you.
If I switch themes and then go back will everything stay the same?
True!
Do you see any error in Chrome Developer Tools -> Console?
Also, are you able to turn on debugging temporary and copy/paste error message (if any) here?
To turn debugging on, you should edit your wp-config.php file in your root directory:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
You can try with setting WP_DEBUG_DISPLAY to true and your error message will be shown on blank page (the page that you have issues with) or, if your site is in production, you should set WP_DEBUG_LOG to true and check the log in /wp-content/debug.log
Thread Starter
valsc
(@valsc)
So it looks like it is with the theme, which they have discontinued and no longer provide support for lol…
Warning: fopen(./.ips1.txt): failed to open stream: Permission denied in C:\inetpub\wwwroot\cavaweb\wp-content\themes\hetica\hetica\footer.php on line 2
Warning: fopen(/var/tmp/.ips1.txt): failed to open stream: No such file or directory in C:\inetpub\wwwroot\cavaweb\wp-content\themes\hetica\hetica\footer.php on line 2
Warning: fopen(.SIc7CYwgY): failed to open stream: No such file or directory in C:\inetpub\wwwroot\cavaweb\wp-content\themes\hetica\hetica\footer.php on line 18
Warning: fopen(/var/tmp/.SIc7CYwgY): failed to open stream: No such file or directory in C:\inetpub\wwwroot\cavaweb\wp-content\themes\hetica\hetica\footer.php on line 18
—
I don’t have the problem in Chrome, so I don’t get these errors in Chrome when I go to the site. My Co-worker does have an extra popup in Chrome, and I checked her computer, and she does have those errors on the page when she gets the pop up.
So would that be the cause of the extra blank page? — it should be noted that I believe the person who set up the site is using the template\footer.php and not the hetica\footer.php – I am checking with him on this, but I’m pretty sure this is the case.
I had someone from spiceworks take a look and he said he found
Could not locate http://www.cava.cc/wp-content/themes/hetica/hetica/assets/css/style.sass specified in source map http://www.cava.cc/wp-content/themes/hetica/hetica/assets/css/style.css.map.
So I’m not sure if that might be the problem as well.
Thanks!!
-
This reply was modified 8 years, 9 months ago by
valsc.
Thread Starter
valsc
(@valsc)
What I did was copy the footer.php from the location that we use, and put it in the location that we do not, where this error came from, and it seems to have fixed the problem.
I’d prefer to find the reference that point to the wrong path and fix that, but for now this does work.
Thanks for the help, I was able to solve the problem because of it!!!