[Plugin: Easy Nivo Slider] Destroys Memory

I’m sorry, I don’t understand what “destroys memory immediately” means. Can you be more specific?

Can you offer some information on what kind of problem you are experiencing?

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected ‘;’ in …/wp-content/plugins/easy-nivo-slider/easy-nivo-slider.php on line 95

WP 3.1 fresh installation

arg. I missed a file when I uploaded changes last night. Correcting that now…sorry.

Ok, the file should be updated now. Sorry about that.

10x

another little problem

Getting above message when I try to run a NextGen slider:

NetworkError: 404 Not Found – …/wp-content/plugins/easy-nivo-slider/3rd-party/jquery.nivo.slider.js?ver=2.5″
jquery…ver=2.5
$(“#slider-1”).nivoSlider is not a function

I found the problem:

easy-nivo-slider.php
rows 21-22 and rows 73-74

21 wp_enqueue_script(‘nivo-slider’,plugins_url(‘/3rd-party/jquery.nivo.slider.js’,__FILE__),array(‘jquery’),EASY_NIVO_SLIDER_NIVO_VERSION);
22 //wp_enqueue_script(‘nivo-slider’,plugins_url(‘/3rd-party/jquery.nivo.slider.pack.js’,__FILE__),array(‘jquery’),EASY_NIVO_SLIDER_NIVO_VERSION);

73 // wp_enqueue_script(‘nivo-slider’,plugins_url(‘/3rd-party/jquery.nivo.slider.pack.js’,__FILE__),array(‘jquery’),EASY_NIVO_SLIDER_NIVO_VERSION);
74 wp_enqueue_script(‘nivo-slider’,plugins_url(‘/3rd-party/jquery.nivo.slider.js’,__FILE__),array(‘jquery’),EASY_NIVO_SLIDER_NIVO_VERSION);

Dang, that’s my inexperience with Subversion. I missed that file when I committed the changes for 1.6.1. It should be there now. Apologies for the miss.

Any future updates will use the packed plugin. (was using the nonpacked in an attempt to correct the sizing of NextGen galleries)

This looks awesome, except no matter how many slides I specify, it only shows 5, and I seem to have no control over which 5. Any thoughts?

I’m receiveing this two messages on my admin panel. What seems to be the problem?

Warning: session_start() [function.session-start]: open(/tmp/sess_c07db6e2e5103613c7e55edb4faf2328, O_RDWR) failed: Read-only file system (30) in /home/**************/wp-content/plugins/easy-nivo-slider/easy-nivo-slider.php on line 112

Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/********************/wp-content/plugins/easy-nivo-slider/easy-nivo-slider.php:112) in /home/***************/wp-content/plugins/easy-nivo-slider/easy-nivo-slider.php on line 112

yiotta,
Which type of slider are you using? It may be that the type you are using isn’t processing the number=xx parameter correctly, or that the other sliders are not available – knowing which type of slider will help to pinpoint the problem.

Version 2.0, which I’m testing now, allows you to sort the images/posts/etc that are selected based on date, name, etc. Hope to have it available soon.

svetskigigacar, that message shows up when a plugin or theme file outputs a character (any character, even a space) before the session variables are initialized.

Not all scripts/plugins/themes use session variables, which is probably why you haven’t seen this before. Easy Nivo Slider uses two session variables to pass data to the editor popup window – it’s how the plugin knows what’s what.

I don’t *think* my plugin is generating the error-causing space, but the use of session variables is what’s setting the warning. A few options:
1. You could try disabling other plugins to see if the warning goes away. if turning off a plugin removes the warning, then that plugin is generating the whitespace. I’ve found this problem is often caused by the simplest of things – having an extra space or line after the ?> at the end of a php file.
2. You could turn off the editor part of the plugin. this would be a manual edit of the code to just deactivate the shortcode generator – basically give the plugin a lobotomy. The shortcode would then have to be entered manually, but the warning would go away.
3. I modify the plugin to not use session variables. This would be the best solution, but time constraints make this hard for me right now.
Sorry I cannot say, “click this and it will be fixed:.