After upgrade from 6.x-2.2 to 6.x-2.3, can't edit views

This bug is confirmed on my setup too.

This appears to be a duplicate of http://drupal.org/node/370946 (?)

I can confirm what is perhaps the same difficulty.

When adding a new field, a JS error appears, and update fails.

On canceling the update, the new field is actually present; the error apparently gets triggered after the add and before the configure field step.

For fields involving relationships, this means the relationship doesn't get set properly, and subsequent efforts to edit the field configuration fail (error and perpetual whirligigs on the field line).

However, if I click to re-order fields, that will sort of correct things for the fields that were whirligigs. Subsequent edits for those fields seem to work, but the references for those fields in the Views pane remain incorrect (the references given in the reorder fields selector are correct).

I can confirm too.

I am also not able to create new view.

When I clik ADD, then fill in basic info, I proceed to views form, where I can edit with some problems (after several clicks I get ajax js error) and settings do not get saved. Moreover after clicking save button I get error Page not found.

After upgrade from Views-6.x-2.2 to Views-6.x-2.3, all edit to views doesn't take effect.

This is the most useless bug report I've ever gotten.

#2: When you get the js error, can you tell me what the js error is? I have so far been unable to duplicate any of this behavior on my test system.

After I upgraded from 2.2 to 2.3, I ran update.php and got this error:
"The update process was aborted prematurely while running update #6002 in views.module. All errors have been logged. You may need to check the watchdog database table manually."
I also have an error in my Status Report:
"Database updates Out of date Some modules have database schema updates to install. You should run the database update script immediately."

I found a thread stating that the views_object_cache.data field should be a LONGBLOB.
http://drupal.org/node/295246#comment-1186206 Checked my database, and it was a BLOB. I changed it, but that didn't help.

When I first did the update, I had this in my error log:
Details
Type php
Date Saturday, February 14, 2009 - 20:44
User [user]
Location [base url]/admin/build/views/edit/MyEvents
Referrer [base url]/admin/build/views
Message Invalid argument supplied for foreach() in [base url]/sites/all/modules/views/includes/admin.inc on line 1226.
Severity error
Hostname [ip]
Operations

No errors have been logged since then, but I still can't edit my views. When I try, I get:
"An error occurred at [base url]/build/views/ajax/[rest of path]"
When I roll over those links, the status bar shows something different:
"[base url]/build/views/nojs/[rest of path]"
This is true for all the settings, whether I try to add or edit views.

I fixed the update problem by uninstalling all but the core modules, reinstalling Views 2.3 and running update.php. It did change the views_object_cache.data field--to LONGTEXT. I've reloaded all the modules, and everything seems to work fine now. I'm wondering how much of my problem was caused by my outdated Mac (OS 9), because I still can't edit views on it. Did I not clear a cache enough times somewhere? I had no problems with previous Views versions on my Mac.

Sorry, Merlin, I had to migrate to a clone environment before I played with this any more.

Here's what I do to replicate. Install the 2.3 upgrade. Run updates 6002 for views. No problem. ("ALTER TABLE {views_object_cache} CHANGE data `data` LONGTEXT DEFAULT NULL")

Select a pre-existing view. Attempt to add a field to the view which requires a relationship. For example, in a users view that references a Content Profile node, attempt to add the name field from the content profile node. Select field, click Add. This results in a relatively generic Firefox alert box:

"The page at http://site.com says:

An error occurred at http://site.com/admin/build/views/ajax/add-item/user_profile/default/field"

After acknowledging the error box OK, clicking on "cancel" instead of add returns me to the primary views edit screen, and the field is actually listed. However, as was pointed out above, selecting that field for editing causes additional problems.

This error seems to occur only when selecting a field which is based on a relationship. That is to say, in a users view selecting a users field like email or roles adds normally.

Hope that helps a bit. I'm running Firefox 3.0.5 on an Intel Mac if that matters.

