By marlowe on

I don't know what is happening. I cannot access to the page of modules administration (it appears a blank page). Could be a problem with upgrade to 4.5.1 version?

thanks..//

Comments

media girl’s picture

media girl commented

The obvious one is making sure you did a text-based ftp, not binary. I also remember that some people had troubles with the total upgrade if they did not clear the cache. As it turns out, in upgrading from 4.5.0 to 4.5.1, all you have to do is ftp the modules and includes, since there were no changes in the database. Hopefully one of these things will help.
--
mediagirl.org

marlowe’s picture

marlowe commented

Uploaded the upgrade again (in text mode) but the problem is the same. Thank for the suggestion.

ezheidtmann’s picture

ezheidtmann commented

Is there anything showing up in your server logs or Drupal's watchdog?

marlowe’s picture

marlowe commented

Nothing in drupal log and this in server log

[Mon Dec 27 00:32:33 2004] [info] [client 217.159.201.131] (32)Broken pipe: client stopped connection before rwrite completed
[Mon Dec 27 01:33:02 2004] [info] [client 217.159.201.131] (32)Broken pipe: client stopped connection before rwrite completed
[Mon Dec 27 02:34:08 2004] [info] [client 217.159.201.131] (32)Broken pipe: client stopped connection before rwrite completed
[Mon Dec 27 03:33:34 2004] [info] [client 217.159.201.131] (32)Broken pipe: client stopped connection before rwrite completed
[Mon Dec 27 05:32:20 2004] [info] [client 217.159.201.131] (32)Broken pipe: client stopped connection before rwrite completed
[Mon Dec 27 05:47:36 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:47:36 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:06 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:07 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:08 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:08 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:13 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:32 2004] [debug] mod_rewrite.c(1633): [client 200.41.42.130] mod_rewrite's internal redirect status: 0/10.
[Mon Dec 27 05:49:33 2004] [info] [client 194.224.199.47] (110)Connection timed out: client stopped connection before rwrite completed

Any Idea?

Dublin Drupaller’s picture

Dublin Drupaller commented

Wild stab in the dark this, but, try deleting the mod rewrite module in your modules folder...and then try going to the administer -> modules page

I notice all the errors in your log are related to mod_rewrite.

Hope that heles

J

Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate

marlowe’s picture

marlowe commented

Ouuuch!! You are talking about apache mod_rewrite? I´cant access that, I´m on a web hosting provider

Dublin Drupaller’s picture

Dublin Drupaller commented

HI Marlowe...

I see....my mistake....I thought there was a mod_rewrite.module for drupal..obviously not.

Anyway..maybe worth trying the following to access your administer modules page:

1. Go to ADMINISTER -> SETTINGS

2. Switch off clean urls.

3. Save Configuration

4. now try accessing your ADMINISTER -> MODULES page

Hope that helps..although, I'm not sure why you are able to access other areas of the site and unable to access the modules page.

Usually when that happens to me, it's because I have uploaded a module to the drupal/modules folder that is not the correct version (i.e. cvs as opposed to 4.5 for example) or I have incorrectly uploaded the module (i.e. in Binary mode as opposed to ASCII for example)

Jason

Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate

marlowe’s picture

marlowe commented

The other areas works fine. I guess the problem could be the ftp upload. I will try upload all files again. Thanks..

marlowe’s picture

marlowe commented

The problem is the weblink module, after delete the folder, the module admin page works fine...

marlowe’s picture

marlowe commented

Very simple solution, just put the value php_value memory_limit "16M" in htaccess.

pougas’s picture

pougas commented

You are great!, same problem with the modules page and i turn off the clean urls and now its working great

ty a lot

brainiacPol’s picture

brainiacPol commented

I couldn't access the modules page...
there're lots of tips on how to fix this problem none of them work... I thought i was screwed but it worked ;)
btw: i have v6.x
thanks thanks thanks ;)