I'm having problems with Views UI after upgrading to PHP 5.3. I add to have done also other changes to my drupal installation. Upgrading php is the major, but it could also be something else.
My actual version is the last 2.x-dev; I tried downgrading (to 2.8) and upgrading to 3.0-alpha3. Nothing went.
The error I have is this: http://nopaste.info/187ba95ae9.html
It appears as an error in the browser when trying to use the interface for creating a new block/page, etc in a display, trying to modify or add records etc. (Screenshot attached)
Nothing appears in drupal logs with 2.x-dev. The only error I have is when updating:
[code]Multiple primary key defined query: ALTER TABLE views_display ADD PRIMARY KEY (vid, id) in /home/facens3/webtelevideo/drupal/includes/database.mysql-common.inc alla riga 374.[/code]
In 2.8 the error is:
[code]call_user_func_array() expects parameter 1 to be a valid callback, function 'views_import_access' not found or invalid function name in /home/facens3/webtelevideo/drupal/includes/menu.inc alla riga 452.[/code]
Enabling PHP logs (with E_ALL), nothing appears about views and neither drupal.
I also tried to apply the patch suggested in this topic regarding php 5.3, but nothing goes.
Thanks in advance for the helping.
Thanks for the great job you provide.
| Comment | File | Size | Author |
|---|---|---|---|
| screenshot_01.jpg | 303.65 KB | Fa-sum |
Comments
Comment #1
Fa-sum commentedI confirm that the problem is with JavaScript, because disabling it in Views>Tools, the error disappears.
About this, the version of Jquery is 1.4.2.
Feel free to ask my any additional info.
Greetings.
Comment #2
Fa-sum commentedComment #3
dawehnerSo you used 2.10 and downgraded? If you have this error, clear the menu cache and it will go back.
There has to be a php error somewhere, if you cannot provide this real php error, its really hard to fix this, because we don't know what to fix :)
Comment #4
Fa-sum commentedI tried to clear both drupal and views cache. This was without effects.
About the version, I'm explaining that views doesn't go with both 2.10 and 2.8, but giving different errors. The one reported in the first part of my post is about 2.10 (2.x-dev) and the second is with views 2.8.
How do you explain the fact that with JS disabled in Views>Tools the error in 2.10 (that what I ask to focus to) disappears?
Greetings.
Comment #5
Fa-sum commentedThe problem is with JQuery 1.4.2; Downgrading to 1.3.2 solved the problem.
Comment #6
merlinofchaos commentedRetitling issue. Looking for people who know jQuery who can maybe help.
Comment #7
ldipeso commentedIt looks like you're using the jQuery form plugin. Maybe just upgrading to the latest would work:
http://jquery.malsup.com/form/#download
Comment #8
ldipeso commentedSo, I think I've tracked down part of the problem. The ajaxSubmit functions are erroring out. The error type is "parsererror" -- my guess is, for some reason, the JSON parser in jQuery 1.4.2 is now complaining about what's being returned.
EDIT:
And this is probably the cause (was added in jQuery 1.4.1):
http://api.jquery.com/jQuery.parseJSON/
See also:
http://api.jquery.com/jQuery.parseJSON/#comment-46164903
Maybe there each ' \" ' should be ' \\" '?
Comment #9
lcampanis commentedWaiting on this guys ;)
Comment #10
Rubix commentedWaiting as well :3
Comment #11
merlinofchaos commentedDrupal core itself is not compatible with jquery 1.4: http://drupal.org/node/479368
In no circumstances is a lack of support for jquery 1.4 critical.
Comment #12
esmerel commentedCopied from #940280: Jquery 1.4.x NOT COMPATIBLE WITH Views 2.11
Posted by alanburke on November 18, 2010 at 8:16am
There are issues with jQuery 1.4 and Drupal in general.
They are likely to get sorted out in this issue for jQuery update.
http://drupal.org/node/685060
The particular issue you are encountering, can be sorted with this patch to Drupal Core which has made it to Drupal 7
http://drupal.org/node/479368#comment-3410894
Comment #13
merlinofchaos commentedThere's nothing really to be done about this until/unless core is fixed.
Comment #14
mustanggb commentedFor anyone else experiencing this issue here is a patch to core that fixes it drupal_to_js_proper_json-D6.patch