• Twenty Ten Weaver 1.2.2 seems to have caused a FUBAR in my blog.
    I’m using WP 3.0.1 with Twenty Ten 1.1. I’ve switched back and forth between various themes without problem prior to trying Weaver.

    I installed Twenty Ten Weaver 1.2.2.

    Preview would spin its wheels for a while and then give a Internal Server Error.
    Against my better judgement I thought I’d try activating the theme instead. Same thing happened. Now I can’t get into my blog. All I get is

    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Can anyone suggest how to proceed to recover from this situation?

    -thanks
    PS: Fortunately I do have backups.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator James Huff

    (@macmanx)

    Access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename everything except the /twentyten/ directory. This will force the Twenty Ten theme to activate.

    Thread Starter lyledp

    (@lyledp)

    Thanks James.
    That got things back to normal.

    Unfortunately, Twenty Ten Weaver preview still causes a sever error.

    Moderator James Huff

    (@macmanx)

    Try deleting the theme files and reinstalling it.

    This seems to be a PHP version issue. There was a perfectly legal foreach loop that was causing this issue – but not on all hosts. Most of the time, the code worked perfectly well. We changed the code in question, and it seems to now work on different versions of PHP.

    This kind of bug is really really frustrating because it only happens very rarely, but is awful when it does. Version 1.2.3 should solve the problem.

    Thread Starter lyledp

    (@lyledp)

    wpweaver – v1.2.3 fixed the problem.

    Exploring your theme now.

    I’m liking all the configurable aspects.

    But Twenty Ten Weaver 1.5.4 is fantastic! Great theme!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Twenty Ten Weaver Catastrophe’ is closed to new replies.