warning

Hrm. Very interesting. Are you sure you have the jquery_ui module installed and configured correctly? It can be a little tricky. Make sure you are using the right version of the jquery_ui plugin; I think it only supports version 1.6.

Remember, it wants the plugin installed at modules/jquery_ui/jquery.ui (notice the dot).

Also, I don't know if this would make a difference, but try turning off and emptying the cache, as well as any JS or CSS compression. This module depends on CSS and javascript, both of which might be getting cached or compressed or something and acting weird for you.

If that does not fix it, please report back what browser and version you are using. I have tried the module on Chrome 5.0.375.70, Firefox 3.6, and IE8, but am unable to test it anywhere else.

Thanks,
Richard

-- Correction! jQuery UI supports plugin version 1.6, not 1.3. I will change it in the original post.

Interesting. I did not use jquery_update. I only am using jquery_ui with plugin version 1.6. If you still feel like experimenting, try using that set up and see if it works for you. Also, if anyone out there reading this has had problems with jquery_update and version 1.8, please let us know. I will experiment and see if I can replicate the problems with your set up.

Richard

I just thought about it, and the problem might also lie with your theme, if it's doing something unexpected with CSS (and possibly overriding certain CSS properties set by the module). I tested this with Garland and a couple others, without problem. You might try temporarily switching to Garland and see if that does anything.

The only other thing I can think of is that it relies on hook_form_alter to set up the positions of the elements and add wrappers around them. Perhaps you have another module installed which does something in hook_form_alter which my module doesn't want to cooperate with?

Of course, these are just theories. My hunch is that it is indeed a jquery_ui problem.

I have just put out a new release, version alpha4. It has a few code changes, as well as support for Webform. I don't know if you are still interested in this module or not, but if you have the time to experiment, you might try it out and see if it fixed anything for you. You might also try it with the webform module, just to see if its a difference between CCK and webform.

Best of luck!

Richard

Hrm. That's really odd. I am not sure why that change would make the grid show up. I had to do a lot of experimenting with the positions (absolute vs. relative) before I could get the module to correctly save the positions.

The fact that they are still not draggable is weird. That is accomplished with a simple jQuery function call of $(".arrange-fields-container .draggable-form-item").draggable (see line 35 of js/arrange_fields.js).

Either this is not getting called for you, or it is, but it is having errors.

I'm sorry you keep having trouble with it! If you do discover anything else, please post the details in case someone in the future has a similar problem.

Richard

I have the same problem. My drupal site has only cck, pollfield, views, autopath, and token modules installed. I have also tried changing it to a bunch of layouts, even Zen, but the result is the same.

If you could post a tutorial on how to use Arrange_Field and install JQuery_UI module I think that would be very helpful.

Below are the steps I took to install JQuery UI and Arrange Fields:

1. I downloaded JQuery UI from the Drupal Module page
2. Went to the JQuery google code page and downloaded and downloaded the jquery-ui-1.8.2zip file
3. Extracted the contents of the zip file to the JQuery Module folder (sites/all/modules/JQuery_ui)
4. Installed the module through my Drupal site
5. Installed Arrange Fields module

Result
I what you see in my screen shot and I can't drag things around.

Your help is very appreciated.

I have been thinking of posting a tutorial/handbook page for some time, but I wanted to wait until the module was a little more stable before I did it. But I do think that's a good idea.

I believe your problems lie with jquery_ui. There probably should be a handbook page or some such for that module, as I think its installation is what trips up most people. Here is the module's readme.txt file, which provides a step-by-step:
http://drupalcode.org/viewvc/drupal/contributions/modules/jquery_ui/READ...

As I've said in earlier posts, I think your error is that you should have downloaded version 1.6 of the jquery_ui plugin, not version 1.8. Version 1.8 requires a higher version of jquery than what is included with Drupal.

Also, unpack the files into /modules/jquery_ui/jquery.ui (notice the dot in the last folder!)
After you do this, for example, the file MIT-LICENSE.txt should be at /modules/jquery_ui/jquery.ui/MIT-LICENSE.txt.

Next, you probably need to clear out both your browser's cache and drupal's cache, to wipe out any errant javascript.

Then, go to arrange a form. Click "Reset positions" to start fresh.

If you still have problems, upgrade Arrange Fields to the latest dev release, if you haven't already. Then clear your caches and try again.

Best of luck!
Richard

Yea you were right that JQuery_UI only works with 1.6.

I also have a filefield for loading images in my cck content and I can't drag it around. It is always stuck on the upper right corner. Could you please provide some advice on how to solve this problem?

When collapsed menus are expanded it does not dynamically allocate additional space and overlaps page blocks instead. Is there a way to preserve dynamic spacing through your module as well?

Not sure if these functionality exist, but would I be able to select multiple blocks at once and make certain fields invisible? Might be a good feature to have in your next release.

Thanks a lot.

Hrm, I am not sure about the filefield. I have tested that very functionality in the past, and did not have a problem. I will give it another look to make sure. I would say, be sure you are using the most recent version of arrange_fields, either dev or beta5. If you have one of those installed, please provide a screenshot of the problem happening.

