• Resolved Malae

    (@malae)


    Thank you for your excellent slider plugin.

    The update to version 2.1.6 produces the following notice:

    Notice: Undefined index: sa_auto_height \wp-content\plugins\slide-anything\php\slide-anything-frontend.php on line 169

    Regarding the changelog, may I suggest that you reverse the order to put the latest change at the top, to avoid having to scroll down the page to find the most recent changes.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author simonpedge

    (@simonpedge)

    Ok, small bug with the new release. Please edit your slider, and re-save it. This should sort out that issue.

    Thread Starter Malae

    (@malae)

    Hi Simon,

    The above issue occurred on a site running on WAMP, where I leave wp-debug running and had several lines of the notice. Before your reply, I had deleted ver. 2.1.6 and reinstalled ver. 2.1.5. On activating I had no images on the page with the slider shortcode. On the SA page all the images are still showing, although the text editor will not open and the Preview shows a darkened empty page, the same for the Sample Slider.

    I tried saving the slides again with no effect. I reinstalled ver. 2.1.6 and still same result and the same with the Sample Slider and a newly created Slider.

    I then deleted and reinstalled ver. 2.1.6, but it did not change anything, or resolve the issues.

    On the page with the shortcode, the Console has the following:

    Uncaught SyntaxError: missing ) after argument list
    VM100:455 Uncaught TypeError: jQuery(...).owlCarousel is not a function
        at HTMLDocument.<anonymous> (VM100:455)
        at i (jquery.js?ver=1.12.4:2)
        at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
        at Function.ready (jquery.js?ver=1.12.4:2)
        at HTMLDocument.K (jquery.js?ver=1.12.4:2)
    Plugin Author simonpedge

    (@simonpedge)

    Look at what you’ve given me, I’ve got no idea – it seems that it’s not locating a file/files in the Owl Carousel plugin, which I bundle with Slide Anything.

    Not experiencing this issue myself – I just enabled debug on edgewebpages.com – no error messages.
    Also have not got any other emails/support threads for this error from anyone else, and I would have been flooded with messages if there was a general bug (40K+ active installs)

    Could be a clash with another plugin or your theme. So you need to go through the process of:
    1) deactivating all plugins, check if the error persists, and then activate your plugins one-by-one
    2) activate another theme temporarily to see if this resolves the issue

    ALSO: double check if you are receiving any JavaScript errors (press CTRL+SHIFT+J keys together to bring up the JS Console)

    Could also be something that occurs only with WAMP – I’ve not used this before – all the sites I deploy are on linux.

    Re saving the slider solved this error for me.

    Plugin Author simonpedge

    (@simonpedge)

    Ok, I’m glad you got it resolved.

    Thread Starter Malae

    (@malae)

    Hi Simon,

    I had already tried deactivating all plugins, without success, but did more digging and found some messages in the wp-debug file including:

    WordPress database error Illegal mix of collations 
    and synch.container_id IS NULL made by activate_plugins.

    I did a repair database, restarted WAMP services and, on opening the page, the errors had disappeared and the page with the slider images was back to normal. The site was running PHP 7.0.

    Another site just updated on a hosted server running PHP 7.2 did not show any notices. I assume the issue was caused by the WAMP server.

    Sorry for the trouble, I will be forewarned about WAMP problems in the future.

    • This reply was modified 6 years, 8 months ago by Malae.
    Plugin Author simonpedge

    (@simonpedge)

    In my experience, WordPress doesn’t play well with Windows-Based sometimes. 99% of the sites I’ve developed and deployed have been on Linux-based hosting. I remember a couple of occasions there’s been issues when deploying a client’s hosting which has been windows-based hosting, and where the client switched over to linux-based hosting these issues were resolved. A lot of the time these issues are because of the differences between windows and linux file system permissions.

    So always raises a red-flag for me, and you’ll have less hassles in your life if you stick to linux-based hosting …

    Thread Starter Malae

    (@malae)

    I always use Linux on hosting and only use WAMP for development sites. The main issues I recall were related to case sensitivity when moving to Linux.

    I have a question related to the recent update. Wordfence is warning that the slide-anything-frontend.php file on my website is different from that in the repository.

    Original Version:

    169	 $slide_data['auto_height'] = $metadata['sa_auto_height'][0];
    170	 if ($slide_data['auto_height'] == '1') {
    171	     $slide_data['auto_height'] = 'true';
    172	 } else {
    173	     $slide_data['auto_height'] = 'false';

    Modified Version on your WordPress system:

    169	 if (isset($metadata['sa_auto_height'])) {
    170	     $slide_data['auto_height'] = $metadata['sa_auto_height'][0];
    171	     if ($slide_data['auto_height'] == '1') {
    172	         $slide_data['auto_height'] = 'true';
    173	     } else {
    174	         $slide_data['auto_height'] = 'false';
    175	               }
    176	 } else {
    177	     $slide_data['auto_height'] = 'false';
    178	 }

    It appears that lines 176, 177 & 178 duplicate lines 173, 174 & 175.
    I do not understand why Wordfence is showing a difference, unless you added more code without changing the version number. Can you advise if the the version on my website is the correct one and if so, that I may delete the duplicated lines.

    • This reply was modified 6 years, 8 months ago by Malae.
    • This reply was modified 6 years, 8 months ago by Malae.
    Plugin Author simonpedge

    (@simonpedge)

    Please update to the new version, version 2.1.7

    Thread Starter Malae

    (@malae)

    Thank you Simon.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘PHP Notice: Undefined index: sa_auto_height’ is closed to new replies.