Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

GeneratePress GenerateBlocks

Bug Report: Blog Module Script Dependency Error in WordPress 6.9.1

  • Hefin
    February 13, 2026 at 12:38 pm

    WordPress Version: 6.9.1
    GeneratePress Theme Version: Latest
    GeneratePress Premium Version: 2.5.5
    Active GP Premium Modules: Blog module only
    Other Plugins: None

    Issue Description
    When accessing Appearance → Customize with the Blog module activated, the following notice appears at the top of the Customizer:
    Notice: Function WP_Scripts::add was called incorrectly. The script with the handle “generate-blog-themecustomizer” was enqueued with dependencies that are not registered: generate-blog. Please see Debugging in WordPress for more information. (This message was added in version 6.9.1.) in /var/www/html/wp-includes/functions.php on line 6131
    Steps to Reproduce

    Fresh WordPress 6.9.1 installation
    Install GeneratePress theme (latest version)
    Install GeneratePress Premium 2.5.5
    Activate only the Blog module in GP Premium dashboard
    Navigate to Appearance → Customize
    Notice appears immediately at the top of the Customizer interface, debugging enabled and shown

    Expected Behavior
    The Customizer should load without any notices or errors.
    Actual Behavior
    WordPress throws a “called incorrectly” notice indicating that the script generate-blog-themecustomizer is being enqueued with a dependency on generate-blog, but the generate-blog script handle is not registered.
    Isolation Testing

    ✅ Reproduced on clean WordPress installation with zero legacy data
    ✅ Reproduced with zero plugins except GP Premium
    ✅ Error disappears when Blog module is deactivated
    ✅ Error reappears when Blog module is reactivated
    ✅ No other GP Premium modules are active

    Possible Cause
    The Blog module is enqueuing the Customizer script generate-blog-themecustomizer with generate-blog as a dependency, but the base generate-blog script is not being registered before the Customizer attempts to load it.
    This appears to be a script registration timing issue specific to the Blog module in WordPress 6.9.1+.

    Impact
    Functionality: Site and Customizer function normally despite the notice
    Severity: Cosmetic – produces console noise but does not break features
    User Experience: Distracting error message in admin interface

    The issue is reproducible in a completely isolated environment with only GeneratePress theme and Premium plugin active.

  • Ying
    February 13, 2026 at 1:11 pm

    Hi there,

    I can not replicate the issue on a fresh install with WP 6.9.1.

    So it’s likely an issue on your site or server.

    Can you provide an admin login for us to check the backend?

  • Hefin
    February 13, 2026 at 3:07 pm

    Hi Ying,

    Hope you’re all good. I’ve set up a quick test site running on my cPanel instance for you. Everything should be fairly generic, so feel free to dive right in and change anything you need. It’s not a live site, just one of my test sites, so nothing here affects production.

    I’ve given you admin access

    I did install a starter site (Pool Swift starter site), but I don’t think that actually matters for this issue. Just so you know, the error notice itself mentions that it was added in WordPress 6.9.1. I’ve also turned on all error messages, so you’ll see the notice at the top of the screen as soon as you visit the Customizer.

    As you can see, I only have GenerateBlocks and GeneratePress Premium installed. If you remove the Blog module and deactivate it, the Customizer loads fine without errors.

    Thanks for checking this out!

  • George
    February 15, 2026 at 2:12 pm

    Hello.

    I was able to reproduce what you are seeing. We have logged the issue and are working towards a solution.

    Thanks for reporting it!

  • Hefin
    February 15, 2026 at 2:20 pm

    Hi George & Ling,

    Thanks for confirming and for logging it.

    From my testing it doesn’t appear to cause any functional issues, so I’m happy to close this on my end and wait for the fix in a future update.

    Appreciate you taking the time to investigate.

    Thanks again.

  • George
    February 15, 2026 at 2:41 pm

    Yep, it’s just a notice, nothing to worry about, it will not cause any issues on your site!

    Thanks again!

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.