Ok, for those getting this error, can you try the -dev version? The part of the code that should care about it being a BLOB has been, I hope, fixed, but it's difficult for me to confirm.

Downloaded and installed the Feb 18 dev. Same problem still exists. The site I'm working on is mostly views set up with user->node relationships from Content Profile, and these fail uniformly in Views 2.3. I haven't been thorough in tracking what other relationship combinations also have problems but will try to map it out a bit tomorrow.

If it is only the content profile relationship that fails, then this might be a bug report for that module. When you see that box about a server problem, check your apache/php error log. Usually this indicates a server crash and the ajax can't really tell what happened.

Had to set this aside for a while to work on other things. Coming back to it now on a 6.10 fully updated install it does seem to be tied to the views I'm generating off of Content Profile relationships. I'll do some more testing this weekend to confirm.

Same error. I am in the middle of upgrading from 5.x and am trying to recreate my views. I also had content profile installed but I uninstalled it to no avail.

If it would be helpfule I can post the javascript code that comes up in Firefox after trying to add an argument or a field, but it's pretty lengthy.

I have not installed the dev version but will give it a try.

Let me know if you have any specific quesitons

JV

For problems related to views object cache, this is finally fixed and should be in the 2.4 release.

No, it's not fixed. I installed 2.4 and am still getting the same error.

Aren't we supposed to test a bug before we close an issue?

Let me know what information/testing you need.

Something new.

Before when I would attempt to add an element to a new view (field, arguement, etc.) I would get an error and nothing would be added to the view.

Now, if you refresh the page, it seems that despite the odd error the elements are being added to the view.

Note: if I click "Cancel" instead of "Add" the same error occurs.

Aren't we supposed to test a bug before we close an issue?

Please don't expect my help in the future.

jvinci: Just to add, your problem may or may not be the same, but the problem identified in #7 is fixed. If your problem is different, then you have no business giving me lip for closing an issue that you're basically taken over.

Dear merlinofchaos,

Please forgive me.

I'm sure you've met a lot of ungrateful jerks. I'm not ungrateful, but I can see why you might think so.

My post was not meant to upbraid, to rebuke, or to give you lip. It was an honest question, meant only to understand the proper procedures for closing out a problem.

As you stated the problem may or may not be the same. But I'm not a Views genius and apparently can't tell the difference. I admit that my post was a little presumptive. I will take care to observe a little more humility in the future.

I will repost my problem. Please do not interpret it as a demand on your time after you've stated you will not help me (and I don't necessarily blame you), but as a call to others with the same error. Your efforts on drupal.org are certainly voluntary, and you can help or refuse to help whomever you wish.

Sincerely Yours,

jvinci

Please excuse if this is not the same 'issue'; my thinking at this point is that it is the same issue or related to it, just a different symptom.

I have been seeing the SAME symptoms as described here, PLUS I get a download dialog box offering to download or open file: field25611.eac when I try to edit and add fields. They seem to get added if I cancel. But whenever I click the UPDATE button or the CANCEL button after 'adding' a field or even trying to modify a field, I get these eratic behaviors and the dialog box.

field25611.eac -- how strange. That's not something I even recognize, nor do I know what a .eac file is supposed to be.

You may need to turn off the javascript UI, which you can do at admin/build/views/tools -- that'll force it to downgrade to the non js ui which is not as good but is still usable.

