Posted by js1 on March 26, 2007 at 6:47pm
7 followers
Jump to:
| Project: | Category |
| Version: | 6.x-2.0-rc2 |
| Component: | Wrapper modules |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Using the March 6, 2007 category-5.x-1.x-dev.tar.gz. I enable the Taxonomy module, then go to Administer->Content Management->Categories->Settings, and click on the "Install now" link (drupal5/category/wrapper/taxonomy/install), but it returns:
Page not found
Comments
#1
I've installed the taxonomy wrapper manually, but the category module doesn't recognize it as being installed:
Also, there are two Categories sub menus under the Content management menu. Normally, when the taxonomy wrapper is installed properly, there's only one.
#2
Confirmed. I just upgraded from 5.0 to 5.1 and this behavior is the result
#3
Ditto, I also have both symptoms.
(It's also messing up my custom CCK nodes... just on the node view, tho. I believe that this is related, but could be wrong...)
#4
I've got a simliar problem with Drupal 5.2 and Category 5.1.1 . . . The wrapper will install just fine, but the categories no longer be created or edited. I can set them in the page editing form, but they are ignored by Drupal. I finally had to drop back down to Drupal 5.1.
#5
Just to report, I downgraded to 5.1 and all is well. Except for the fact that I am stuck on 5.1.... which is less than ideal...
#6
Just to follow up, how is it coming on this issue? A category module Drupal 5.2 patch is needed for a soon to be production site.
#7
similar issue.
when i try to uninstall wrapper, page not found.
#8
Hello,
I'm running 5.2. I downloaded the latest dev snapshot of the Category module, and:
1. Extracted just the wrappers/ folder and category_wrapper.inc, replaced current files
2. Deleted all of the .old and _old files in the taxonomy module folder
3. Ran the "Install Now"
4. Worked like a charm!
No further problems have developed as of this posting!
#9
I don't want to chance using a "dev" version for such a critical component on a production server. So when is the dev version going to be made into a production one?
#10
2 years later, I guess this may be closed. I ran category 5.x-1.1 on a production site for these 2 years (nearly), and while I got with core updates as far as 5.15, I never encountered similar problems. It might be specific to some configuration, or just to 5.2 core (which I skipped along with a few other versions in my site upgrades), but #8 suggests that's not really the case either. I also suspect that upgrading without un-installing wrappers first might be a bad idea.
But anyway, that's just a bunch of ideas - otherwise this seems to affect only a few sites (if any), and since the original posters didn't follow-up for 2 years now, and 5.x branch is not really maintained now, I'm closing this to clean up in the queue.
Feel free to re-open if necessary.
#11
I tried to use the wrapper install from the category page on my sites. I am trying to implement the Category to provide a sort of easier makeshift wiki.
I get "The file taxonomy.module.php could not be renamed. Unable to perform the specified operation."
I am using Acquia Drupal 1.2.23 (Drupal 6.16 core). I tried to use the manual option and copy the file over and got a white screen ( no screen errors).
Any suggestions would be most appreciated ( code hacks etc).
#12
If you have a paranoia-high security setup (considered a must in Drupal community, but usually not the case on a shared hosting as far as I have seen), you need to do it manually - I never really tried this, but I suspect that there might be some *very* outdated documentation out there. I believe that the thing to do is: In the taxonomy wrapper directory in Category package, rename the .module and .info files so that there's no .php extra extension. Then rebuild modules information, which should probably be done by re-submitting the modules page (even with no change). As I said, I didn't try this myself. It's different from 5.x versions, so beware of old documentation.
First thing I would try is: Change permissions on the taxonomy wrapper directory, and on all the files inside, to make them "world writable". (Sometimes called as CHMOD, or CHMOD 777) If you manage to change the permissions, then the installer script will work fine. You can change the permissions back afterwards.
BTW, this is a support request unrelated to the old bug above. I'm just stating that here, so that the issue may be closed again after this is resolved.