I'm the admin. I'm using the admin account. I've narrowed missing image gallery selection, free tags and other taxonomic elements to the core Taxonomy module. I've combed the database. I've examined all related admin pages. I'm locked out of all taxonomy admin pages. What should I do?

Comments

markpenny’s picture

markpenny commented
Title: Access denied to admin/content/taxonomy/edit/vocabulary/* » Separate core and core optional modules from contributed modules in folders and on page
Component: taxonomy.module » other
Category: support » feature

For a module hog like me, the fact that a wealth of modules can plug up memory is a real pain in the neck.

How about alleviating the problem by allowing assignment of modules to separate folders such as Core and Contributed--even allowing admins to create and hook up their own folders? Each folder could have its own admin/build/modules page.

Of course, there is the related issue of all admin pages failing to load when the mod count climbs too high. Segregation might not solve it. But surely there must be a way have a ton of modules without getting a ton of memory.

markpenny’s picture

markpenny commented
Title: Separate core and core optional modules from contributed modules in folders and on page » Access denied to admin/content/taxonomy/vocacubary/*

Problem solved.

Database. menu_router. Change access_callback in admin/content/taxonomy/edit/term, admin/content/taxonomy/add/vocabulary, admin/content/taxonomy/edit/vocabulary/%, admin/content/taxonomy/%/add/term from 0 to user_access.

markpenny’s picture

markpenny commented
Title: Access denied to admin/content/taxonomy/vocacubary/* » Access denied to admin/content/taxonomy/vocabulary/*
Category: feature » task

Sorry. Mistyped title. I'm okay now.

Crell’s picture

Crell commented
Status: Active » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.