Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter dworthington

    (@dworthington)

    Thank you. Your solution solved the situation. Very happy here, and I provided a great review as well.

    Thread Starter dworthington

    (@dworthington)

    Yes, thank you – I will. I first customized suffusion quite a while ago now, when I didn’t know any better, and have since used it on several other sites using a child theme. I’ve just been reluctant to go back and redo everything for this site – but now my hand is forced, so to speak, so now is as good a time as any, I guess.

    Thread Starter dworthington

    (@dworthington)

    My issue is resolved. As I most recently suspected, it was a (suffusion) theme issue. Unfortunately, I now have to re-modify the theme, and find alternatives for a few plugins. But the “what’s going on?” part is over.

    Thread Starter dworthington

    (@dworthington)

    I just finished restoring the site to version 3.3, so now its working again. I have been using a highly-modified instance of Suffusion 3.9.2. I have previously deleted 2011, so I need to load it again. Once I complete that, I will activate it and then attempt the upgrade one more time. If all that works, then I will have to update the Suffusion theme and re-do my mods – this time in an upgrade-proof style.

    Thread Starter dworthington

    (@dworthington)

    In my first post, I said what was happening. The server closed the connection without sending any data. That’s it. This results in a “No Data” Browser error. The browser would eventually timeout itself from this condition, but if the server actively closes the connection, the browser can report that. This is what is happening.

    I suppose it could be a corrupted core data file, but I’ve downloaded and upacked the release 3 times, and ftp’ed it to the server now 6 or 7 times

    Thread Starter dworthington

    (@dworthington)

    The same thing happened. But since I’ve been testing one level deeper, I’m seeing I get a fatal error in /wp-includes/template.php @ line 30. So I’m having a template problem most likely.

    My next step is to restore the old version, switch to a different template (maybe 2011), and try the upgrade again. If that works, I will have to revert back to 3.3 again, as I’m invested in my current template (suffusion) and I will have to modify it, or merge it back into its dev stream to use it.

    Thread Starter dworthington

    (@dworthington)

    Sorry about my attitude – I apologize. I have already done as you suggested twice. Once following the general instructions and once following the detailed instructions. The result is the same in all cases. All plugins were disabled, but not deleted. Overloading the 3.3 version restores operation.

    Thread Starter dworthington

    (@dworthington)

    Really? You’re kidding, right? After I already did that twice (see post)? That’s your best suggestion?

Viewing 8 replies - 1 through 8 (of 8 total)