• Resolved rockydinosaur

    (@rockydinosaur)


    I had to deactivate the plugin after the latest update.

    Caused the following debug error on page

    Notice: Function wp_script_is was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scriptsadmin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the swiper handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/hacketts/public_html/wp-includes/functions.php on line 6170

    Notice: Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scriptsadmin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the swiper handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/hacketts/public_html/wp-includes/functions.php on line 6170

    Notice: Function wp_style_is was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scriptsadmin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the swiper handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/hacketts/public_html/wp-includes/functions.php on line 6170

    Notice: Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scriptsadmin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the swiper handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/hacketts/public_html/wp-includes/functions.php on line 6170

    Notice: Function wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scriptsadmin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the testimonials-carousel-widget-handler handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/hacketts/public_html/wp-includes/functions.php on line 6170

    Warning: Cannot modify header information – headers already sent by (output started at /home/hacketts/public_html/wp-includes/functions.php:6170) in /home/hacketts/public_html/wp-includes/functions.php on line 7220

    Warning: Cannot modify header information – headers already sent by (output started at /home/hacketts/public_html/wp-includes/functions.php:6170) in /home/hacketts/public_html/wp-includes/pluggable.php on line 1535

    Warning: Cannot modify header information – headers already sent by (output started at /home/hacketts/public_html/wp-includes/functions.php:6170) in /home/hacketts/public_html/wp-includes/pluggable.php on line 1538

Viewing 4 replies - 1 through 4 (of 4 total)
  • vestamiranda

    (@vestamiranda)

    I am having the same errors with the image carousel since the last update.

    Plugin Support Vitalii

    (@uappsk)

    Hello @rockydinosaur and @vestamiranda ,

    Thank you for bringing this to our attention.

    The fix has now been rolled out. Please update the plugin to the latest version, clear your website cache, and let us know if everything is working correctly on your side.

    Thank you!

    Best regards,
    UAPP Team

    • This reply was modified 2 months, 3 weeks ago by Vitalii.
    Plugin Support Vitalii

    (@uappsk)

    Hi @rockydinosaur and @vestamiranda,

    Just following up on our previous reply — the fix for the script registration issue has been available in the latest version. Could you please confirm whether updating the plugin resolved the issue on your end?

    If you’re still experiencing any errors after updating, please let us know, and we’ll be happy to take a closer look.

    Thank you!
    UAPP Team

    Plugin Support Vitalii

    (@uappsk)

    Hi @rockydinosaur and @vestamiranda,

    Just a quick follow-up — since we haven’t received a reply, we’ll temporarily close this thread.

    If you still need help, you’re always welcome to reopen it or start a new one, and we’ll gladly assist.

    — UAPP Support Team

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.