By mason on

I'm getting a "Zero Sized Reply" when I try to get to my modules admin panel (which in my case is located at "http://provopulse.com/home/?q=admin/system/modules").

This started happening after I tried tweaking event.module I don't understand what happened, but I was tweaking the event.module and user.module.

I'm running Drupal 4.4.1 with event.module 4.3.1 (but I've also tried updating event.module to 4.4.0)

The only changes I made were these:

$ diff user.module user.module_022405 
443c443
<           $result = db_query_range("SELECT uid, name FROM {users} WHERE status != '0' ORDER BY uid DESC", 0, 6);
---
>           $result = db_query_range("SELECT uid, name FROM {users} WHERE status != '0' ORDER BY uid DESC", 0, 5);

and:

$ diff event.module event.module_022505 
49c49
<           $block['content'] .= "<div class=\"more-link\">". l(t("see more"),"event", array("title" => t("More events."))) ."<br><br><a href=\"http://ProvoPulse.com/home/?q=node/add/event\"><i>list your event</i></a><br><br></div>";
---
>           $block['content'] .= "<div class=\"more-link\">". l(t("more"),"event", array("title" => t("More events."))) ."</div>";
755c755
< function event_block_upcoming($limit = 8) {
---
> function event_block_upcoming($limit = 6) {

I also tried reverting back to the original versions of both of these files but I still have the same problem.

Any ideas?

Comments

gsarwohadi’s picture

gsarwohadi commented

Yeah,.. I get the same problem and a friend told me it's more likely a webhosting problem (something about Squid)... So, you should consult with your webhosting CS.. I myself haven't had the chance to get hold with my webhostings CS.. so.. maybe you can try your luck :)

twom’s picture

twom commented

Hy,

Do you all still have this problem? Today I transfered my drypal site (from windows pc) to a linux machine, and I get the same problem while trying to acces the administer/modules. Tomorrow I will ask the system administrator to help me out, but are there already any clues regarding this problem? Look at the server or better look at the code?

twom’s picture

twom commented

The problem is due to memory limitations set in php.ini. The following deals correctly with the problem: http://drupal.org/node/29786