I have tried on 2 sites I have using Drupal 6 to install the Views module. After I upload Views to the server in the modules folder I get a "Error 500 - Internal server error". All pages in my site are either plain white, or show a page not found error (I believe this has to do with how I have my error reporting set up). In order to get my site back I have to delete the Views module and then run update.php.

Hosting service is 1and1.com. They have suggested that I need to use php5, however when I changed my .htaccess file to do so my site was down for 12 hours last night while I re-installed all of the Drupal 6 files back to the original install.

my sites are: http://batchelorfamily.org and http://azldshsa.org. They are now back to their original status.

I would really like to use the Views and Organic Groups modules. I need help getting Views to work.

Thanks~ CB

Comments

merlinofchaos’s picture

merlinofchaos commented

If you see a 500 error, there should be a corresponding error in your http error log.

Anonymous’s picture

Anonymous (not verified) commented

This is my first post, so please forgive any formatting faux pas.

Try checking your PHP memory limit. I was having the same issue after activating Views: modules page and others displayed only a white page. I noticed that a similar error occurred when I tried to install Devel #272964: White Screen when accessing module page: memory limit exhausted.

After following the recommendation to up my PHP memory limit (how-to is here), both the Devel problem and the Views issue went away.

If you don't have access to see your PHP memory_limit through your hosting service, you can create a single-line PHP file outside your Drupal path to display that info:

phpinfo();

Just navigate to that generated page and search for "memory_limit."

Good luck!

batchelor007’s picture

batchelor007 commented

There is no corresponding error in the log file.

1and1.com is my hosting service and they are not able to see any errors either.

batchelor007’s picture

batchelor007 commented

The memory limit is set to 32MB in the php.ini file.

I turned off several modules and tried to install Views again, but I still had the same "Error 500 - Internal Server Error".

Thanks for helping! ~ CB

Anonymous’s picture

Anonymous (not verified) commented

Are you trying to install Views directly on your 1and1 hosted account? The 1and1 FAQs have two conflicting pieces of info about PHP memory limits on their shared hosting:

If you can, it's always best to test your Drupal setup on a local development machine first. In this case, you can't be sure that your setting of 32M is actually affecting the configuration. If you have a Dev machine, you'll know that your settings are accurate and the problem must be something else. As it stands, you might want to check with 1and1 to find out which of their FAQ answers applies to your account.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Postponed (maintainer needs more info)

An error 500 indicates a server error, so there MUST be an error. If it's not in the log file, there are two possibilities: 1) you're looking in the wrong file, 2) the server is badly configured.

I am unable to help without knowing more about the error. As scmizer indicates, it is probably memory related. Drupal 6 is taking up more memory.

mthart’s picture

mthart commented

I'm having the same problem, but with no server error, just the WSOD.

I end up having to uninstall views-6.x-2.0-beta4 and then loading the update.php in the browser to get my site back since no matter what page I try to go to, I get a white screen.

I'm running OS X with latest version of MAMP, and Drupal 6.2.

Anonymous’s picture

Anonymous (not verified) commented

mthart, I'm also using MAMP on OSX. Have you tried adjusting your PHP memory limit, as I mention above? The default set by MAMP is 8M, which is insufficient for Drupal 6.2 + Views beta4. Mine works fine with 32M, but you might want more depending on which modules you install.

For configuring a MAMP dev machine, check out the section titled "Optional: Adjust PHP's memory limit for scripts" and in this how-to. If you're running MAMP Pro, be sure to check out the third comment, "Changing php.ini in MAMP PRO"

karens’s picture

karens commented

Might be the core bug explained at "Page Not Found" error on ALL pages of Drupal 6 website. It's another reason to use the -dev version of Drupal instead of Drupal 6.2. I've added a note to our release announcement saying you need that version of core. Once you get that result, it looks like you might want to just go back to your backup and start over.

brainanta’s picture

brainanta commented

Hi. I'm still a newbie learning Drupal 6.2 so let me know if I'm wrong.

