initially received a Page not found error when trying to edit the associated node
| Project: | Taxonomy Node |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | hanoii |
| Status: | closed |
Jump to:
I installed the module earlier tonight. I haven't fully put it through its paces, but I did run into a couple of things. I tried the module on an existing test site with a pre-built taxonomy already in place. When I went to the edit page for a taxonomy term and tried to click on the link within the "You can edit the associated node >TERMNAME< as well" text I received a "Page not found" error.
It took a while of poking around in the .module file before I realized that I had to visit the Vocabulary page first to create the association. It might help to provide a check that the association has been created before displaying the link on the term page. Then again, a README file could also point users in the right direction.
Also, once I did try to create the association, I got a timeout error, presumably because I tried it first on a vocabulary with a lot of terms.
Neither of the issues are necessarily show stoppers, but I thought you might like some initial feedback from a first time user.
Thanks for the module.
#1
Yes, a README would certainly be helpful, I'll try to do that soon. About the link to the node that has not being created, you are right, that shouldn't have been there and I'll fix that soon as well.
For the timeout issue, you did check the batch create checkbox, didn't you? I am asking because that's the only case where the association should take that long if a lot terms are there. I'll probably put a limit there as well.
#2
Yeah, the timeout was with using the batch create checkbox. For what it's worth, the vocabulary in question has 650+ terms and I was testing on a relatively slow laptop, so I'm not surprised it timed out. I just thought I'd pass it along as a possible issue to keep in mind.
Thanks again. And feel free to close the issue, since it sounds like you already have plans to address the things I brought up. My intent was for the message to provide feedback more than to report an actual bug.
#3
Hi Matt. Feedback appreciated. I have released a new version (1.2) with readme and the timeout issue with some limit as well as some other nice new little improvements. If you have time, check at the release notes of the version, the readme file and try again the module as more feedback is very much welcomed.
Thanks
a,=
#4