• Resolved yaroslav1367

    (@yaroslav1367)


    The loading order of JavaScript snippets is reversed.
    It should be: the lower the priority number, the earlier the snippet loads.
    Currently: the lower the priority number, the later the snippet loads.
    You can see this for yourself by creating:
    Snippet_1.js, write in it: console.log("Snippet_1 Priority: 1 "); and assign it Priority = 1.
    Snippet_2.js, write in it: console.log("Snippet_2 Priority: 99 "); and assign it Priority = 99.

    General Options:
    Automatic insertion, footer
    Linking type - External File

    In the console, you'll see that Snippet_2.js loaded first, followed by Snippet_1.js.
    Here's my console message:
    5134.js?ver=1781766214:4 Snippet_2 Priority: 99
    5131.js?ver=1781766256:4 Snippet_1 Priority: 1

    I'm using Woody Code Snippets Version 2.7.5
    Other installed plugins:
    Backuply Pro
    Code Snippets
    GoSMTP Pro
    Loginizer Pro
    Members
    PopularFX Website Templates
    SiteSEO Pro
    SoftWP
    UpdraftPlus - Backup/Restore
    Woody code snippets (PHP snippets | Insert PHP)
    WP All Export/Import
    WP Data Access
Viewing 1 replies (of 1 total)
  • Plugin Support rodicaelena

    (@rodicaelena)

    Hi there,

    Thank you so much for letting us know about the issue you’re facing. We truly apologize for the trouble this is causing you.

    We’ve confirmed the problem and created a bug report for our development team. They’ll be carefully reviewing it soon and determine the best course of action.

    Our team prioritizes fixes based on their impact and the number of users affected, so it’s hard to say exactly when this will be fixed. But we’ll keep you updated every step of the way.

    If you have any more details that might help us understand the issue better, please don’t hesitate to share them.

    We’ll let you know as soon as a fix is ready. You can also keep an eye on the product’s changelog for updates.

    If you have any other questions, please don’t hesitate to reach out.

    Again, we’re so sorry for the inconvenience and appreciate your patience.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.