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

Check SEO Keywords to prevent duplication #1808

Closed
edirpedro opened this issue Sep 4, 2014 · 4 comments
Closed

Check SEO Keywords to prevent duplication #1808

edirpedro opened this issue Sep 4, 2014 · 4 comments

Comments

@edirpedro
Copy link

Trying to use SEO Keywords I found that OC doesn't check anything to prevent duplications, because of this i got errors navigating on the store. In this example above, only products from Bike > Accessories are displayed in both Accessories categories because they use the same keyword. They are different on url /bike/accessories, /skate/accessories, but are the same to OC.

We can't let users remember if a keyword already exists!

Category (keyword)

  • Bike (bike)
    • Accessories (accessories)
  • Skate (skate)
    • Accessories (accessories)
@DS-Matt
Copy link
Contributor

DS-Matt commented Sep 4, 2014

@edirpedro -

This has been brought up several times. There is no way to have the same keyword for two different categories (as in your example). Are you requesting creating a validation for the input field or modifying the code to allow for the same SEO keyword for multiple categories (which isn't possible just an FYI)?

Either way, if you don't suggest this with a pull request this will most likely get closed as a non issue by the project owner...

@jamesallsup
Copy link
Contributor

This is already on my to-do and will be added at some point (hopefully before 2.0 is released). It isn't a bug though - improvement suggestions should be added on http://OpenCart.uservoice.com

@DS-Matt
Copy link
Contributor

DS-Matt commented Sep 5, 2014

@jamesallsup -

Can you add the uservoice URL to the ReadMe file - that's a helpful link to have. Also, will you be adding a roadmap (sounds like you've got a private one) anywhere, or would you be using the uservoice as a roadmap?

Thanks!

DS-MATT

@jamesallsup
Copy link
Contributor

We don't have a public road map just yet - I'll discuss it with Daniel later but it is likely that we would be very vague about upcoming changes (otherwise people may just copy before we could release).

I have updated the readme though :)

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

3 participants