I realize it’s sort of a n00b move to not back up your whole site before updating one measly plugin, but it’s also sort of a jerk move to delete the slider entirely when the client updates their plugins… causing this developer to work on his Saturday.
Thanks for causing headaches,
Hi Nick, the plugin should have automatically imported all of your settings if the update was completed by WordPress correctly. This procedure was tested as far back as Easing Slider v1.0 and worked without fault. Not much I can do if for whatever reason that has been prevented.
You can have a look at the code yourself in the Upgrade.php file within Easing Slider v2.0+. I’ve made sure to follow all of WordPress’s best practices in coding the upgrade systems, but they are quite “dodgy” and WordPress hasn’t actually implemented an official channel for hooking into upgrades (despite the outcry for one). Occasionally, as you probably well know with WordPress, it doesn’t always tend to go smoothly.
You can also check if your old setting still exist in the ‘Settings’ panel of v2.0. An option will show titled ‘Legacy Settings’. If so, you could always try uploading v1.2.1 via FTP, then completing the upgrade again. Be sure to wait a moment after the download completes for the plugin to activate automatically.
Regardless, sorry for the inconvenience caused.
Two separate sites, it killed the Easing Slider plugin after update with the same error – “This plugin has been removed because it no longer exists”. You then have to activate the new plugin only to discover that the slider, all the images, settings, etc – are nowhere to be found. Probably because of the new name?
It kills it this same way each time I try it with my backup copies of these sites, too – I wanted to make sure the client hadn’t done something silly. Standard WP upgrade procedure.
It’s not a huge deal, since I had opened the original slider page up before I did the upgrade – but if I hadn’t done that, I’d have had to figure out how to find what the slides were before the client upgraded (no easy task).
That’s very odd, it isn’t occurring for me. I took a screencast of me carrying out the upgrade procedure from scratch. Works fine, no problems.
Potentially your WordPress installs are detecting the filename changes, as WordPress saves records of active and deactive plugins via their slugs and main plugin filename. It used to be ‘easingslider.php’, but was changed to ‘easingsliderlite.php’ to reflect the altered plugin name. However, I did check this out throughly beforehand and WordPress wasn’t giving me any problems regarding the change. Tested on multiple blogs, both online and locally.
Typical that what works for one person may unexplainably not work for others! My sincere apologies. Think for the next update I’ll build in a manual settings import tool, just incase the automatic upgrades don’t go as planned (as they haven’t here).
Again, I’m very sorry for the inconvenience caused.
I’m not doing anything crazy with either install, so who knows! 🙂
Thanks for the follow-up Matthew!
No worries Nick, again sorry for the problems. Hopefully improvements can be made from what has occurred here.
All working fine (anxiously awaiting the return of the arc effect and borders) … but I would like to add my experience — I was working on my site, unaware of any changes when I unexpectedly noticed the slideshow had vanished from my site (seemingly on its own). I installed the update — no images. I had to go into settings and import the OLD SETTINGS to restore my images and slides.
But so far so good … used the code mentioned elsewhere to get it centered again. I seem to have lost the nice border around the slides and no edits to any css files seems to fix that (?)
Hi @aly22, yes that process is normal. The upgrade used to be automatic, but it was failing for some users due to the plugin filename changes. Personally, on my own systems I had no problems at all. But apparently other users were. Possibly due to different hosting setups, etc. I actually tested on 7 WordPress installs before release! Just goes to show you that you can never be too sure.
As a result, I decided to make the system manual in v22.214.171.124. Again, not ideal, but at-least it was guaranteed to work when the user did click the import button. If they failed to do so, simply no slideshow would show. If they were logged in as the admin, they’d get an error message. Un-obtrusive, so users visiting the site wouldn’t know that anything was wrong.
The styling options were held back for the initial release of v2.0. I’m working on adding them as we speak, with a new visual editor. I’d hope to have it added and released as v2.0.2 soon, possibly before the end of this week. However, I think the priority at this moment in time is to nail of the teething problems and bugs. Nearly there.
You should be able to style the slideshow yourself using CSS. The new version has been designed to be much easier than before to re-style. If you are finding that certain CSS properties aren’t being applied, try adding ‘ !important’ to the end of the value to override the defaults. As you can imagine there is a lot of structural CSS (that can be a little tricky to override) in place to make sure the slideshow is structurally sound from the word go.
You can also always style it entirely yourself by disabling the styling via the “Settings” Easing Slider admin menu. Grab the core slideshow CSS yourself from the ‘slideshow.css’ file, then do the rest yourself, if you’re feeling adventurous!
Apologies, I read an older thread and didn’t notice the name had changed back to easingslider. I added the style to my custom.css (not to styles.css) and is now working. Appreciate the quick response, Matthew!!
- The topic ‘Deletes Slider On Plugin Update… Not Cool’ is closed to new replies.