Closed (fixed)
Project:
Panels
Version:
5.x-2.0-beta3
Component:
Panel pages
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
29 Apr 2008 at 10:18 UTC
Updated:
1 Oct 2008 at 07:21 UTC
Hi,
Since several days, I have an internal server error when I try to change the content of my panels or to change the layout settings.
I removed the module. re-install-it or install an other version.
No difference.
I've contacted my server host company and they said that they don't see any bug.
I know that I've installed lots of contributed modules. I'll disable one by one those modules. But before this fishing strategy, I wanted to have your opinion.
Thanks
Ben
Comments
Comment #1
sdboyer commentedPlease describe the sequence of events in more detail. You're able to view the panel display, but when you click on the edit content or layout tabs, you get the ISE? Or, is it when you try to save the changes you've made on either of those forms?
Also, is this an actual ISE, as in white page, "Internal Server Error" at the top, with some explanatory text below? If so, please copy/paste that text in its entirety here, just for reference.
Comment #2
sunWithout further information, we should guess this issue is no longer critical and already fixed.
Comment #3
blooksllc commentedI get internal server errors as well, every time I update views, or update module settings. I uninstalled panels and the error went away. I am not having page memory issues, already checked that.
Modules Installed:
Request Invitation
CCK
CCK Address Fields
CCK Field Permissions
CCK Computed Field
CCK Content
CCK Content Templates
CCK Date
CCK Email
CCK Field Group
CCK Link
CCK Node Reference
CCK Number
CCK Text
Core Comments
Core Help
Core Menu
Core Path
Core Taxonomy
Invite
Node Factory
Date API
Pathauto
Simple Paypal framework
Token
CAPTCHA
reCAPTCHA
JQuery Update
Views
Views Theme Wizard
Views UI
Extra Voting forms
Voting API
Workflow-ng
Workflow-ng UI
Custom No duplicate titles module
Custom Node Regeneration module
Customization of Donation module
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
bneel commentedIn fact, during a upgrade of drupal 5.5 to 5.8, I disallowed all modules before upgrade, than I upgreated durpal, and finally I re-activated my modules. This error disapear.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.