Viewing 10 replies - 1 through 10 (of 10 total)
  • Just because it does not work for you and your WP-version, hosting, plugins, etc, does not mean it’s for you to set an alarming header like this in a support forum.

    Ask a question and enclose circumstances.

    Hello @rkebbi, could you please post here your error message so that someone might assist you further.

    Kind regards

    Thread Starter rkebbi

    (@rkebbi)

    Hello Gezan,

    Maybe be you’ve right, maybe you’ve wrong !
    The last version 3.0.8 work well with all my plugins and WP-version…
    Without it works…and I posted my version of WP…
    I think a forum is a place to talk… like a democracy…
    have a nice day too ! ??

    Thread Starter rkebbi

    (@rkebbi)

    Hi mbrsolution,

    Thanks for your help, the error message was :
    “Erreur HTTP 500 (Internal Server Error) : Une situation inattendue s’est produite tandis que le serveur tentait de traiter la demande.”

    But I uninstalled the version and it works now. I don’t want to update again for the moment.

    Thanks again for your help !

    Good work!

    Thread Starter rkebbi

    (@rkebbi)

    Gezan thank you for your congratulations!
    I close this I keep the previous version. I will therefore not update at the moment.

    Hello @rkebbi, have you got a testing site?

    I have seeing another person post a similar error with WordPress 3.4.2.

    Kind regards

    Thread Starter rkebbi

    (@rkebbi)

    Thanks mbrsolution !
    So I have to update my WP version
    Have a nice day ! Thank you !

    Hi @rkebbi, running the most up to date version of WordPress is always advisable for security and stability purposes. I always encourage users to have the latest WordPress version. If you decide to update please make sure that you have a backup just in case something goes wrong.

    Also, I am not saying that you should update to the latest version although it is advisable. I am just curious that two have already reported some issue while running WordPress 3.4.2.

    Kind regards

    Plugin Author Robert Windisch

    (@nullbyte)

    We have fixed this issue in 3.0.9 and deployed version 3.0.10 with the folder change. When the Source Code was submitted to svn the change of the folder failed. This caused the error at the version 3.0.9. I am sorry for the problem this release caused.

    regards,
    Robert

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘DON'T UPDATE TO 3.0.9 !!!’ is closed to new replies.