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

Sometimes its create duplicate records in Database for content types. #31

Open
RazaTayyab opened this issue Jan 9, 2023 · 4 comments
Open

Comments

@RazaTayyab
Copy link

After Enabling the Seo, Plugin for different content types. After creating the SEO content the plugin attaches the component data to multiple content types. which cases the duplicate content of the content type. After deleting from one end it will also be deleted from other components type as well. In some cases, it also attaches the same component data to the same content-type records as well.

@nydavo
Copy link

nydavo commented Apr 6, 2023

I'm also encountering this issue.

@Mcastres
Copy link
Collaborator

HEllo @RazaTayyab 👋

Thanks for the issue, can you give more context about this issue? I'm. not able to reproduce it.

@mrpharderwijk
Copy link

I have a similair issue.

Strapi Version: v4.12.1
Strapi Seo plugin version: 1.9.2
Node Version: 18.15.0

Collection Types: Pages
Single Type: Global

Inside the Collection Type Pages I have a page called Blog containing the seo component which uses the sharedSeo component. In the Single Type Global I also have the seo component with the same setup. Whenever I change the seo of the Collection Type Pages > Blog and save it, the change is also made in the seo data of the Single Type Global seo data.

For me this is a no no in using this plugin because I can't keep track of what is being overwritten. It seems that the seo id's for both these Types are the same or something similair. They like share the same entry in the database.

@Mcastres
Copy link
Collaborator

My first thinking is that it is more globally a Strapi issue rather than a plugin issue.
Actually, the plugin just creates the component in the app but you manually associate it to your own content types so I don't really understand why this behavior happen :/

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

4 participants