[Core] Entry duplication issue in Strapi 5

[sayedbs]

Description:

After installing the Webtool, Sitemap-addon plugin, and configuring it into my project. I attempted to create a duplicate Entry. Change content, and when I click Save Changes, the system doesn't behave as expected. Each time I click the save button, the same issue persists, but the interested thing is every click generated new entry but showing error.

Steps to reproduce the behavior

1. Install/configure the Strapi Webtool plugin and sitemap addon also.
2. Go to the list of content
3. Duplicate an existing Entry.
4. Change something and
5. Click "Save Changes".
6. Showing an alert message and also checking the browser console
7. Back to the list and check how many entries have been added here I add some screenshot.

Screenshots

Browser console:

interesting, this is when I go back to the list, then the showing each click generates/duplicates one item here:

System

• Node.js version: v20.16.0
• NPM version: 10.9.2
• Strapi version: ^5.12.6
• Plugin version: Webtool latest and Sitemap latest
• Operating system: MAC OS

[mrdhira]

I have the same issue in here, what I cann see we can fix in this packages/core/server/services/bulk-generate.ts where in this file

// eslint-disable-next-line no-await-in-loop
      await Promise.all(entity.localizations.map(async (loc) => {
        const patterns = await getPluginService('url-pattern').findByUid(type, loc.locale);
        const path = getPluginService('url-pattern').resolvePattern(type, loc, patterns[0]);

        const alias = await strapi.documents('plugin::webtools.url-alias').update({
          documentId: newUrlAlias.documentId,
          locale: loc.locale,
          data: {
            url_path: path,
            generated: true,
            contenttype: type,
            locale: entity.locale,
          },
        });

        await strapi.documents(type as 'api::test.test').update({
          documentId: entity.documentId,
          locale: loc.locale,
          data: {
            url_alias: [alias.documentId],
          },
        });
      }));

And we can fix the loop instead of usingawait Promise.all we can use for (const loc of entity.localizations) because in strapi 5 (idk the prev version) one documentId can have two row of data, indicatiing published_at is set and is null for managing draft and published status (it's weird, but understandable, should be using historical or transactional data)

[mrdhira]

bumps to @boazpoolman . I can make the PR, but i don't have the access

[boazpoolman]

Hi @mrdhira,

You can create a fork, after which you can create a PR.

See the contributing guidelines for a detailed description on how to do that:
https://github.com/pluginpal/strapi-webtools/blob/master/CONTRIBUTING.md

[mrdhira]

Hi @boazpoolman sorry for the late PR, I hope this is correct, it's my first time to contribute in open source like this. please let me know if there any miss that I need to take a look

!282

[boazpoolman]

This issue was solved in version 1.4.3