Regarding collapsible fieldsets, please see this issue: #826202: Fieldsets do not behave pushing content down on open and a suggestion

I have considered trying to do multi-selection in the past, but it is very difficult to do in javascript. I will give it another look, though, just in case. No, there is no simple way to make a field invisible, though you can accomplish this in your theme's CSS file. Just target the element in question and say:

#element-id {
  display: none;
}

Thanks
Richard

-- And actually, I just tested, and you are right-- the file field is not working. I must have broken it with a recent update. I will try to get it fixed.

Thanks for finding this one!
Richard

Okay, I have a solution in place. It will be in the next dev snapshot later today, but if you don't want to wait, you can download arrange_fields.module from here:
http://drupalcode.org/viewvc/drupal/contributions/modules/arrange_fields...
(version .19 or later).

It seems my method for adding draggable wrappers to fields was failing for filefields, because of the way CCK renders them on the screen.

Thanks for finding this bug!
Richard

Thanks for the quickly fixing the bug. I read your other post about dynamic spacing (pushing content) and I agree that the most practical solution would be a solid white background. The filefield wrapper also seems to be a little too small, so the upload button is being pushed to the next line (see screen shot). I fixed by changing the wrapper size to 465px, but this is dependent on my screen resolution, so it might need to scale based on the screen resolution. I am not really sure I don't really do web design.

When you commit updates tonight could you please implement the solid white background for the drop down menus and change the wrapper size for the filefield?

If it is too much trouble could you please let me know where exactly I would go to make these changes?

Your the man!

For white background for expandable menus works great, but for filefields it does not work so well. The ImageFields displays more content after submission of a image (please see screen shot 1). You said dynamic spacing is not feasible, but allocating space for the expansion does not really solve the problem because it creates an unappealing UI (see screen shot 2). What should be done about the filefield?

Thanks alot

Well, unfortunately filefields are problematic. You are correct that you need to allocate extra space if you plan to use them; there isn't really any way to help that. I would suggest either always placing them off to the side, or maybe in a fieldgroup (requires you to enable that module) and then setting the fieldset to have a certain height. After you set the wrapper height, hit save and the fieldset should automatically resize. This way space is still allocated, but since it has a border around it, it doesn't look so odd.
-- If you don't want to fool with a fieldgroup, you could also just add a border to the wrapper div around the filefield in your theme's CSS file.

Setting a default solid background color for fieldsets is probably a good idea. I will put that in, and the dev snapshot (which runs automatically every 12 hours) will have it in there when it re-runs.

As for where manual CSS changes should go, there is probably a "style.css" or some other .css files in your theme folder. You can add your changes to the bottom of that file.

Thanks
Richard

-- A quick addendum to adding a solid background color to fieldsets-- the reason I didn't do that is because some themes (Like Garland) already do it. But, since users may have all sorts of different themes, I am going to put it in, as it's probably easy to forget. You can always override the color and transparency in the theme's CSS file later.

Richard

That is a good solution for dynamic spacing. I guess another concern I have is how do I add the non-fields, such as title, menu, and path.

Thanks for all of your help.

I am not exactly sure what you mean. Those fields should all be on your form already, just as collapsed fieldsets. You can just click their titles to expand them. If you meant, what is the best way to lay them out, I'd recommend horizontally at the bottom of your form. (Well, I'd keep the title at the top of the page. I just meant your node admin fieldselds like path, menu, published, etc).

You can also install the Vertical Tabs (http://drupal.org/project/vertical_tabs) module, which converts your fieldsets into very attractive vertical tabs, which is compatible with Arrange Fields and may look nicer.

Thanks,
Richard

Hi everyone. I am having the same problem with Arrange Fields modules. Here i uploaded a .doc file where you all can see the problem. Can any one please help?

https://docs.google.com/document/edit?id=1iSZo9gC-tttKA--FAa9420pFcSSpon...

Regards

I believe you are using the wrong version of jquery UI. It should be version 1.6. For example, in my jquery_ui/jquery.ui folder, I have a file called "jquery-1.2.6.js" while you have "jquery-1.4.2.js".

-- please look at the handbook for help installing the right version:
http://drupal.org/node/877774

(closing issue)

I keep getting this warning what should I do?
* warning: file_get_contents(modules/arrange_fields/js/arrange_fields_node_edit.js) [function.file-get-contents]: failed to open stream: No such file or directory in /home/content/90/7333990/html/includes/common.inc on line 2467.
* warning: file_get_contents(modules/arrange_fields/js/arrange_fields.js) [function.file-get-contents]: failed to open stream: No such file or directory in /home/content/90/7333990/html/includes/common.inc on line 2467.
* warning: file_get_contents(modules/arrange_fields/js/arrange_fields_dialog.js) [function.file-get-contents]: failed to open stream: No such file or directory in /home/content/90/7333990/html/includes/common.inc on line 2467.

Looks to me like your javascript files got deleted somehow. Try deleting thearange fields folder and just redownloading the module. If you still have an issue, please open a new issue instead of adding on to unrelated ones.