This happened in the following conditions:

1.) Site originally used taxonomy. Simplenews was installed and a newsletter vocab created with one newsletter term
2.) Category module was installed, both the wrapper modules enabled, cat_legacy enabled and the import done *without* turning off simplenews module. All legacy paths and aliases were redirected.

Screenshot attached.

CommentFileSizeAuthor
#7 cat_legacy_duplicate_containers6.gif5.39 KBvenkat-rk
#6 cat_legacy_duplicate_containers5.gif12.11 KBvenkat-rk
#5 cat_legacy_duplicate_containers4.gif7.22 KBvenkat-rk
#4 cat_legacy_duplicate_containers3.gif4.1 KBvenkat-rk
#2 cat_legacy_duplicate_containers2.gif4.08 KBvenkat-rk
cat_legacy_duplicate_containers.gif6.44 KBvenkat-rk

Comments

venkat-rk’s picture

venkat-rk commented

I forgot to add that the fixes provided in this thread were applied (#0, #6 and #12).

I may be wrong, but I doubt if this issue has anything to do with those patches. I have experienced the same bug before, I just didn't submit it. If I turn off the simplenews module before importing, duplicates are not generated.

venkat-rk’s picture

venkat-rk commented
StatusFileSize
new cat_legacy_duplicate_containers2.gif4.08 KB

The containers (Newsletter) were generated at the same time, as the timestamp in this screenshot shows.

venkat-rk’s picture

venkat-rk commented

In the previous screenshot, the top link points to node/8, the middle one (the actual newsletter) points to node/7 and the bottom, to node/6

venkat-rk’s picture

venkat-rk commented
StatusFileSize
new cat_legacy_duplicate_containers3.gif4.1 KB

More confirmation about the duplicate containers on the admin/node page

venkat-rk’s picture

venkat-rk commented
StatusFileSize
new cat_legacy_duplicate_containers4.gif7.22 KB

When I tried to delete the additional container that had been created, a new node (and an alias) was created although category prints out a message that the node was deleted.

This happened twice- the original node I tried to delete was node/8 (node/9 was the newsletter term beneath it). Node/10 was then created with an alias and when I tried to delete that, node/11 was created.

Something in either the wrapper module or cat_legacy isn't working right.

venkat-rk’s picture

venkat-rk commented
StatusFileSize
new cat_legacy_duplicate_containers5.gif12.11 KB

I tried deleting the containers from the admin/node page, but with the same results- a new node (container) and an alias was created. The category (newsletter term) was deleted fine.

venkat-rk’s picture

venkat-rk commented
Component: Category_legacy » Wrapper modules
StatusFileSize
new cat_legacy_duplicate_containers6.gif5.39 KB

It's the wrapper module !!

I temporarily uninstalled it, went to admin/category/list/outline and deleted node/12, the newly created container. And it worked.

Moving this issue to the correct component.

venkat-rk’s picture

venkat-rk commented
Title: Cat_legacy generates duplicate containers on taxonomy import » Wrapper module generates duplicate containers on taxonomy import

Changing title too.

bdragon’s picture

bdragon commented

Any updates?