My partner, who installed the acutal update has just notified me that he may have installed incorrectly! :( He says he has correctly reinstalled the update and I am about to test again now. If the problem persists, I will try disabling the js ui as you suggest and let you know. Thanks.

I have finished some testing since my partner 'fixed' his update. It seems to be working now and I'm not getting the dialog box (even with JS UI enabled), but it was intermittent. I'll keep an eye on it for a while and, if needed, let you know. If you don't hear any more from me on this...it was our fault. :) Others with editing problems may want to double check that they did the update correctly too...may save them, and you, a bit of time and grief. Thanks again.

Hello, I am having an issue similar to that described in http://drupal.org/node/370913 #370913: After upgrade from 6.x-2.2 to 6.x-2.3, can't edit views
Running Drupal 6.19 with View 6.x-3.0-alpha3

Clicking any links in the Views > Edit view main area (i.e. to the right of the tab column)
causes the spinners to spin perpetually, and an error alert to pop up.

Here is an example of the content of the alert message:

An error occurred at /admin/build/views/ajax/display/test_exposed_admin_ui/page_1/display_title.
Error Description: { "display": "\x3cform action=\"/admin/build/views/ajax/display/test_exposed_admin_ui/page_1/display_title\"  accept-charset=\"UTF-8\" method=\"post\" id=\"views-ui-edit-display-form\"\x3e\n\x3cdiv\x3e\x3cdiv class=\"form-item\" id=\"edit-display-title-wrapper\"\x3e\n \x3cinput type=\"text\" maxlength=\"128\" name=\"display_title\" id=\"edit-display-title\" size=\"60\" value=\"Page\" class=\"form-text\" /\x3e\n \x3cdiv class=\"description\"\x3eThis title will appear only in the administrative interface for the View.\x3c/div\x3e\n\x3c/div\x3e\n\x3cdiv class=\"clear-block\"\x3e\x3cdiv class=\"form-buttons\"\x3e\x3cinput type=\"submit\" name=\"op\" id=\"edit-submit\" value=\"Update\"  class=\"form-submit\" /\x3e\n\x3cinput type=\"submit\" name=\"op\" id=\"edit-cancel\" value=\"Cancel\"  class=\"form-submit\" /\x3e\n\x3c/div\x3e\x3c/div\x3e\x3cinput type=\"hidden\" name=\"form_build_id\" id=\"form-c8e60d7154341fdfc24068eeed5f23e8\" value=\"form-c8e60d7154341fdfc24068eeed5f23e8\"  /\x3e\n\x3cinput type=\"hidden\" name=\"form_token\" id=\"edit-views-ui-edit-display-form-form-token\" value=\"f57b9603f22524733070823d4dfbb96c\"  /\x3e\n\x3cinput type=\"hidden\" name=\"form_id\" id=\"edit-views-ui-edit-display-form\" value=\"views_ui_edit_display_form\"  /\x3e\n\n\x3c/div\x3e\x3c/form\x3e\n", "title": "Page: The name of this display", "url": "http://theoryonwheels.com/admin/build/views/ajax/display/test_exposed_admin_ui/page_1/display_title", "js": null, "hilite": ".views-item-page-1-display-title" }

END OF ALERT

I have checked the Apache log and error. It does not appear that Apache is logging an error in relation to this event.
In the apache log, I have the request made to Views:
24.203.3.244 - - [19/Sep/2010:14:03:09 -0400] "POST /admin/build/views/ajax/display/test_exposed_admin_ui/page_1/display_title HTTP/1.1" 200 1515 "http://theoryonwheels.com/admin/build/views/edit/test_exposed_admin_ui" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_4_11; en) AppleWebKit/533.16 (KHTML, like Gecko) Version/4.1 Safari/533.16"

But I don't have anything in the error log that corresponds in time, and that's related to this request.

I have tried:
-- switching back to the default theme
-- uninstalling most other modules, including jquery_UI
-- otherwise it is a fresh install of drupal 6.19 with View 6.x-3.0-alpha3

I am wondering about the possibility that my server provider (hosting.com) has some settings which restrict the functioning of AJAX. But i'm not really sure what those settings would be, are they part of php.ini, apache conf, or somewhere else? Is there some way to check my server configuration to ensure it is compatible with module needs?
Or, is this a legitimate bug with Views?

I hope I've provided enough documentation of the bug.
Thanks to anyone who can give advice.

Come on.

This issue is about updating 6-2.4 Please search for similar issues first