Important Information for Easing Slider v3

so it looks like now that the plugin deleted the slider … fine I created a new one, editted the shortcode still no display. Looks like the container has display:none changed that now the individual images will not display. Checked image names and all correct, tried to edit the css visibility & display on the image no luck. probably some javascript error but I do not really want to debug.

Site = https://www.baysidemarine.net/

I can appreciate growing pains, and I like the plugin but software upgrades should not involve developer effort at all.

BTW image name may be tripping people up if they specify dimensions

So, I upgraded to 3.0.1 again, thinking I’d just try creating a new slider and drop it in instead (I only have the one on the home page). But even that doesn’t work:

Trying to add images from the library causes a fatal error:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /Library/WebServer/axstv/wp-includes/post.php on line 2380, referer: https://localtest.axs.tv/wp-admin/admin.php?page=easingslider&edit=26816

But no image will actually be added. And, I eventually get to a place where the “Update” button won’t enable.

Finally, I am also not able to delete the new slider I’ve made by clicking the “Trash” button in the “All Sliders” view. Nor, for that matter will it duplicate an old slider…

cm

Hi @cm258, thanks for letting me know that you found a solution. Yes, that old function for displaying a slider was discontinued in October 2014. For reference, the code is now:

<?php if ( function_exists( 'easingslider' ) ) { easingslider( ID_HERE ); } ?>

@joefinnerty_123, very sorry for the difficulty you’ve been having. I do agree, growing pains definitely are to be expected. Unfortunately it’s nearly impossible with the tools at our disposal as WordPress developers to ensure 100% guaranteed success when upgrading. With the multitude of other plugins, themes, and variables that could at any point break plugins such as Easing Slider, problems are always expected.

For example, the reason your slider isn’t showing could be related to Javascript interfering with the slider from your theme, or another plugin. The more plugins installed, the more likely an error can occur. In particular, there should be no display: none; property preventing slides from showing, so something alternative is causing this. This we need to debug.

Can you link me to the page in question?

We’ve had over 1,000 successful upgrades today so considering that we’ve only encountered a couple of issues so it’s important to stress that isolated problems will always occur and can be resolved with a little bit of co-operation and effort ??

Hi Matthew, sorry to pile on but I received the following error at the top of my wordpress site so I just deactivated your plugin & used a stationary image for the time being:

– – – – – – – – – –

Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(/nfs/c10/h01/mnt/177660/domains/nhresearch.com/html/wp-content/plugins/easing-slider/easing-slider.php/languages/easingslider-en_US.mo) is not within the allowed path(s): (/nfs:/tmp:/usr/local:/etc/apache2/gs-bin) in /nfs/c10/h01/mnt/177660/domains/nhresearch.com/html/wp-includes/l10n.php on line 556

– – – – – – – – – –

Thanks for all your hard work on this!

I have these errors when I try to activate the plugin and when I can turn the images still will not let me add a new slider.

Warning: Attempt to assign property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-legacy.php on line 661

Warning: Attempt to assign property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-legacy.php on line 662

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 232

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 233

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 234

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 235

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 236

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 237

Warning: Attempt to modify property of non-object in /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-customizer-legacy.php on line 240

Warning: Cannot modify header information – headers already sent by (output started at /home/curbano/public_html/wp-content/plugins/easing-slider/includes/class-es-legacy.php:661) in /home/curbano/public_html/wp-includes/pluggable.php on line 1171

Send the data from the web via the support form.

Does anyone know how to revert to 2.2.1.1? This new “upgrade” is horrid.

To all, I’m currently pushing v3.0.2 that should fixes most of the issues mentioned in this topic. Please upgrade and respond further if that doesn’t appear to be the case.

It’s recommended that you downgrade to v2.2.1.1, then upgrade back to v3.0.2, if you’ve run into trouble upgrading previously. This is necessary to re-trigger an upgrade procedure.

Uploaded 3.0.2…still not working. Can you send out 2.2.1.1?

Hi @roscoe89, all past versions can be found here.

If you can let me know more details on what’s occurring, I’d be happy to help.

all of my sliders vanished once I uploaded 3.0 release. i must have done something wrong.

Ok. Can you see your sliders listed in the “Sliders” admin panel?

If you can, please link me to an example of a slider on your site. Or at least, where a slider was displaying before you upgraded.

Updated to 3.0.1 but since that does not work I reverted back to 2.2.1.1.

Hi @motoristi, have you tried v3.0.2?

Can you provide more information on what issues you had?

Thanks for update, works…

sliders were on our homepage before the upgrade