patocka

Dug around a bit longer, found this fix.

This issue is closed.

Thanks Yogi, I already have a ticket open with my hosting provider so we’ll see what they come back with. They’re just painfully slow with their TAT…

Thanks for the heads up. Its because I have 2.x selected. Switched back to 1.8. Found this:

https://s14.postimage.org/t1a6mu6b5/Comment_Settings_Thesis_18.jpg

Tried ticking the boxes anyway, and hitting save just to see what happens.

Got the following:

Warning: Invalid argument supplied for foreach() in /home/content/p/a/t/patocka1868/html/blog/wp-content/themes/thesis_18/lib/classes/options_design.php on line 468

Warning: Cannot modify header information – headers already sent by (output started at /home/content/p/a/t/patocka1868/html/blog/wp-content/themes/thesis_18/lib/classes/options_design.php:468) in /home/content/p/a/t/patocka1868/html/blog/wp-includes/pluggable.php on line 876

Not a WordPress issue. I’ll log a new ticket with DIYThemes.

This is likely whats causing the issue. Thanks kmessinger for your patience.

Tried to update to 2.0.3.1. That was a disaster. Have a thread going to address that:

https://diythemes.com/forums/showthread.php?84166-Headline-links-link-to-blank-pages-after-1.8-to-2.0.3.1-migration&p=393278#post393278

Reverted to 1.85 just to see if the issue persisted. Still have the comments problem on the 1.85 setup.

Right now I have it set on 2.0.3.1 for DIYThemes to troubleshoot but 1.8 appears to be the only stable build for me right now.

Thoughts?

Good idea. Upgrading to 2.0.3.1. Stay tuned.

Swapped out Thesis for the 2012 Theme. Still “Comments are closed.”

Played plugin bingo. Deactivated all plugins and reactivated one by one.

“Comments are closed.”

I also did a complete fresh manual re-install of 3.5 on Wednesday of last week in trying to troubleshoot an internal server error issue, so I don’t know if going through that process again is going to solve anything unless a fresh batch of upgrades has been released over the weekend.

Save for the steps taken above, reading through the 3.5 master list you linked to, it doesn’t appear that anything listed pertains to the issue I am having at the moment. Then again, if I am overlooking something please let me know.

I opened edit screen options and set the values:

[x]Allow comments.
[x]Allow trackbacks and pingbacks on this page.

Updated test post. Still getting “Comments are closed.”

Disabled Jetpack.

Still getting the “Comments are closed” message.

Well, after a weekend of going back and forth with my hosting service and not finding anything on their end, I logged in today and attempted the plugin updates. And lo and behold, without changing anything outside of what was discussed in this thread – things proceeded without error.

I have no idea how or why this happened. Go figure.

Thanks for your help in troubleshooting regardless esmi. Cheers.

Update: Still waiting on my host to give me some legitimate service. They said they can’t recreate the issue. I’m still seeing it on my end. Likely going to escalate to a phone call today.

In the meantime enjoy an extended 48 hr error log. Still with no 500 error?

[Tue Jan 15 13:40:24 2013] [error] [client 65.55.212.168] File does not exist: /var/chroot/home/content/p/a/t/patocka1868/html/robots.txt

[Tue Jan 15 18:58:31 2013] [error] [client 123.125.71.102] File does not exist: /var/chroot/home/content/p/a/t/patocka1868/html/robots.txt

[Tue Jan 15 23:01:18 2013] [warn] [client 97.74.144.170] mod_fcgid: read data timeout in 40 seconds

[Tue Jan 15 23:01:18 2013] [warn] [client 97.74.144.170] (110)Connection timed out: mod_fcgid: ap_pass_brigade failed in handle_request_ipc function

[Tue Jan 15 23:12:45 2013] [error] [client 180.76.5.61] File does not exist: /var/chroot/home/content/p/a/t/patocka1868/html/robots.txt

[Wed Jan 16 04:58:06 2013] [warn] [client 97.74.144.170] mod_fcgid: read data timeout in 40 seconds

[Wed Jan 16 04:58:06 2013] [error] [client 97.74.144.170] Premature end of script headers: wp-cron.php

[Wed Jan 16 23:32:24 2013] [error] [client 65.55.213.243] File does not exist: /var/chroot/home/content/p/a/t/patocka1868/html/robots.txt

[Thu Jan 17 07:28:58 2013] [warn] [client 97.74.144.170] mod_fcgid: read data timeout in 40 seconds

[Thu Jan 17 07:28:58 2013] [error] [client 97.74.144.170] Premature end of script headers: wp-cron.php

The only other error log is completely empty. I’m going to kick this into my hosts inbox to see what they come up with.

Stay tuned.

Well, after recreating the issue multiple times by trying to run the following:

/wp-admin/update-core.php

/wp-admin/update-core.php?action=do-plugin-upgrade

I’ve accessed the error log via FTP and this is literally the only value that’s returned in the file after 40 min of intentional failure generation.

[Tue Jan 15 13:40:24 2013] [error] [client 65.55.212.168] File does not exist: /var/chroot/home/content/p/a/t/patocka1868/html/robots.txt

Leads me to wonder why the 500 server errors aren’t registering? Am I looking in the right place?

3.5

Ok, after waiting a while the site is back up. I can get into admin. But the problem remains where I get the error, and the 500 Internal Server error is the same as before. The difference now is that I have the following at the top of the screen:

An automated WordPress update has failed to complete – please attempt the update again now.

Click the hyperlink to update and *boom* 500 Internal Server error.

Thanks for the prompt response esmi.

Per your advice:

Switched over to the 2012 default theme, attempted updates, and still experienced the issue.

Reset the plugins folder by renaming plugins to plugins.hold via FTP. Logged out, logged back in. Reverted change. Issue persists.

Backed up entire directory. Downloaded a fresh version of wordpress files, deleted old wordpress directory and re-installed the files with the legacy version of wp-content. Also transferred over the legacy wp-config.php. This allowed me to access the update plugins menu from the toolbar at the top of the screen (which wasn’t capable before) but once I selected the plugins to update I received the server error again, only this time the entire screen didn’t white out with the message, it just showed up in the frame of the Update Plugins view.

Now whenever I click on anything in Dashboard I get the following message: Briefly unavailable for scheduled maintenance. Check back in a minute. Same thing comes up when I try to access my site URL. Trying to access admin login, it 404’s.