Docs

[karenhaid]

Hello,
I just noticed that when I clicked on a category on my blog page, it leads to a blank, white screen. I think this used to work, but I did do an update recently.
My blog: http://www.CalabriaTheOtherItaly.com/blog/
I’m using WordPress 4.5 running X – Child Theme: Integrity Light theme.
Thank you for your assistance,
Karen

[Darshana]

Hi there,

Thanks for writing in! First you can try regenerating your permalinks structure by head over to Settings > Permalinks and then save the changes by selecting your desired configurations.

If that doesn’t resolve your issue, you can enable WP_DEBUG mode to see any issues. You can do this by opening <strong>wp-config.php</strong> in the root of your WordPress installation folder and adding
define( 'WP_DEBUG' , true ); just above /* That's all, stop editing! Happy blogging. */ For example:

define('WP_DEBUG', true);

/* That's all, stop editing! Happy blogging. */

When you revisit the page with the white screen, you should have some error output describing the issue in more detail.

Let us know how it goes.

[karenhaid]

Hi,

I followed your instructions, first with the Settings/Permalink, which didn’t change anything and then I found the root menu in the File Manager and looked for wp-config.php. Then I added the code as you said. I pushed Save and I suppose it did, although it went to a blank screen. I then went back to the File Manager to check that the phrase was there and it was. So I went to my site and clicked on a few blog categories and I got the same white screen without any error message.

I had a thought. My blogposts are set to Post Name – http://www.calabriatheotheritaly.com/sample-post/ On my last 2 posts I shortened the url. So, instead of http://www.calabriatheotheritaly.com/reflection-drills-and-politics-in-italy/, it’s http://www.calabriatheotheritaly.com/politics-in-italy/. Could that have something to do with the problem? I thought that on the Edit Post page you could make adjustments.

Thank you for your assistance,
Karen

[Paul R]

Hi,

Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

[karenhaid]

This reply has been marked as private.

[Rue Nel]

Hello There,

I did some further investigation. I noticed that you are using PHP version 5.3.29 and WordPress 4.3 requires at least 5.6 (https://wordpress.org/about/requirements/). This could possibly be the cause of the issue. In most cases you cannot update your PHP version yourself and need to contact your host about this. The upgrade process is an easy process and should be something your host can do for you without affecting your website or charging you for it. Here’s a letter you can send to your hosting company:

Dear host,

I\'m interested in running the open-source WordPress <https://wordpress.org/> 
web software and I was wondering if my account supported the following:

PHP 5.6 or greater
MySQL 5.6 or greater
The mod_rewrite Apache module

Looking forward to your reply.

Hope this helps. Kindly let us know.

[karenhaid]

Thank you for all of the information. I contacted my provider with the above letter and they told me how to upgrade to PHP 5.6 – just a matter of selecting a different PHP from a drop-down menu and setting it. Apparently they aren’t equipped for the MySQL 5.6 yet.

So, I went back to my site and nothing seemed to have changed. The Category Archives didn’t function and when I selected one, it just went to a blank white screen, as before. The archive by date does function, however – although I didn’t test that the last time, so it was probably fine before.

Would you have any other ideas?

Thank you,
Karen

[Rue Nel]

Hey Karen,

I spent some time again checking your site. It is weird because all the other archive pages such as tag, date, month is working. Only the category page is not. Could you please put the site in maintenance mode and try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Please let us know how it goes.

[karenhaid]

Hello,

First I installed your “under construction” plugin and enabled it. Then, I went to the Plugins page and deactivated everything. Then tested the category archives and got the same white, blank page. As you noted, the other archiving pages worked. So then I reactivated the plugins, but couldn’t connect back up to the Jetpack and got the message:

Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host.
GnuTLS recv error (-9): A TLS packet with unexpected length was received.

Prior to deactivating, the Jetpack was connected without a problem. So I deactivated the Under Construction and still couldn’t connect to Jetpack. Then I deleted the Under Construction and still couldn’t connect to Jetpack.

I’m left scratching my head. Now I have an additional problem.

Other possibilities?

Thank you for your time.

Karen

[Lely]

Hello Karen,

Please try checking in with your hosting provider about this issue with jetpack. Or you may check this link:
http://blog.stuart.shelton.me/archives/883

For the original issue, would you mind switching from child theme to main X theme? Then clear cache and check again. This is to make sure that the issue is not a result of any customization. Do let us know how this goes.

Always,
X

[karenhaid]

Hello,

I wasn’t sure how to switch from child theme to main X theme. What I did was activate the X theme and then on the Dashboard it said, “WordPress 4.5 running X theme” So, I take it that’s what you suggested. I then emptied the caches and I got the same blank page on the category archives. And then I switched back to the child theme.

As I mentioned with the Jetpack, the strange thing is that it worked just fine initially before I went into maintenance mode and deactivated/reactivated. I’m hoping my host can come up with something on it.

Another thought regarding one of the above messages #893101. Could some of the other issues that cropped up after I started trying to determine what the problem was with the category archive be related to this Debug code. I’m a beginner at all of this (yes, painfully obvious), and I thought that perhaps I should have deleted that Debug code afterwards. I just went to the page and I remember putting that code in just above the sentence you told me, but now I see some other stuff in-between:

define(‘WP_DEBUG’, true);
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

/* That’s all, stop editing! Happy blogging. */

Should this all be in there, or should I remove something now? I apologize for asking what is probably a stupid question.

Thank you,
Karen

[Paul R]

Hi Karen,

I would like to check further but the ftp login you provided doesn’t seem to work.

Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– FTP host/ ip
– FTP Username
– FTP Password

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

Thanks

[karenhaid]

This reply has been marked as private.

[Jack]

Hi there Karen,

Thanks for writing in.

I’ve taken a look at this for you and it’s definitely odd, as in the error log apart from two errors from over two years ago there are no other entries.

I have seen similar issues before with W3 Total cache, can you try removing W3 Total cache and then remove the code it adds to your .htaccess and the code it adds to your wp-config.php and see if it works correctly then?

Thank you!

[karenhaid]

Hello,

Can you explain where the code in .htaccess is and what I should remove? I looked under .htaccess in my FileManager and didn’t see anything about W3 Cache.

I found the wp-config.php in my file manager. Is this what I should remove?

/** Enable W3 Total Cache Edge Mode */
define(‘W3TC_EDGE_MODE’, true); // Added by W3 Total Cache

Also, can you answer this question from above:
Another thought regarding one of the above messages #893101. Could some of the other issues that cropped up after I started trying to determine what the problem was with the category archive be related to this Debug code. I’m a beginner at all of this (yes, painfully obvious), and I thought that perhaps I should have deleted that Debug code afterwards. I just went to the page and I remember putting that code in just above the sentence you told me, but now I see some other stuff in-between:

define(‘WP_DEBUG’, true);
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );

/* That’s all, stop editing! Happy blogging. */

Should this all be in there, or should I remove something now? I am afraid that by adding that code I have messed something else up as it’s the only thing I changed before the JetPack stopped being able to be accessed. The problem is that I don’t know exactly what to take out.

Can you please assist me on both of these questions?

Thank you,
Karen

[Author]

Posts