Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter Livsy

    (@livsy)

    Nelio EFI generates a lot of placeholders for each post. Maybe this is the reason of problems?

    Screenshot: https://41.media.tumblr.com/6b2bc52be82eed1bf2042ae45716a7ec/tumblr_nsf98fefJd1u2tf5go1_500.png

    Plugin Author David Aguilera

    (@davilera)

    Hi Livsy!

    That’s weird. All those thumbnails are not generated by our plugin, but by your theme. Any posts using an external featured image will use one of those thumbnails as a “frame” in which the actual external image URL will be set.

    If you’re having trouble with the 1.3 series, I recommend you go back to version 1.2.0. In fact, I’ve set version 1.2.0 as the stable one, so that nobody else faces any more problems.

    I’ll keep working on the 1.3 series and, hopefully, I’ll be able to fix all those issues. In the meantime, though, it’ll be better if you stick to the stable version.

    Best,

    Thread Starter Livsy

    (@livsy)

    Hi David!

    Can I just unpack the old version to my plugins folder? Or I should uninstall ver. 1.3 and then install ver. 1.2 from dashboard?

    Anyway, thanks for support and good luck with troubleshooting!

    Thread Starter Livsy

    (@livsy)

    Find the answer in another topic. But problem with site speed is still exist. Even when plugin was deactivated. With 1.2 version the speed of my site is very slow too. What should I do?

    Thread Starter Livsy

    (@livsy)

    I did a database recovery (from July 28). I lost some posts, but the site is now running normally.

    The new version is not working with my top post images also. Is there a way to fix it without having to backdate or lose anything?

    WTH…
    – every single image is gone
    – regenerate EFI attachments warning never goes away
    – clicking the “Regenerate EFI Attachments” literally regenerates every single attachment, every single time the button is clicked. It’s not a progression.
    – I have over 30,000 images at 1 update per second… that’s going to take a while
    – the update process is done via ajax (i.e. browser window must remain open), why not a cron job?

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘Problems with new version’ is closed to new replies.