Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Thanks for what appears to be a great module.
However, I am not able to get to the configuration page admin/settings/trpnt.
I have installed the module like normal under /sites/default/modules. I do see the modules list under /admin/build/modules, and I am able to check the box and install the module. I do not receive any error messages, and the module indicates that it installed.
However, when I go to admin and look for the option to configure this, I don't see it. I manually go to admin/settings/trpnt, and it gives me the admin/settings page, which indicates that it cannot find that path.
I'm running Acquia Drupal 6.19.
I do have the administer taxonomy permission, and I also logged in under user 1, with no luck.
Any help would be appreciated!
Comments
Comment #1
mherchelUpgrading to the dev release did not help out, either. Thanks,
Comment #2
rsevero commentedSince version 6.x-1.2 the path to the configuration page is http://example.com/admin/content/taxonomy/trpnt.
The Advanced Help page mentions the right path.
Have you installed 6.x-1.2 from scratch or have you updated it?
As per release notes and README.txt, if you are upgrading from a previous version, you must uninstall the module and then install the new version (6.x-1.2). This is necessary so Drupal notices the change in the path.
I probably shouldn't have changed this path in a minor update. Sorry.
Comment #3
rsevero commentedMarking it fixed. Please reopen with new info if necessary.
Comment #4
mherchelThis was a new install of 6.x-1.2 (and then an upgrade to dev).
I got that path from line 28 of the module's readme.txt. This file should probably be updated with the correct path (should this be an issue??).
Anyway, the new path works. I'm now going to get it going. Thanks for the module!
Comment #5
rsevero commentedSure, this is a issue. I forgot to update the documentation mentioning the new path.
It's fixed with http://drupal.org/cvs?commit=446342.
Thanks for your report.