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

Hero and Post block all messed up on all archives

  • datatv
    March 29, 2024 at 5:27 pm

    So here we go again! The problem is back! I already did a bunch of things suggested in the past. Cleared and Flushed cache. Deleted and re-installed GenerateBlocks. Regenerated CSS and changed the print method. Nothing works. Why is this so wonky?!

  • Leo
    March 30, 2024 at 2:09 pm

    Hi there,

    Sorry – Fernando is no longer working with us so we might need to refresh the issue a bit.

    This is what I’m seeing currently:
    https://www.screencast.com/t/nAYGYFbjF

    Is that not the correct layout?

    If so can you clear and disable your caching plugin for us to take a closer look?

  • datatv
    March 30, 2024 at 4:44 pm

    No. Definitely not. What you should be seeing is two columns of posts. Not one. And the hero on top should be much larger. Here’s a template that does still work and should show you whqt the homepage should look like.

    I’m using LiteSpeed Cache and just disabled the plugin.

    No change.

  • Leo
    March 30, 2024 at 4:52 pm

    The previous replies have shown that this is not a GP/GB issue – it’s likely a caching or optimization issue still.

    Are you able to restore a backup version?

  • datatv
    March 30, 2024 at 5:53 pm

    Found the problem and it’s not caching. One of our editors created a post and somewhere in that post, no idea yet, has something that is causing to screw things up. Perhaps it’s because we’re using the Classic Editor and someone pasted Gutenberg code in?

  • Leo
    March 31, 2024 at 11:01 am

    Perhaps it’s because we’re using the Classic Editor and someone pasted Gutenberg code in?

    I’m not sure but maybe.

    If it happens again then you would just need to go through the debugging steps again – I think we can confirm that it’s not a GP/GB related issue.

  • datatv
    March 31, 2024 at 12:42 pm

    I’m not so sure it’s not a GP/GB related issue. After all, it’s the code in the post that is screwing up the query builders where the post might reside in that feed. If it’s not in the feed everything is fine, and that’s likely why it was always displaying fine on those post types.

  • Leo
    March 31, 2024 at 12:45 pm

    I think it’s fair to rule out GP and GB based on the previous replies and debugging steps.

    We’ve not had other reports from other users either.

    But we can cross that bridge if/when it happens again – a staging site would be a good idea for odd issue like this.

  • datatv
    March 31, 2024 at 12:59 pm

    We don’t have enough room for a staging site based on our plan. So if it’s going to happen, it’s going to happen here.

Viewing 9 posts - 33 through 41 (of 41 total)
1 2 3
  • You must be logged in to reply to this topic.