• Resolved ACEkin

    (@acekin)


    There are many entries in my error log file that repeat the same error, presumably every time a gallery image is used in a particular way (I used xxxxxx where a domain or folder name used):

    Only variables should be passed by reference in /home/xxxxxx/public_html/xxxxxx.com/xxxxx/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_singlepic/package.module.nextgen_basic_singlepic.php on line 35

    Is there a fix for it?

    Thank you,

    Cemal

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @acekin – Can you share how you are using the SinglePic display as we are not seeing this in any test site error_logs …

    Thanks!

    – Cais.

    Thread Starter ACEkin

    (@acekin)

    It is probably from one of the old posts, I do not remember using a single pic recently. Is there a way I can quickly find where it may be among the posts?

    When I used to use them, I would choose to insert a single picture, find the one I want, click on the name to insert. It would put a token with dimensions and I might change the dimensions or leave the way it is inserted.

    I will appreciate some pointers to quickly find the post(s) where it was used and remove them.

    Thanks,

    Cemal

    Thread Starter ACEkin

    (@acekin)

    I did a search for singlepic and found the posts. Here is one instance (I replaced the domain name keptlight with xxxxx):

    Decorating the tree

    Cemal

    Thread Starter ACEkin

    (@acekin)

    Here is another use:

    [singlepic id=4156 w=320 h=480 float=none]

    I am going through the posts one by one and removing the singlepic use. Quite time consuming ?? !

    Cemal

    eldo eldorado

    (@eldoradothemeart)

    I have a similar problem ??

    It also throws me wrong buzz when editing gallery

    Fatal error: Cannot unset string offsets in /home/nzamky/akcevmladeboleslavi.cz/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_gallery_display/package.module.nextgen_gallery_display.php on line 1575

    eldo eldorado

    (@eldoradothemeart)

    Fatal error

    How about fixing all these stricts and notices?

    Warning (Suppressed) copy(): Filename cannot be empty 9 wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/nextgen_data/package.module.nextgen_data.php:3408

    Notice (Suppressed) Undefined index: HTTP_REFERER 1 wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/attach_to_post/module.attach_to_post.php:98
    This one is quite funny…

    Strict (Suppressed)	Declaration of M_Ajax::define() should be compatible with C_Base_Module::define($id = 'pope-modul...', $name = 'Pope Modul...', $description = '', $version = '', $uri = '', $author = '', $author_uri = '', $context = false)	1	wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/module.ajax.php:0
     wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/ajax/module.ajax.php
    Declaration of M_Attach_To_Post::define() should be compatible with C_Base_Module::define($id = 'pope-modul...', $name = 'Pope Modul...', $description = '', $version = '', $uri = '', $author = '', $author_uri = '', $context = false)	1	wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/attach_to_post/module.attach_to_post.php:0
     wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/attach_to_post/module.attach_to_post.php

    And 30-40 more… can’t even see my own bugs because they get hidden between all that @*#$^!$
    If it would be my choice, i’d uninstall this slow and sluggish plugin and never look back ?? But I can’t.

    eldo eldorado

    (@eldoradothemeart)

    New, last update, this problem solved;)

    Plugin Contributor photocrati

    (@photocrati)

    @val_ – Please start your own topic so we can try to help you with your specific issue on your specific site.

    See https://codex.www.ads-software.com/Forum_Welcome#Where_To_Post

    … or, feel free to send us a Bug Report (https://imagely.com/report-bug/ … please reference this topic) so we can get a better look under the page at your site.

    Please include as many details as you can about your site and the issue at hand so we can move on this as fast as possible.

    Thanks!

    – Cais.

    Thread Starter ACEkin

    (@acekin)

    I am not sure if the previous message was meant for val or for me? Do you want me to open a bug report or wait here?

    Cemal

    Plugin Contributor Imagely

    (@imagely)

    @acekin – Very sorry for the confusion, it was intended for @val_ ?? Did you recently move/migrate your site? Or have you moved the files on the server? Have you installed our latest update, did it help clear out the error you’re seeing? Just trying to understand why this would happen on your site. We haven’t received any reports of this type of error happening.

    @eldoradothemeart – thank you for the follow up. That is good news! ??

    Becky

    Thread Starter ACEkin

    (@acekin)

    @imagely – No problem, I just wanted to make sure. No, I did not move my site but the hosting company upgraded cPanel which caused me other kinds of grief. Maybe this is related to that. I have the latest updates of everything including NG. I will ignore the error message since everything seems to be working fine. However, if I move my site to a new hosting company that may use a different absolute path structure, will I need to change something in NG settings?

    Thanks,

    Cemal

    Plugin Contributor photocrati

    (@photocrati)

    @acekin – In most migration related issues (and possibly cPanel update/upgrade related problems) the use of the Reset Option under Gallery > Other Options (or our Reset Tool plugin) will resolve the absolute path structures that may be changed.

    Thanks!

    – Cais.

    Thread Starter ACEkin

    (@acekin)

    I have done the reset, I will check the error logs again in a day or two and write again. Thank you.

    Cemal

    Plugin Contributor photocrati

    (@photocrati)

    @acekin – Thanks, as always, for your updates and thoroughness!

    – Cais.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Error log’ is closed to new replies.