Hello,

I am trying to use the nodequeue module in my Drupal installation and after I enable it, my admin/build/modules will no longer load. I get the following error from Firefox:

File Not Found

Firefox can't find the file at http://mydomainname.com/drupal-6.6/?q=admin/build/modules.

* Could the item have been renamed, removed, or relocated?
* Is there a spelling, capitalization, or other typographical error in the address?
* Do you have sufficient access permissions to the requested item?

The only way I can get that page to display again is by going into the database and flipping the status of the nodequeue module to 0 in the system table.

Am I doing something wrong?

Thank you for your help.

Comments

ezra-g’s picture

ezra-g commented

Try clearing the cache at admin/settings/performance.

Are you using Rc3 for sure, or are you using the dev snapshot? According to project usage stats, 363 sites have rc3 installed, so i'd be surprised if nobody reported this.

NidSquid’s picture

NidSquid commented

Hi,

Thanks for responding. I'm pretty sure I'm using the RC3 version (nodequeue-6.x-2.0-rc3.tar.gz is the name of the file I downloaded).

I cleared the cache before and after enabling the module and I still see the same problem. On an odd note, when I tried to clear the cache I initially just got a blank page but when I refreshed Drupal told me the cache was cleared successfully. When I try to load the page to clear the cache again it goes intermittently between showing me a blank page and working properly.

And also, I tried refreshing the admin/build/modules page a few times - once I saw a completely blank page, otherwise it's just the error as I described in my original post.

And I did search the forums before posting and I didn't see this problem reported by anyone else either.

I'm using Drupal 6.6.

What other information should I provide that could be useful to you? Should I just try using the dev snapshot?

Thank you.

NidSquid’s picture

NidSquid commented

Update: Same behaviour with the dev snapshot.

ezra-g’s picture

ezra-g commented

Can you read your PHP/apache error log? is there any info in there around the time you get the "blank screen" after clearing the cache and also when you get the not found error at admin/build/modules?

ezra-g’s picture

ezra-g commented

The fact that you get firefox's 404 page rather than drupal's suggests that drupal is crashing. I wonder if your problem is similar to the one that this user in the forums is having.

NidSquid’s picture

NidSquid commented

I will check the error logs (shared hosting makes the error logs a pain to get to sometimes but I will dig them up). I also wonder if I am running into a PHP memory limitation with Drupal - I will also try upping my memory limit (man, I hate shared hosting sometimes :-)).

I saw that other user's issue when I was searching for a solution to the issue (before I posted here) - the difference seems to be that he/she was actually using the nodequeue module with some queues enabled and they tried to turn it off. For me, as soon as I enable the module, Drupal chokes. But it is possible that they are related. I will research and post back with updates.

Thanks for responding.

NidSquid’s picture

NidSquid commented

Hi,

The problem is solved. PHP exceeded my hosting account's memory limit when I tried to activate nodequeue module. My host upped it for me and it is working now.

Sorry to have bothered with this issue - it was on my end.

BTW, this module is really cool and very helpful to me, so thank you very much.

ezra-g’s picture

ezra-g commented
Status: Active » Fixed

No problem. Glad that you got this resolved. Thanks!

Status: Fixed » Closed (fixed)

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