Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generated link doesn't match with expected link #460

Open
RikLamers opened this issue Sep 15, 2023 · 2 comments
Open

Generated link doesn't match with expected link #460

RikLamers opened this issue Sep 15, 2023 · 2 comments

Comments

@RikLamers
Copy link

Hi there!

Description

We are building a website using Nuxt 2 & Craft 3. We utilize the GraphQL API provided by Craft to fetch our content on the front-end.
We are experiencing an unexplainable issue: throughout our website, the link (URL) shown in the SEO field doesn't seem correct. For example, we have a section called "Events Overview", which is a single. The URI we provided is "events" so we would expect to see "localdev.com/events" as url generated for the Google tab output. Instead, we are seeing "localdev.com/events/events-overview". Added an image below which shows the output of the SEO plugin.
Screenshot 2023-09-15 at 11 34 20
Another example is a single section named "Events & Culture" that has the URI "events-and-culture" output link by the SEO plugin: "localdev.com/events-and-culture/events-culture".

Steps to reproduce

I don't know how to reproduce since I can't see anything wrong in the config of the plugin.

Additional info

  • Craft version: 3.8.11
  • SEO version: 3.7.5
  • PHP version: 8.0.26
  • Database driver & version: MariaDB 10.4.27
  • Other Plugins:
  1. Super Table - 2.7.5.1
  2. Site Switcher - 2.2.0
  3. SAML Service Provider - 2.7.5
  4. Redactor - 2.10.12
  5. KeyChain - 1.0.3

If there is anything else I could clarify more or should provide more information about let me know!

@niektenhoopen
Copy link
Contributor

@RikLamers Does this issue still occur? I suspect that #464 might be related

@RikLamers
Copy link
Author

Hi @niektenhoopen

This issue is still present.
I made a typo in the version we used, this was 3.7.4, I've now updated to 3.7.5 as mentioned in the description of the issue and the issue still occurs.

The issue you mentioned looks like it indeed could be related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants