"Invalid display ID" message

Well, clearly you've found a bug. I'm...not sure what it is, though.

What version of PHP are you running?

I had the same problem on a fresh D6 final install testing Views 2 alpha 2 out of the gate a few hours ago. I checked and noticed I was running PHP4 on the test install. I switched it to PHP5 and the problem went away. So whatever the problem is, it was with PHP4 for me.

- Guy

Ugh. I don't currently have a PHP4 platform running a high enough MySQL version to test with. It wouldn't surprise me, though, if there were a problem with object references, as PHP5 is really...lax about that and PHP4 isn't.

Yeah, with the death of PHP4 happening currently, it won't surprise me to find all sorts of problems in the Drupal 6 world having to do with PHP4. Honestly, I didn't realize my test install was even on PHP4, and didn't intend to do that. So, it's not an issue for me. Just happened to also notice the issue and that it went away with PHP5. I imagine most D6 users are going to be using PHP5 these days (or at least I'd think). If not, they'd probably wanna consider it given the number of contribs that are probably gonna start having problems under PHP4, given that most active dev is probably happening on PHP5 from here out. It's gotta be a massive pain for the poor devs out there to have to consider reactions that various versions of PHP & MySQL will have to things. Yuck. ;-)

Nono, the issue isn't closed.

If I can't get the PHP4 code working, then I can set requirements in the info file, so it won't be a problem. I fully intended to be PHP4 compatible, but I've run into some referencing problems and they are not going to be easy to fix.

all cache interactions happen in cache.inc -- open the file and search for views_default and you should find it.

Subscribe, same message.

fresh install of 6.1 and same error

Invalid display id

I am using PHP4 and have same problem.

Yea, this is a problem with PHP4 and I am not 100% sure if it is fixable. Will have to see but prepare for the possibility that I may be forced to declare that views is PHP5 only. =(

I also had this error, switched to php5 and that solved it.
My ISP has PHP4 set as the default BUT allows you to switch to PHP5 by adding a line to your .htaccess file.
Might check with yours for that option too.

My hosting service allows both...! =] Problem fixed.

You can test and see if your server allows php5 by adding this to your .htaccess

AddType application/x-httpd-php5 .php
AddHandler application/x-httpd-php5 .php

Good luck!

I am seeing a lot of errors on PHP 5.2.5, would it be useful for me to report them or are they already known?

Invalid display id
Error: Display refers to a plugin named '', but that plugin doesn't exist!

and then when I reloaded:
Fatal error: Class name must be a valid object or a string in /home/d6/contributions-HEAD/modules/views/includes/handlers.inc on line 13
Call Stack
# Time Memory Function Location
1 0.0002 90400 {main}( ) ../index.php:0
2 0.1087 16203288 menu_execute_active_handler( ) ../index.php:18
3 0.1192 17470472 call_user_func_array ( ) ../menu.inc:346
4 0.1192 17470800 views_ui_edit_page( ) ../menu.inc:0
5 0.1232 18272456 theme( ) ../admin.inc:209
6 0.1234 18272712 call_user_func_array ( ) ../theme.inc:632
7 0.1234 18272800 template_preprocess_views_ui_edit_view( ) ../theme.inc:0
8 0.1368 18838608 views_ui_display_tab( ) ../admin.inc:378
9 0.1368 18838608 theme( ) ../admin.inc:519
10 0.1370 18841280 call_user_func_array ( ) ../theme.inc:632
11 0.1370 18841368 template_preprocess_views_ui_edit_tab( ) ../theme.inc:0
12 0.1460 18932632 views_get_plugin( ) ../admin.inc:489
13 0.1460 18932632 _views_create_handler( ) ../views.module:482
And I have loads more debugging info like variables in local scope...

mfb: See http://drupal.org/node/232905

The PHP 4 problems should be fixed. I believe this problem should be completely fixed as of alpha3.

I am running the Beta1 and am currently getting the "Invalid display ID message". My server runs PHP 4. Is the error back? It seems like it was fixed in Alpha3

No, this is something new and different and already reported: http://drupal.org/node/223565

LOL merlin, your last comment refered to the same node:) Anyways, just around searching for a solution to my problem (which is simular).

Dont think I am running PHP4, but if you want

+1 to leaving php4 (edit... Put PHP5 instead) in the dust! Hey Zend wont support it, why should we! (now I just have to make sure php5 is running)

Mike

I had this too today.
I was doing some crazy stuff inside Views ... (deleting displays, putting them back , deleting them again... was trying something out)
after a while it became too much for Views and it threw me the above error. The "removed" display still had an entry in the display list with the name "invalid"

I know this probably isn't a solid solution , but removing one of the other displays (and later putting it back) also got rid of the "Invalid" display.
It seems that the "remove action" on the other display took care of the pending "invalid" display.

Damn , I must get some sleep :)
Just my 2 cents,

Sunchaser