unexpected output

  • Resolved Jakob Helmer

    (@jakobuz)


    1 year, 3 months ago

    congratulations for being back Jacob!
    The latest update caused sadly enough some issues for us:
    the album order is now mixed up and when I click on a album an js-popup comes up with the message “unexpected output”.
    If I log out of WP and go to the albums it all looks good, but after a while the errors as described occur.
    I’ve cleaned the cache of WPPA, but it didn’t help.
    The error log (just a part ): 

    Recursieve logmelding gedetecteerd: Err Could not create

url: /wordpress/wp-admin/admin-ajax.php?action=wppa&wppa-action=render&wppa-size=910&wppa-occur=1&wppa-fromp=16588&lang=nl&cache=1&wppa-album=8f257d45bdf1&wppa-cover=0&wppa-occur=1&lang=en&resp=1&wppa-cw=1242
Err: on:23.12.2023 09:58:27: rzl_admin (2153784): Illegal photo specification: wppa-photo=016255851610 (wppa_encrypt_url) Stack: wppa-links.php:1917 wppa_encrypt_url() <- wppa-thumbnails.php:1225 wppa_get_imglnk_a() <- wppa-theme.php:145 wppa_get_thumb_masonry() <- wppa-functions.php:587 wppa_theme()
url: /wordpress/wp-admin/admin-ajax.php?action=wppa&wppa-action=render&wppa-size=910&wppa-occur=1&wppa-fromp=16588&lang=nl&cache=1&wppa-album=401025083bac&wppa-cover=0&wppa-occur=1&lang=en&resp=1&wppa-cw=1242
Err: on:23.12.2023 09:57:53: rzl_admin (2139778): Illegal photo specification: wppa-photo=209787392021 (wppa_encrypt_url) Stack: wppa-links.php:1917 wppa_encrypt_url() <- wppa-thumbnails.php:1225 wppa_get_imglnk_a() <- wppa-theme.php:145 wppa_get_thumb_masonry() <- wppa-functions.php:587 wppa_theme()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
War: on:23.12.2023 09:57:21: rzl_admin (2130522): .../wp-content/cache/wppa-shortcode/nl-log-4209-d95d6b15a7c7e41c30e29590adba3670 could not be removed Stack: wppa-cache.php:561 wppa_unlink() <- class-wp-hook.php:324 wppa_page_cache() <- class-wp-hook.php:348 apply_filters() <- plugin.php:517 do_action()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
War: on:23.12.2023 09:57:21: rzl_admin (2130522): .../wp-content/cache/wppa-shortcode/nl-log-4209-bf72b55e5192243b69f95d32554ee1c2 could not be removed Stack: wppa-cache.php:561 wppa_unlink() <- class-wp-hook.php:324 wppa_page_cache() <- class-wp-hook.php:348 apply_filters() <- plugin.php:517 do_action()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
War: on:23.12.2023 09:57:21: rzl_admin (2130522): .../wp-content/cache/wppa-shortcode/nl-log-4209-b3cf8c0dc3e29f0ea5d70bf95d87c6a2 could not be removed Stack: wppa-cache.php:561 wppa_unlink() <- class-wp-hook.php:324 wppa_page_cache() <- class-wp-hook.php:348 apply_filters() <- plugin.php:517 do_action()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
War: on:23.12.2023 09:57:21: rzl_admin (2130522): .../wp-content/cache/wppa-shortcode/nl-log-4209-8d67f8f44641dbe382d621cc73b0b85f could not be removed Stack: wppa-cache.php:561 wppa_unlink() <- class-wp-hook.php:324 wppa_page_cache() <- class-wp-hook.php:348 apply_filters() <- plugin.php:517 do_action()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
War: on:23.12.2023 09:57:21: rzl_admin (2130522): .../wp-content/cache/wppa-shortcode/nl-log-1-administrator-bbp_keymaster-cfbd9784c9178fed25db33092f186fba could not be removed Stack: wppa-cache.php:561 wppa_unlink() <- class-wp-hook.php:324 wppa_page_cache() <- class-wp-hook.php:348 apply_filters() <- plugin.php:517 do_action()
url: /wordpress/wp-admin/admin.php?page=wppa_cache&delete=1
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jacob N. Breetvelt

    (@opajaap)

    – What is exactly you version number? (8.6.01.003 ?)
    – What should i do to reproduce it? Admin or frntend, what page and what display and what to click upon???

    Thread Starter Jakob Helmer

    (@jakobuz)

    Versie 8.6.01.003
    It happens on the frontend. Only for some albums:
    If I click on some older albums a popup appears with “unexpected output” and than the album-order is mixed up. Than, when I clean the cache, the album order is oke again. When I click the same album, the same happens. Settings of all albums are the same …
    I’m now doing some regular maintenance (cleaning the index, renew albums codes) … hopefully it helps … don’t know yet ..

    • This reply was modified 1 year, 3 months ago by Jakob Helmer.
    • This reply was modified 1 year, 3 months ago by Jakob Helmer.
    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    Do the following:
    Go to Photo Albums -> Settings -> Advanced settings -> Maintenance -> I
    Run the items
    18: Renew album crypt
    and
    20: Renew photo crypt
    by clicking the Start button, one at a time and wait for completion
    This should fix it.

    Thread Starter Jakob Helmer

    (@jakobuz)

    Thanks Jacob. i will do. I’ll keep you informed.

    Thread Starter Jakob Helmer

    (@jakobuz)

    it looks that “renew photo code” is locked in some kind of loop:
    it hangs on a number between 6000 and 9000 and than starts again somewhere at 10.000. The status is also variable, it alternates between “pending”, “cron-job” and “working”.

    • This reply was modified 1 year, 3 months ago by Jakob Helmer.
    Thread Starter Jakob Helmer

    (@jakobuz)

    I installed the new version (8.6.01.004).
    fyi: the popup “unexpected output” at the same older albums still exists, but the album-order stays oke now.
    The Maintenance -> 20: Renew photo crypt and 10: make new index photo’s are still locked in a loop as described above.

    Plugin Author Jacob N. Breetvelt

    (@opajaap)

    If the jobs are cron jobs, theu will finish eventually. You do not need to keep the browser open for this.

    If yu did not run the renew album crypt yet, do it also by cicking the start as cron job button.
    You can leave the browser.

    Make sure you clear all caches, maybe some time later again, but when the renew album crypt is finished and you cleared caches thereafter, it should be fixed.

    Thread Starter Jakob Helmer

    (@jakobuz)

    Thanks Jacob!
    The problem is solved: we use Redis-caching on our site and that was the cause of the problem.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘unexpected output’ is closed to new replies.