After I add a view this is the error I get:
////////////
This view has a broken default display and cannot be used.
Changed viewView ListView, displaying items of type User.
Error: Display refers to a plugin named '', but that plugin doesn't exist!
//////////////

I am trying to make a block display - I have also tried page display and I still get the errors
Any help would be greatly appreciated.

I have tried several scenarios and they all error out like this.

Comments

jcbrew’s picture

jcbrew commented

Additional Info:

//After clicking on "Tools" this is the warnings I get:

warning: Missing argument 1 for drupal_get_form() in C:\Inetpub\vhosts\***\httpdocs\includes\form.inc on line 69.
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '' was given in C:\Inetpub\vhosts\***\httpdocs\includes\form.inc on line 358.

//Content Under List > Operations > Export:
$view = new view;
$view->name = 'ListView';
$view->description = 'ListView';
$view->tag = 'View';
$view->view_php = '';
$view->base_table = 'users';
$view->is_cacheable = '0';
$view->api_version = 2;
$view->disabled = FALSE; // Edit this to true to make a default view disabled initially
$view->display = array();

merlinofchaos’s picture

merlinofchaos commented

Hmm. That indicates the default display is somehow not being saved correctly. Do you get any PHP errors prior to seeing that message?

Do you have a 'views_display' table in your database?

(The error under the tools tab is irrelevant to this; the tools tab isn't implemented)

RoboPhred’s picture

RoboPhred commented

Same error. It started occurring after I updated to the most recent cvs version.
The error occurs even with the bare minimal of creating a view, and submitting the options page without actually changing anything.

jcbrew’s picture

jcbrew commented

Yes, using phpMyAdmin I was able to confirm that views_display is in my database.

merlinofchaos’s picture

merlinofchaos commented

Are you using PHP4 or PHP5?

jcbrew’s picture

jcbrew commented

PHP5

merlinofchaos’s picture

merlinofchaos commented

Any existing views you have are likely to remain screwed up pretty much forever; does this continue to happen when you make new views?

jcbrew’s picture

jcbrew commented

Yes, I have not been able to add any views at all. I just installed the module.

More info that might help:
I am using a Windows machine with IIS, MySQL 5 and PHP 5

jcbrew’s picture

jcbrew commented

Hi - Could you let me know if you are able to fix this issue... I haven't had much luck with support on these forums.

Thanks

I'd hate to start using a .Net solution, but there seems to be more help with Windows programming languages.

RoboPhred’s picture

RoboPhred commented

For the record:
MySQL 5.0.45
PHP 5.2.5
Apache 2.2.6

Using WAMP server on a home pc for testing.

The problem probably is in saving the view. I made a view with the new version, then as a test reverted to the Feb 21 version of the cvs and the created view was still broken. I deleted it and made a new one, which worked properly.
I will step through versions and try to find the one where the error starts occuring.

Update:
I created a view with the 10 March 2008, it worked fine.
I updated the view module to the 11 March 2008 version. A new view failed to save with the error in the first post here.
Interestingly enough, the view created from the 10 March version still works fine, and I can edit/save it properly.

I have not tested them actually functioning as they should though.

I will try to get a more accurate location of the commit it broke at, but I have yet to find how to do this in cvs.

RoboPhred’s picture

RoboPhred commented

I found the error occures on includes/views.inc version 1.40, but not on 1.39. Will continue poking at it.

Update:
The issue appears to be these two changes:

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/views/inclu...

Reverting those changes on an up to date cvs copy fixes the issue.
I tried reverting only one of the two changes, and it still fails as long as at least one of those changes are present.

merlinofchaos’s picture

merlinofchaos commented

ARgh. Argh I say.

jcbrew’s picture

jcbrew commented

I'm impressed.... That got it to work. Thank you!

yched’s picture

yched commented

FWIW, reverting to views.inc 1.39 didn't work for me.
What *did* work was emptying the content of the {views_obect_cache} and {views_display}tables.

I can now save views with current CVS code.

usidobn’s picture

usidobn commented

Hi

Same problem with the version of 11 and 13 march. (PHP5, WAMP, Windows)
Return of the alpha2 for me, which work.

Good luck.

RoboPhred’s picture

RoboPhred commented
Component: Miscellaneous » Code

I tried emptying those two tables on a fully up to date cvs and the error still occurred. Maybe these are two different issues?

merlinofchaos’s picture

merlinofchaos commented

When this happens, do you get some kind of error in your apache/php log or the watchdog log as well?

usidobn’s picture

usidobn commented

There are not entries save by the dblog module and apache/php log... :-/

jcbrew’s picture

jcbrew commented

I am using Windows/IIS

merlinofchaos’s picture

merlinofchaos commented
Category: support » bug
Status: Active » Fixed

Ok, figured this one out. I just checked in a fix for it, should roll up in next -dev.

karens’s picture

karens commented

Works great now. Thanks!

Anonymous’s picture

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

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