I also experienced the same problem (error 500) after uploading Views module on my 1and1 hosted site. When I delete views folder from /sites/all/modules everything's back to normal. So I didn't run update.

I then decided to try switching to php5 from .htaccess, and the problem's gone instantly. My memory_limit was 24 and I boost it a bit from php.ini after switching to php5 (after views works).

In my case, it seems that the problem is with php 4 - the host techsupport that batchelor007 talked to might be right. Boosting memory_limit did help me fix error 500 with taxonomy_menu module though, although the browser error report showed the problem (memory overuse) unlike just bare error 500 when still running php4.

mthart’s picture

mthart commented

Ok,

Here is the best I could figure out.

I had to uninstall VIEWS to clear data, AND uninstall the 'Search' module as well as I was getting weird memory_cache errors when I tried to run update.php after setting memories limits per http://drupal.org/node/207036.

My final memory settings were to set memory_limit to 64M in php.ini, and delete the "ini_set('memory_limit', '16M');" ins settings.php.

I then reinstalled latest Views module and so far so good...

:)

jason.frazier’s picture

jason.frazier commented

Here's what I've found:

Issue:
Got same issues as above, my site was crashing on the Modules page after uploading and enabling the Views module.

Solution:
Uninstall the Administration Menu module. Views doesn't like the special admin menus (too bad, really handy). I tried this with SuperNav module and got the same 500 error.

Procedure:
1. First, to get back into the Modules page, you will need to delete or move the modules/views folder via ftp.
2. Go to Modules page. Disable all modules except core. You might have to do a few rounds of disabling and saving to get everything turned off.
3. Recommended to switch to default drupal theme.
4. Copy /views folder back to the server in /modules directory.
5. Go to Modules page. Enable Views. Save. Enable Views UI. Save.
6. The Server Error should have went away.
7. Enable modules 1 by 1. See if they crash it. If you don't get a crash, the bug is in your theme.
8. Once you know what module is messing with Views, you will need to start at step 1 again. This time, in step 2, just disable the module or modules which were crashing drupal with views.

workaround to not having an admin menu: use address bar in browser like a command line. Remember paths to things you want to do, type them in.

For example: www.example.com/?q=admin/reports/status/run-cron
to run cron

Hope this helps someone!

Edit: Sorry for the cross post, but doing the above help solve the problem on one drupal installation, but not on a different one I am working on. Checking ?q=admin/reports/status, I could tell PHP4 was being used by my host by default. I found in the host documentation a way to change the parsing engine to PHP5, and voila(!), both sites are humming.

I got one installation to work somehow with php4 by turning the memory limit waaay up to 128mb. But after switching to PHP5, site runs on 32mb no problem.

Yes, throw the stones at me now. *ducks* ;)

I found this line in the drupal system requirements a bit misleading:
Note: Drupal works with PHP 4 & 5. If you need support for the newest PHP 5.2, however, you must use Drupal 6.0 (and higher) or Drupal 5.1 (and higher)

I think it might be the other way around: If you want to use Drupal 6, you need to have PHP 5.2 installed.

It took a while to track all of this down, I hope it can at least relieve one person's confusion (other than my own)!

AJArend’s picture

AJArend commented

This is exactly the problem. I'm hosting on Verio, and they allow you to switch between php4 and php5. I've been using php4 because another script on my site requires it and errors when I try to use php5.

I've been testing "Drupal" for my site, but when I tried to install "Views," I had the internal server error when I tried to go to the modules page.

Out of curiosity, I decided to go into my site control panel and switch to php5. I was able to access the modules page with no problem at all. When I put it back to php4, the problem re-appeared.

Thanks for posting this! At least I know what the problem is now. This is a bit of a bummer, but I'm going to try and find a way around it.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Fixed

Updating status to fixed. Be sure to use PHP 5.2 or higher and set PHP memory limit to at least 16MB, per the http://drupal.org/requirements">Drupal System requirements (see the PHP section).

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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