installed drupal 5.1 everything is working fine.
I uploaded a new module (cck). when i was accessing the admin page i got a "page cannot be found" error (not the 404 error by drupal). same at the update.php . no problems at the frontend.
I deleted the module again per ftp an everything is working again. but i cannot even install cck (i got the right version) cause i cannot reache the module admin page.

Comments

docdor’s picture

docdor commented

more info:
Drupal 5.1
Configuration file Protected
Cron maintenance tasks Last run 10 min 30 sec ago
You can run cron manually.
Database schema Up to date
File system Writable (private download method)
GD library bundled (2.0.28 compatible)
MySQL database 4.1.20
PHP 4.3.9
Unicode library PHP Mbstring Extension
Web server Apache/2.0.52 (CentOS)

moshe weitzman’s picture

moshe weitzman commented
Priority: Critical » Normal

i can't reproduce this. downgrading.

jasio’s picture

jasio commented

I have a very similar problem both on my testing and "to-be-production" sites. Installing CCK made admin pages unavailable. The only difference is, that I don't get an error message, but the page in a browser freezes. If I now switch to another window and go back to the browser, the page appears to be blank. Page source is empty. The same issue happened also with some other modules as well (views, addressbook).

I can actually access some of the admin functions entering their direct URL's, and if a particular page is live - further navigate using menu.

I have not checked whole administration system of my production site, but:
admin -> locks
admin/content/types -> 500 Internal server error
admin/build/block -> locks
admin/build/menu -> locks
admin/build/modules -> locks
admin/build/themes -> locks
admin/settings/admin -> 500 Internal server error
admin/settings/locale -> locks
admin/user/access -> locks
admin/logs/watchdog -> locks
admin/logs/page-not-found -> locks
admin/logs/status -> locks

Other administration pages are available and at least some of them seem to function properly (I have not checked it THAT deep).

Additional modules activated in ./sites/all/modules:
CCK (seemed to cause a problem)
FAQ

Additional modules inactive in ./sites/all/modules:
poormanscron

Additional modules activated in .modules:
nodewords

Additional modules inactive in ./modules:
addressbook (seemed to cause similar problem, but the modules page was active, so I deactivated it, though not deleted)

Production site configuration:
Linux 2.6.17-2-686 #1 SMP
Drupal 5.1.
PHP Version 4.4.4-6,.
Apache version: unknown.
Server API CGI/FastCGI
memory_limit 8M

Test site configuration:
Linux 2.6.16.27-0.9-default
Drupal 5.1.
PHP Version 5.1.2.
Apache/2.2.0 (Linux/SUSE)
Server API Apache 2.0 Handler
memory_limit 8M

I hope, that helps.

PS. If you need it, I can dump whole phpinfo pages for you.

--
Best regards,

(js).

jasio’s picture

jasio commented

I checked logs on my test site (I don't have admin access to the production site, which is hosted), and found:

"PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 14592 bytes) in /srv/www/htdocs/drupal/sites/all/modules/cck/fieldgroup.module on line 191, referer: http://localhost/drupal/?q=admin/build/modules"

I allocated more memory (16M, as drupal requires) and it seems, that it fixed the problem, at least locally.

ricabrantes’s picture

ricabrantes commented

i can't reproduce this. Any news?? I used D5.x-dev

cat ivan’s picture

cat ivan commented

same here with D6.2 and cck-6.0-beta.
module admin page is completely blank
removing cck folder from modules fixes this

kjv1611’s picture

kjv1611 commented

I had a similar issue and tried all sorts of fixes with the .htaccess file as suggested in other places.

I'm using D6.4, cck tried both the stable release as of today, and the dev release.

I took cat's advice, and just deleted the whole cck folder, and everything else is working fine.

I'd like to use that module, as I've read many good things about it, but it isn't worth having part of the site just shut down.

If anyone has any updates/hints/help/ideas on this, I'd be most appreciative!

Thanks for anything. :)

kjv1611’s picture

kjv1611 commented

I think fixed - I had accidentally renamed the .htaccess file to htaccess
..then I found another problem, but fixed it by upping the memory limit in the php.ini file to 64M

kjv1611’s picture

kjv1611 commented
Version: 5.1 » 6.4
cor3huis’s picture

cor3huis commented
Status: Active » Closed (cannot reproduce)

Since CCK is not in D6 core and I can use latest CCK just fine with Drupal v6.4 and now Drupal v6.20 will change the status. Not said there can be no such issue, however the issue is open for a long time without original reporter adding information. Also in the mean time user kjv1611 change the version where the issue should be.