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.

GP Premium “not been tested”

  • The last TWO updates to GP Premium triggers a WP alert, “Warning: This plugin has not been tested with your current version of WordPress.”

    Yes, I know it still works. But it strikes me as inattentive or sloppy: you can’t increment the supported version number past 6.6? WP is at 6.7.2.

    It creates support confusion among my clients, and I’m afraid I might be injured when my forehead hits my keyboard.

  • Hi there,

    We’ve released a patch today, and it’s set to be compatible with WP 6.8

  • Thanks, Ying. Hope they keep up with that in future releases.

  • Yeah, except that the changelog doesn’t mention ANY changes done in 2.5.2, AND it still says it’s compatible up to v6.6. Sigh.

  • It doesn’t:

    https://snipboard.io/53M4ph.jpg

    In short, the reported problem persists despite your assurance of a fix in the release yesterday.

  • Well, it does in GP’s change log.

    It might not show up yet in WP.

  • Bottom line: that’s a poor answer. You can’t pass the problem along? You’re saying I have to be satisfied with a Tier 1 response? Sorry, but “I dunno?” really isn’t acceptable when I’ve paid for support.

  • We knew the problem, it’s caused by aggressive WP cache, it takes time to show the actual message.

    We’ve tried clear cache on our end multiple times, so it depends on when WP clear its cache.

    Hope that’s clear!

  • Yes, that’s clear AND helpful, thank you.

    Indeed, without further updating it IS now showing compatibility, as well as showing 2.5.2’s changes. I’ve never seen such a lag previously, so it’s good to know of this possibility. I consider that a bug in WP!

    I’m satisfied with the fix and will mark this as solved. Thanks again.

  • You are welcome   🙂

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