Viewing 14 replies - 16 through 29 (of 29 total)
  • Greetings All.

    Had the same issue with my sites. Looks like when they did the update, the changed the code around for the Import-Export feature. It used to be under separate files, then they combined them. While this is good for the long-run, forgetting to add the file back into the plugin was bad-form.

    Hopefully, it is corrected and an update is issued.

    anonymized-14293447

    (@anonymized-14293447)

    I don’t understand how can that commented line solve the problem, if not even plugins/code-snippets/php/import-export.php is present.
    If they amended the error, well I cannot acces my backend. How can I get the new version? it’s not in the changelog

    I think the easiest solution for most people (if they have server access) is to login to the hosting account and use a file manager (or ftp), navigate to wp-content> plugins folder, and rename the plugin folder from code-snippets to something else, like code-snippets-old. The site will now be accessible. Then re-install the last stable version (2.10.0).

    You can get a copy of the older version here: https://www.ads-software.com/plugins/code-snippets/advanced/ (at the bottom of the page).

    I had to do this for a dozen websites this morning. I’ll wait for the developer to push an update that fixes this.

    Just found my sites white-screened as well, but the fix brought them back up again.

    anonymized-14293447

    (@anonymized-14293447)

    I cannot even disable other plugins… it’s just a series of warnings FUCK THAT IDIOT in AUSTRALIA !

    Solution:

    create a blank file and call it
    import-export.php
    and put this via FTP in the sub-folder “php” of this plugin, and wait for the next update.
    Works fine at my sites.

    Solution:

    create a blank file and call it
    import-export.php
    and put this via FTP in the sub-folder “php” of this plugin, and wait for the next update.

    Plugin Author Shea Bunge

    (@bungeshea)

    Hello everyone,

    I am really sorry that this has happened. It looks like there was an issue with releasing the latest version of the plugin, and one of the required files did not upload correctly.

    I have since uploaded the missing file and rereleased the plugin, so now if you are able to redownload or update the plugin, this will fix this issue.

    Once again, I am really sorry that this has happened, and for the inconvenience and stress it has caused.

    **Edit** Thanks @aumw-jay for the advice.

    Could someone help a beginner? I can’t access my /wp-admin so I’m unsure how to “comment out”

    • This reply was modified 6 years, 9 months ago by class22.

    Thank you for the quick solution Shea, appreciate it and understand that sometimes things like this happen.

    And thanks to the community for providing a workaround.

    Cheers

    @kibbus90
    Does the Fox you commented out really WORK as you described for the time being?
    Once your fix is applied, you can enter dashboard and all things will be as before?
    Also : I have disabled plugin…
    Should I alter the code before activating plugin or visa versa? If I activate first I naturally can’t sign in to WordPress dashboard
    Howard

    Att: Shea
    So you’re saying I can safely “REACTIVATE” the plugin now?
    If I delete and re upload will settings stay as they were before the crash?????
    Howard

    Plugin Author Shea Bunge

    (@bungeshea)

    Hi @howardmil,

    If you delete the wp-content/plugins/code-snippets folder directly using FTP/SSH/etc and then reinstall the plugin, then yes, all of your snippets and settings will be preserved.

    However, if you delete through the WordPress Plugins menu, then all data associated with the plugin will be deleted. So don’t do that.

    Plugin Author Shea Bunge

    (@bungeshea)

    Oh, and in case it wasn’t clear, anyone who has updated to version 2.10.1.1 can safely activate the plugin. This issue only affected version 2.10.1, and only people who upgraded within the first eight hours or so after it was released.

Viewing 14 replies - 16 through 29 (of 29 total)
  • The topic ‘Version 2.10.1 crashes site’s backend!’ is closed to new replies.