Duplicate items in Umbraco.config on import to Umbraco
Hi all!
For a website we're importing numerous(250 ish) dealers into Umbraco. We're only encountering a weird issue.
The imports itself works fine, with a save and publish command each item gets saved and published correctly to the CMS.
Only a few nights in a week the umbraco.config gets mildly corrupted. Suddenly a entry is shown twice on the front-end (and twice in the umbraco.config, exactly the same as the first). Whilst in the database it only has 1 result as expected.
When republishing the entire site, the umbraco.config gets rebuild, and everything works fine again.
Any suggestion on what might be the issue?
Some side information: The system checks if the node already exists, when it exists it gets updated. When it doesnt exist, it gets added. When it's no longer in the import, it gets removed.
It might be a bug in 6.1.6 - the first thing I'd do is try upgrading to 6.2.6 (or at least check what issues are fixed in the versions in between) to see if this fixes it.
Duplicate items in Umbraco.config on import to Umbraco
Hi all!
For a website we're importing numerous(250 ish) dealers into Umbraco. We're only encountering a weird issue.
The imports itself works fine, with a save and publish command each item gets saved and published correctly to the CMS.
Only a few nights in a week the umbraco.config gets mildly corrupted. Suddenly a entry is shown twice on the front-end (and twice in the umbraco.config, exactly the same as the first). Whilst in the database it only has 1 result as expected.
When republishing the entire site, the umbraco.config gets rebuild, and everything works fine again.
Any suggestion on what might be the issue?
Some side information: The system checks if the node already exists, when it exists it gets updated. When it doesnt exist, it gets added. When it's no longer in the import, it gets removed.
(Umbraco 6.1.6)
It might be a bug in 6.1.6 - the first thing I'd do is try upgrading to 6.2.6 (or at least check what issues are fixed in the versions in between) to see if this fixes it.
is working on a reply...