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 Page & Block Elements Not Retaining Trailing Slashes

  • I’m experiencing an issue where GP page elements like buttons are not retaining trailing slashes for relative links. I noticed some SEO issues that Google didn’t like with canonicals, and based on how everything is being indexed all internal links on my site should have a trailing slash. This is especially true for redis caching, so pages are not being built and stored twice in memory based on the different URLs structures.

    I setup some redirects on the backend to mitigate this, but this does seem like a bug on the GP side of things.

    From the page editor, if I add a link to a button and use the relative link “/blog/”, if I save the page it still will show the trailing slash in the editor. However, if I reload the editor page completely the trailing slash is dropped back to “/blog”. The trailing slash also never gets updated to the frontend.

    This is exclusive to GP page elements & blocks. Everything I have updated outside of that has retained the trailing slashes and updated properly on the frontend of the site, so I can definitively rule out any sort of caching isssue.

  • Hi there,

    Not sure I understand the issue, do you mean when you add /blog/ as the button link, it changes to /blog?

    I just tested it on my site with GB button, but I didn’t see this issue:
    https://app.screencast.com/etTnfsNWuAbbN

    And on the front end, the link stays at /blog/:
    https://app.screencast.com/AZgLCC2NgGZVB

    Let me know if I miss anything.

  • Apologies everything’s good now, narrowed it down to a configuration issue with nginx. Appreciate you following up and confirming.

  • No Problem 🙂

    Glad you’ve got it sorted!

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