Arrange Fields and jQuery 1.7

Have you tested it out? I thought it did work, so long as you follow the directions with jquery UI's README.txt file regarding the jquery updater module (http://drupal.org/project/jquery_update).

I say to use version 1.6 of the plugin on the project page, because some people get very confused about it. I will change the project page to be a little clearer.

Thanks
Richard

PS: If you have tested and it *doesn't* work, please let me know!

Well darn. The last time I checked it was working. I must have fumbled something up since then.

I will look into it right away.

Thanks!
Richard

Okay, I have jquery_updater installed (using the alpha1 release, as required for jquery UI 1.7), and I used jquery.ui 1.7.

Arrange Fields, for me, does appear to mostly work, though I clearly have a few problems. Textfields are no longer resizable, for example. And there are some other CSS problems.

You may want to make sure you are using the version 2x release of jquery_updater.

For the time being, I can only support the 1.6 version of the plugin, at least until the required updater module moves out of alpha.

Thank you for bringing this to my attention. If I do make any changes which support 1.7, I will place a notice about it here.

Richard

Hrm-- well, that should have worked. Have you tried clearing out your browser and drupal cache?

So, on the Arrange Fields page (where you are supposed to be able to drag and drop fields), do you see the gray grid? Also, are their gray boxes around each field?

Richard

Huh. Well, that is pretty weird. I see you also get the little square "handle" box when you are hovering over something, which tells me that part of jquery is indeed working.

At this point, I am afraid I do not know what to tell you to try. For whatever reason, the jquery ui is not assigning the .draggable() property to the fields.

I take it you have probably tried the "reset positions" button, as well as tried it in other browsers?

Sorry I can't be more help! If you do figure it out, please post your solution!

Richard

subscribing

Does it completely work now? All features are fully functional?

If not, I'll have to hold off on installing this module, until it is compatible with jQuery 1.7

BTW, all of these version numbers flying around get quite confusing, regarding jQuery 1.6/1.7, jQuery Update 2.x, jQuery UI 1.3/1.4, etc etc.
If there weren't external libraries to include, would be less confusing methinks :-)

I have not done any further work to make it work better with jQuery 1.7. But.........

I could never replicate the problem listed in post #2, though I did see some admin-side display problems, but it saved the positions correctly and displayed the fields correctly during entry (which only uses CSS, so jQuery 1.7 vs 1.6 doesn't matter).

I would say if you have the time, go ahead and install it and see if it can work for you in your situation. It only takes 5 minutes to test it out.

In all honesty, since Drupal 7 is going to ship with the latest versions of jQuery and jQuery UI built in, I think I'd rather wait for Drupal 7 to make it more compatible with jQuery 1.7 (or, I guess it will be 1.8 or 1.9 by then?) That is, of course, unless there is a large number of feature requests asking for jQuery 1.7 support now. But so far there just haven't been.

Best of luck
Richard

Hi Richard,

Just checking in to see if there has been any progress with jQuery-UI-1.7 compatibility? It appears that some work had been done late last year but you were still deciding whether or not to continue with any of the D6 development given the proximity of the D7 release. As expected, some of us are going to continue to develop with D6 until the dust settles a bit on D7 so I'm certain the community would benefit from anything you are still working on for D6.

Thanks for supporting your module development efforts. If you need any help with testing, drop me an email.

Best,
Gary Betz
Community Site Design
Sacramento, CA

Hello,

I do intend to continue working on the D6 version of Arrange Fields, in parallel with D7 for as long as I can. I have been working for the past week to bring it up to speed for D7, and was actually planning to put out a dev release pretty soon.

As for jQuery UI 1.7, I believe that D7 uses 1.8, and from what I have seen so far, everything is still compatible. So, I will have to give it another look to find out why 1.7 has trouble, while 1.6 and 1.8 seem to work fine. And to be honest, 1.7 largely works for me in my installation of D6. The troubles I have are that the resizing of textfields either looks ugly or sometimes doesn't work at all. But everything else appears to work fine. Has this been your experience, too? I know others have said that it just flatly didn't work for them at all.

Richard

BTW, there is now a version of Arrange Fields up for D7, if anyone wants to try it out. I am not having any javascript problems out of jQuery UI 1.8, which ships with D7.

Richard

Hello,

I used the arrange_fields 1.4 with jquery 1.6 firefox and ie7.

I create content type and add 1 text field for testing. When I save position with ie7, all the field goes on the top. Display correctly with firefox.

If I rename the custom-style.css, it work fine. If I deleted everything in custom-style.css without renaming, all the field goes on the top.

Very weird.

sergehc, that sounds like the IE css bug to me (IE can only load 31 or 32 css files). This module might help: http://drupal.org/project/unlimited_css

(If you continue to have problems, please open a new issue, instead of posting on this one).

Richard

Hi Richard,

it seem that this module work fine. Everything is display correctly now.

Thank you

Moved this to new issue for D7

That sounds like you are having an issue with either CSS or javascript. Please try it out using a neutral theme (like Garland) and see if that helps. If you are still having problems, please open a new issue, as your problem is about the D7 release, and this issue thread is about D6.

Richard

subscribe

I could be wrong, but I think the issues in this thread have been addressed (or could not be reproduced), so I am going to close it. If anyone continues to have a specific issue, please create a new issue thread.

Richard