Hello,

Something is dreadfully wrong with my Views installation. My other modules (such as CCK, fckeditor, IMCE, etc.) are working fine. When I try to enable the Views module I get the message below:

Fatal error: Call to a member function override_option() on a non-object in /home/take9630/public_html/daraio/sites/all/modules/views/modules/comment.views_default.inc on line 22

I did try to migrate my install from another site, so I suppose this could be the problem. I re-created the site using a new database, but ftp'd the site files from my local install to the web server. (Updating settings.php as necessary)

I may try another install and will send updates.

Comments

ssutankayo’s picture

Drupal install information for bug report above.

Drupal 6.4
Access to update.php Protected
Configuration file Protected
Cron maintenance tasks Last run 21 min ago
You can run cron manually.
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
Module and theme update status Up to date
MySQL database 5.0.51a
PHP 5.2.6
PHP memory limit 32M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Web server Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635

ssutankayo’s picture

I have verified this error on a new drupal install.

syrabo’s picture

I have this problem with simplenews since the update Views to last version; deactived views simplenews works.

Fatal error: Class 'views_handler_field' not found in /home/wurzelstein/www/sites/all/modules/simplenews/simplenews_views.inc on line 52

merlinofchaos’s picture

syrabo:

sites/all/modules/simplenews

That's the simplenews module. Not only did you add your info to an unrelated issue, which confuses the original issue, you're not even in the right queue. Simplenews either needs to be deactivated or upgraded, as it's incompatible with API changes made for Views RC2.

ssutankayo: Very strange. The error suggests that for some reason the default display isn't being created for some reason. I haven't been able to come across this error myself, so I'm not at all sure what's causing it. I'll need to try a fresh install and see if I can reproduce it somehow.

The only guess I have that you could look at is to look in the views/plugins directory and make sure views_plugin_display.inc and views_plugin_display_default.inc are there.

ssutankayo’s picture

Hey thanks! It works now. What happened was that because some of the Views module filenames were particularly long, my ftp client (Dreamweaver, never to be used again) mangled the filenames. Or I suppose it could be the ftp server's fault.

Anyway thanks for catching this, it's never happened to me before.

ssutankayo’s picture

Status: Active » Closed (fixed)

attempting to close status...

MoonchildCH’s picture

"... because some of the Views module filenames were particularly long, my ftp client mangled the filenames. Or I suppose it could be the ftp server's fault."

I have the same error, and discovered that many of the filenames in my views/plugins folder are truncated. Where can I get a list of correct filenames?

merlinofchaos’s picture

You can find all the correct filenames in the CVS system: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/views/

MoonchildCH’s picture

Thanks! I will need this because it's causing another problem now. My "handler doesn't exist" error stemmed from shortened filenames in the views/handlers folder. I'm going to go check all the views directories now. Thanks for putting this first thing in the README!

csosalanz’s picture

Interesting how there are multiple postings of this issue but only this thread mentions the truncation issue. I was hitting it with an old version of Fetch 4.0.1 Maybe it's my fault for not updating, but i had never had an issue with it in the past. Switched over to FileZilla.