Closed (fixed)
Project:
Vocabulary Index
Version:
5.x-1.1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Mar 2008 at 17:22 UTC
Updated:
24 Jul 2013 at 00:03 UTC
Hi,
in the settings page admin/content/vocabindex, the paths for vocabulary index pages can't be edited (e.g. to change the paths, or to correct a simple typo). Instead of accepting the changes, Drupal reports:
Path already exists.
Path already exists.
Path already exists.
Path already exists.
Path already exists.
Path already exists.
Path already exists.
The changed path is *not* accepted.
The same applies if a new vocabulary is added: Paths for this new vocabulary can't be added to vocabulary index pages, also. This is extremely annoying. This behaviour can be reproduced on different Drupal installations.
There ist a more or less usefull "workaround", which sometimes works:
1. delete all vocabulary index pages paths, click "Save"; the module will give the above error
2. enter the new paths, click "Save"; the module will give the above error, again.
Sometimes the corrected paths are accepted, as far as I can see, even this does no longer work in v1.1.
Greetings, -asb
Comments
Comment #1
xanoAs far as I can see there are two causes for these messages:
1) Whenever you submit the form and you haven't changed a path, that path will cause an error. Annoying, but the vocabindex page will still work.
2) Old paths aren't deleted from the database. New paths can be set, but any path used before cannot be used again until the menu is rebuilt.
I thought I had already fixed these problems. Perhaps they were lost when my computer crashed a short while ago.
Comment #2
asb commented> Whenever you submit the form and you haven't changed a path, that path will cause an error. Annoying, but the vocabindex page will still work.
* Nothing changed, but saved the settings page: vocabulary index pages still exist;
* Tried to edit/add a vocabulary: vocabulary index pages for edited or added vocabulary are not created
> I thought I had already fixed these problems. Perhaps they were lost when my computer crashed a short while ago.
I'm sorry to hear this. However, drop me a line if I can test anything or you need a more detailled description.
Besides this showstopper, the index pages appear to be quite robust (opposed to similar tools that can't handle larger vocabularies).
Greetingsd, -asb
Comment #3
xanoFixed and committed to 5.x-1.x-dev.
Comment #4
xanoJust a short release note: Although the new version no longer has this bug, previously used paths will remain in use, because they are still present in the database. You will have to remove them manually from the menu table in your Drupal database. Removing those paths is not necessary for the new version to function, however, if you don't remove those paths you will not be able to use them again.
Comment #5
asb commentedHi Xano,
thank you for looking into this issue.
> Although the new version no longer has this bug, previously used paths will remain in use, because they are still present in the database.
> You will have to remove them manually from the menu table in your Drupal database. Removing those paths is not necessary for the new
> version to function, however, if you don't remove those paths you will not be able to use them again.
I have located the paths in Drupal's "menu" table, but I don't like the idea to delete records from a system table. Is it safe to use a front end, e.g. PHPMyAdmin, and will deleting records from the system table not break anything else? Alternatively, would it suffice to disable and uninstall the module?
Also, I'd like to note that the new "dev" release is not being announced through the update status module (maybe this is wanted, maybe it isn't ;-)
Thanks and greetings, -asb
Comment #6
xanoRe-installing the module will not work, because it cannot locate the menu paths you have previously used. Manually deleting them is no problem at all, whether by command line or an interface like phpMyAdmin. You will however have to make sure the menu is being rebuilt after deleting the items from the database. You can simply do this by changing one of the existing menu items through the Drupal admin panel or by creating a new Vocabulary Index page.
Dww told me it can take up to six hours before update.module will notify people of a new release. As this is (so far) just a dev version I do not know if update.module will notify people at all. I have decided not to create the 1.2 release yet, because I'd like some people to test it, so I'd really appreciate any feedback from your side.
Comment #7
asb commentedHi Xano,
I manually deleted six Vocabulary Index entries from Drupal's "menu" table; I did not delete the entry "Vocabulary index pages" (admin/content/vocabindex). However, when going to /admin/content/vocabindex, the paths were still entered in the "Paths" fields. Also, the error "Dieser Pfad existiert bereits" (This path already exists") persists. I also edited another menu entry at /admin/build/menu and saved it.
Then I went again to PHPMyAdmin, deleted the Vocabulary Index entries again, edited another menu entry at /admin/build/menu and saved it; after this, the Vocabulary Index appeared again in the "menu" table.
Another thing I noticed: On the vocabulary index pages, descriptions for the taxopnomy terms appear hyperlinked, and they're not separated from the term itself; it shows up as a huge, very long hyperlink.
Greetings, asb
Comment #8
xanoOf course you will have to delete the index pages through the admin panel as well. Vocabindex saves settings in a table of its own as well (The reason for the paths being saved in a separate table as well is that Vocabindex needs to be able to know for which vocabs an index page is set so it can create the needed menu items during a menu build)
About the term descriptions: could you please create a new issue and provide a bit more information regarding list type, etc.? (I'm guessing you're experiencing this problem with threaded lists only?)
By the way: The "won't fix" status is used for issues that are not going to be fixed. As this issue is fixed its status should be set properly.
Comment #9
asb commented> Of course you will have to delete the index pages through the admin panel as well.
The vocabulary index pages can not be deleted at /admin/content/vocabindex, that's what this issue is about. Changes at this page can not be saved, be it a new path, or changes to existing paths.
> Vocabindex saves settings in a table of its own as well (The reason for the paths being saved in a separate table as well is that
> Vocabindex needs to be able to know for which vocabs an index page is set so it can create the needed menu items during a menu build)
OK, so what has to be done to fix this? How is this Vocabindex table called?
The following procedure does *not* work:
1) Disable vocabulary index module
2) Uninstall vocabulary index module - after this, there's no "vocabindex" table in the database (or is it labeled differently and not deleted during uninstall?)
3) Delete all vocabulary index entries from Drupal's "menu" table
4) Enable vocabulary index module; a table "vocabindex" is being created in the Drupal database.
Accessing /admin/content/vocabindex now delivers empty path fields. However, if you don't fill in every path (e.g. for vocabularies that shouldn't have an index page), the error message persists: "Dieser Pfad existiert bereits". Entered paths are recorded in the "vocabindex" table. Still, changes to the paths at /admin/content/vocabindex can not be saved.
Greetings, -asb
Comment #10
xanoThe following procedure should work:
- Delete the used paths from the menu table in your database
- Delete the index pages from the vocabindex table by hand or through the admin panel. The latter should work as far as I know. If it doesn't, do it manually using phpMyAdmin/
- Upgrade the module to 5.x-1.x-dev
This is what I have done locally and it worked. You will only get the "Path already exists" error when there's 1) a node already using that path, 2) a menu item using the path or 3) another vocabindex using the path. This issue was about number 2 (the menu items). When deleting them from the database and deleting any possibly existing vocabindex pages using those paths the whole issue should be solved as far as I can see. If not, please provide some more information about why it won't work for you. Without information I cannot help, so please provide any info you might think is relevant.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #12
xano