Closed (fixed)
Project:
Simplenews
Version:
6.x-1.x-dev
Component:
Usability
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Dec 2008 at 22:15 UTC
Updated:
12 Jan 2009 at 10:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
sutharsan commentedDid you run update.php after upload?
Comment #2
oneklema commentedyes, I ran update.php FYI, after the update I found two taxonomy vocabularies set to Newsletter. I completely uninstalled simplenews, deleted (by hand) the Newsletter vocabulary, and reinstalled the latest dev version. Now, the Newsletter Issue content type exists.
I had the Event type set as a newsletter. As I recall (I am not sure I am remembering correctly) the "extra" Newsletter vocabulary was associated with the Event type.
Comment #3
sutharsan commentedI don't understand your situation and not even sure if your problem still exists.
After update content type Newsletter issue (simplenews) should not disappear. Your newsletter type 'Event' should not be touched at all by the update. Or did you rename the content type from 'Newsletter issue' to 'Event'?
You can find me in IRC if you still need support on this.
Comment #4
oneklema commentedThe issue was that after I installed the updated dev version, the Newsletter Issue content type disappeared. For instance, if I did a "Create Content" there was no link for creating a "Newsleter Issue" content type. Furthermore, all previously created Newsletter Content stopped being displayed on the website. The other odd thing I noticed was that after the update there were two taxonomy vocabularies set to "Newsletter".
I was only mentioning that I had the Event content type marked as a Newsletter because I thought it might be relevant to the problem. So, on my system the "Newsletter Issue" and the "Event" contents types were newsletters. I noticed after the update one of the Newsletter taxonomy vocabularies named "Newsletter" was associated with the "Event" type and the other Newsletter taxonomy vocabulary was associated with the "Newsletter Issue" type (even though the Newsletter Issue type failed to be visible in any other way).
After completely uninstalling all Simplenews related content, modules, taxonomy vocabularies and the re-installing simplenews things seemed to work fine.
Comment #5
sutharsan commentedOk, thanks. It would have been interesting for me to find out how this happened. But now that it is fixed there is no way to reproduce.
What was your previous simplenews version?
What content type(s) did you use as newsletter before you updated? 'Event' and 'newsletter issue'?
Did you rename the 'Newsletter issue' content type before you updated?
Did you use the standard newsletter vocabulary before you updated?
Comment #6
oneklema commentedI updated from the most recent dev version before the 2008-Dec-24 dev release.
I was only using the event and newsletter issue types as newsletters.
I did not rename the newsletter issue content type.
I used the standard vocabulary. I did not make any changes to it.
It looked to me like the uninstall failed to remove the original newsletter vocabulary from the database and the new install created a duplicate. My gut reaction was that this was the root cause of the problem, but I am very much a drupal newbie.
Comment #7
sutharsan commentedNodes and vocabularies are not deleted by design. That was not the problem. A duplicate vocabulary was created because the install was not designed to re-install simplenews on a system where is was installed before. The root cause of your problem was the deletion of the simplenews node type during update. The attached patch fixes both. I think you are fine now and don't need to apply this patch. Upgrade to the latest dev version is optional.