• Resolved toxicum

    (@toxicum)


    When enabling debugging (Query Monitor Plugin), I see the following notices:

    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:184
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox

    Notice Trying to get property ‘plugin_path’ of non-object
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:189
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox

    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:277
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox

    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foogallery/freemius/start.php:184
    foogallery_fs()
    wp-content/plugins/foogallery/foogallery.php:65
    Plugin: foogallery

    Notice Trying to get property ‘plugin_path’ of non-object
    wp-content/plugins/foogallery/freemius/start.php:189
    foogallery_fs()
    wp-content/plugins/foogallery/foogallery.php:65
    Plugin: foogallery

Viewing 11 replies - 1 through 11 (of 11 total)
  • Hi @toxicum,

    Would you please let us know what version of FooGallery, FooBox and PHp you are using on your site so we can look into this further for you?

    Thread Starter toxicum

    (@toxicum)

    If course.
    WordPress 5.3.2
    PHP 7.3.16
    FooGallery 1.9.8
    FooBox Image Lightbox 2.7.8

    The add-expires-header plugin I uninstalled completely, but there are some leftovers in this table row. It also used the freemius library.

    option_value.fs_active_plugins:

    0:8:"stdClass":3:{
      ...
       O:8:"stdClass":5:{
    	 s:11:"plugin_path";
             s:43:"add-expires-headers/add-expires-headers.php";
             s:8:"sdk_path";
             s:28:"add-expires-headers/freemius";
             s:7:"version";
             s:5:"2.3.2";
             s:13:"in_activation";
             b:1;
             s:9:"timestamp";
             i:1584787157;
         }
    }

    as well as in the fs_accounts row.

    • This reply was modified 4 years, 8 months ago by toxicum.
    Thread Starter toxicum

    (@toxicum)

    It seems I’m in the freemius mess.
    https://www.ads-software.com/support/topic/freemius-mess/

    When I reinstall add-expires-header 2.0 and activate, errors are gone. When I then deactivate and deinstall the plugin, the notices are back.

    FooBox uses Freemius 2.3.0
    Add-Expires-Header 2.0 uses 2.3.2

    Maybe thats the cause?

    • This reply was modified 4 years, 8 months ago by toxicum.
    Thread Starter toxicum

    (@toxicum)

    FooGallery was updated tonight to version 1.9.11

    Same problem.

    Plugin Author bradvin

    (@bradvin)

    @toxicum I can try update FooGallery to Freemius 2.3.2 and send you a version to test, if that is ok?

    Thread Starter toxicum

    (@toxicum)

    Yes, np

    Plugin Author bradvin

    (@bradvin)

    @toxicum – please dl 1.9.12 from here https://we.tl/t-aftsGWbNyv and test it out

    Thread Starter toxicum

    (@toxicum)

    Moved plugin dir, then installed 1.9.12. Nothing changed:

    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:184
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox
    Notice Trying to get property ‘plugin_path’ of non-object
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:189
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox
    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foobox-image-lightbox/freemius/start.php:277
    foobox_fs()
    wp-content/plugins/foobox-image-lightbox/foobox-free.php:61
    Plugin: foobox-image-lightbox
    Notice Undefined index: add-expires-headers/freemius
    wp-content/plugins/foogallery/freemius/start.php:184
    foogallery_fs()
    wp-content/plugins/foogallery/foogallery.php:65
    Plugin: foogallery
    Notice Trying to get property ‘plugin_path’ of non-object
    wp-content/plugins/foogallery/freemius/start.php:189
    foogallery_fs()
    wp-content/plugins/foogallery/foogallery.php:65
    Plugin: foogallery

    Will try now to perform the freemius cleaner. I’m quite sure it has to do with the leftovers in the 2 option rows I mentioned.

    Thread Starter toxicum

    (@toxicum)

    Interesting.
    I deleted the uploaded 1.9.12 version plugin folder, moved 1.9.11 release back to plugins, re-activated FooGallery, and the warnings are gone!

    The fs_ db option rows seem to have cleaned up now, as they only contain the foobox-image-lightbox info.

    I then deactivated / activated all other plugins which use freemium.

    Warnings are permanently gone.

    It seems freemius is not that easy. Singleton is ok, but when many plugins install different versions, how could that work?

    Thread Starter toxicum

    (@toxicum)

    Thanks for your help.

    Plugin Author bradvin

    (@bradvin)

    glad you got it working. I think in most cases you should be fine, but unfortunately, you just seemed to have the “perfect storm” of problems which caused your issue

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Undefined indexes and other notices’ is closed to new replies.