By Simon Pole on

I have just installed a new module, and am unable to access the module node from the menu or explict url. All other nodes work fine. I'm not sure if adding the new module has caused the problem, because I hadn't tried to access the module node in a while.

On Mozilla, trying to access the module node doesn't give any message, it just doesn't load. Trying to load the module with lynx, gives the warning "access denied."

Any idea what is blocking access to the module node?

Comments

sami_k’s picture

sami_k commented

Just go in and delete the module that you enabled when the problem began. Drupal will no longer execute the code and problem will be solved.

--
Read the handbook, search the forums, then ask!
http://drupal.etopian.net (Consulting, Development, and Hosting)

Simon Pole’s picture

Simon Pole commented

I deleted the module and everythings fine now. Thank you.

adlitinc’s picture

adlitinc commented

after installing taxonomy_dhtml on drupal 4.6.1. it would simply not work

adlitinc’s picture

adlitinc commented

I've installed the taxonomy_dhtml and modules would not longer be accessible. I've removed the taxonomy_dhtml and it's still not accessible.

This trick worked last time but not any more I guess

adlitinc’s picture

adlitinc commented

I took out taxonomy_multi_edit and now I'm able to get in

adlitinc’s picture

adlitinc commented

I've been trying to add taxonomy_dhtml but I am unsuccessful, so I've tried installing a different module but that has the same effect, administer> modules will then be inaccessible.

I remove the one module I just installed and everything is fine. I add another different module (pathauto-4.6.0.tar.gz) and voila.. modules is inaccessible

I'm baffled, does anyone have an idea why? It's not the permission, I've chowned the module dir everytime I installed a new one.

Millman’s picture

Millman commented

I'm having a similar problem and can no longer access my 'modules' administration page, even after deleting the 'offensive' module which caused the page to be inaccessible. I've heard editing php.ini and making the memory size bigger (ie. 8mb -> 16mb) should fix your problem, but it didn't work for me.

adlitinc’s picture

adlitinc commented

as soon as try to install 1 other module, the admin for modules no longer works and I'm trying to install other modules for taxonomy and also flexinode and banner

Does any one have an idea on what to do ?

These are under the module directory

aggregator.module
archive.module
article
block.module
blogapi.module
blog.module
book.module
comment.module
contact.module
drupal.module
event
fckeditor
filter.module
forum.module
help.module
legacy.module
locale.module
location
menu.module
nodelist
node.module
page.module
pathauto
path.module
ping.module
poll.module
profile.module
queue.module
search.module
sections
statistics.module
story.module
system.module
taxonomy_browser
taxonomy_dhtml
taxonomy_menu
taxonomy.module
taxonomy_multi_edit
throttle.module
tracker.module
upload.module
user.module
watchdog.module

these I have turned on in the admin panel:

aggregator
archive
article
block
blog
event
fckeditor
filter
help
location
menu
node
nodelist
page
path
pathauto
queue
search
sections
statistics
story
system
taxonomy
taxonomy_browser
taxonomy_dhtml
taxonomy_menu
taxonomy_multi_edit
user
watchdog

sepeck’s picture

sepeck commented

Increase the memory in your php.ini

Be default, a Drupal site only loads those modules it is using for various page views. The modules page, in order to work, loads all the modules on the page into memory. If your memory (referenced in an earlier responce) is insufficient to fit all the modules you have on your site, then you will be unable to load the page.

If you cannot increase the memory in your php.ini, there are some htaccess of settings.php tricks (I don't use Apache) elsewhere on Drupal (search) that can hep you. One other work around is to remove modules you do not have turned on.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

adlitinc’s picture

adlitinc commented

that did the trick. I've added:

php_value memory_limit 128M

to the .htaccess file and it's now working

Thanks

rlorenzo’s picture

rlorenzo commented

I have a fresh copy of 4.6.2 and I cannot access the "module" section. It just doesn't load anything and no error message from FireFox.

I just have the default modules:

aggregator.module drupal.module page.module story.module
archive.module filter.module path.module system.module
block.module forum.module ping.module taxonomy.module
blog.module help.module poll.module throttle.module
blogapi.module legacy.module profile.module tracker.module
book.module locale.module queue.module upload.module
comment.module menu.module search.module user.module
contact.module node.module statistics.module watchdog.module

I have also tried increasing php_memory to 128M, but it is still a no-go.

emotionlovesyou’s picture

emotionlovesyou commented

I can't find a php.ini file on my server and I don't know which .htaccess file to make the changes in question to since I have several in several different directories on my server. Does anyone know what directory to find these files in?

bilgehan’s picture

bilgehan commented

Yesterday I configured the cron job and since then I can't access the module node. I get this error in logs section:

Lost connection to MySQL server during query query: UPDATE sessions SET uid = 1, hostname = '81.33.156.174', session = 'og_last|N;messages|a:0:{}watchdog_overview_filter|s:3:\"all\";', timestamp = 1121444519 WHERE sid = 'f50b3587d8359fd0ce860af63fb5ea1f' in /datos/home/ispanyal/public_html/includes/database.mysql.inc on line 66.

jaskegreen’s picture

jaskegreen commented

Just thought I would add what I found. I started a new modules directory with the included modules. As I added more one at a time, I found that the Donations mod was the one causing the problem. Hope that helps someone else.

Jason
JC SWAK - web hosting & design
www.jcswak.com

jaskegreen’s picture

jaskegreen commented

Well, now I'm having problems again. I've increased the memory size in php.ini and followed all of the advice that I could find here and on Google. Does anyone have a solution to this problem?

Jason
JC SWAK - web hosting & design
www.jcswak.com

LordMerlin’s picture

LordMerlin commented

Funny, the same thing happens to me, with a fresh installation of Drupal. I can't access the Modules Menu as administrator. I increased the memory in php.ini to 100M (default was 8M), and I still can't access them, even though I deleted the whole drupal installation & DB and reinstalled it.

Drupal, in my opinion is very unstable, and though it seem like it's got some good "points", I have yet to discover them. The DB layout is flackey, the code is unstable, and I can't really afford to have these kind of problem in a production environment

OnFairyWingsDesigns’s picture

OnFairyWingsDesigns commented

I am having the same problem. I have deleted a bunch of mods, but still can't access the modules admin. I have checked my error logs and it shows that this is the problem:

Premature end of script headers: /home/******/public_html/index.php

Doe anyone have any ideas?

Thanks in advance!

Heather

*~*~*~*~*~*~*~*~*~*

3JCB Designs ~ Professional Services at Affordable Prices

Web/Graphic Design, Web Hosting, Domain Registration, and More.

http://www.3jcbdesigns.com