Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The only thing different in this version from 1.13, is I added a small "Donate" paypal button on the admin form page. Shameless, I know, but I have to eat too! Seriously, though, any donation amount is greatly appreciated.
Fix for this bug: #1473166: Can not drag Webform file upload field The issue is that the Ajax file upload field is no longer draggable. I fixed it by re-arranging how and when the draggable wrappers are added to elements, placing them in a #pre_render function now.
Added ability to control the "grid width" used with Arrange Fields.
It is on the settings page. Default is 10px. If set to 1px, this
allows users to move fields with a complete freedom of movement.
Based on issue: #1456534: Vertical field alignment
2-26-2012
Added ability to control the "grid width" used with Arrange Fields.
It is on the settings page. Default is 10px. If set to 1px, this
allows users to move fields with a complete freedom of movement.
Based on issue: #1456534: Vertical field alignment
Made changes to fix a persistent issue for some users, where textfields
sometimes have a height of only 1px. To this end, this module no
longer attempts to set the height of textfields, only textareas.
The original issue is: #1241750: Webform text area resize upon save (in D7)
Though the original issue was for D7, I made my changes in D6 as well to be consistent.
Made changes to fix a persistent issue for some users, where textfields
sometimes have a height of only 1px. To this end, this module no
longer attempts to set the height of textfields, only textareas.
The original issue is: #1241750: Webform text area resize upon save (in D7)
Added very small CSS tweak, to correct a problem with the webform datepicker component,
which caused it to stack its elements in a weird way. Issue: #1372978: Datapicker vertical
Thanks to user drizzi (http://drupal.org/user/226909) for letting me debug on his server, I discovered the solution to an annoying bug affecting several Webforms users. When you set the label to be "inline" in webforms, a strange interaction with CSS and jQuery UI caused textfields to resize strangely. From now on, use Arrange Fields to set the label as inline or not.
Also, fixed an issue where sometimes form elements wind up "stacked" on top of each other when arranging fields for the first time.
Found a bug which was causing certain webform components to not be configurable (they didn't get the configure link on the hover handle), and they were not being recognized as webform components.
Added a new "Enable form_id discovery mode" checkbox to the settings
page to make it easier to find out form id's on the page. If checked,
administrators will see a printout at the top of every page with a list
of what forms are on that page. You can then enter those form_id's into
the settings page to arrange them.
Also, since there have not been any significant bugs reported, I am making this an official 1.0 release for D7.
Made minor change to prevent a notice from showing up when
arranging a content type (the notice was coming from core's
node.pages.inc, line 303). Issue: #1098532: Undefined property: stdClass::$language
Made a minor change when looking at elements in the form array
to prevent PHP notice messages from appearing. Specifically, a "notice" was showing up on the user_register form when you had logintoboggan installed.
This is a minor update to prevent php from throwing a notice in one particular spot. I am moving from alpha2 to beta1 since I haven't received any bug reports in a few weeks. If you have alpha2, and haven't been bothered with any PHP notices, then you do not need to upgrade at this time; that one little change is the only difference.
Tweaking some display issues, and doing my best to get rid of PHP notices being generated from this module. Also, corrected some instruction text to be correct for D7 (was still showing instructions for D6). Also, fixed permissions-- was still using D6 style permissions by mistake.
Initial commit of Arrange Fields for D7. It should be completely functional, but as I haven't had much time to test, I am sure bugs will be discovered, so I must mark this as "alpha" for now.
Added in some extra per-form CSS, so you may have more than one
webform block on the screen at a time. In reference
to issue #1010044: Multiple forms on a page.
Fixed a bug in hook_menu which was causing an Arrange Fields tab to
appear on all nodes for users with the administer arrange fields
permission AND webform module installed.
Also, added a hack which forces Captcha to not be treated as a
fieldset. This seems to be the default behavior for most people,
but an issue was raised where, for some reason, Captcha was being
treated differently, and it caused an issue with Arrange Fields.
The Profile module lets you create fieldsets with spaces in the name,
which breaks Arrange Fields. This was fixed. Also, since no major
bugs have appeared for a while, I am going to move Arrange Fields
to a full 1.0 release.
If you have RC2, this is the only change, so it is possible you do not
need to upgrade just yet, if you are not using fieldsets with the Profile
module.
Added ability for webform fields to also have the same convenient config popup
that CCK fields have, so you can edit the properties of the field w/o having
to leave the page. Tested and working on Webform 2.9 and Webform 3.0 beta6.
This version of the module is now considered "RC" which means no new features
will be added to this branch, only bug fixes if and when they come up. If all
goes well, then I will move the code into an official 1.0 release... then get
to work on version 1.1-alpha1 ;)
7-30-2010
Added experimental support for webform 3.0. I don't want to do too much work
though, until webform 3.0 moves out of beta (I am afraid of their code
continuing to move around, and then I will have to keep making changes to catch
up).
7-29-2010
Added cache_clear_all() to hook_enable(), as clearing the cache often fixes
the initial javascript and css bugs which some new users experience.
******UPDATE:*********
In fact, I did not fix the bug-- it's still there. Use beta4 version instead! So sorry!
So, to recap, do not use this version, please use beta4 or later!
*********************
Fixed a fairly embarrassing bug where, with CCK forms, the delete button could not be arranged. For anyone using the beta1 or beta2 release, I recommend upgrading to this version.
I changed around how form fields were detected in $form, which allows you to use form_id's whose forms have more than one dimension. This is an internal change, largely for people who want to use this module with custom forms they've created. Webform and CCK forms are unaffected.
In addition to some minor bug fixes involving display, with this release you can now add arbitrary markup to your forms. I am making this a "beta" release, as we have gone through 7 alpha releases with no major bugs discovered, so I think it's safe to move it to "beta."
Made a lot of changes with this release, which are documented in the
CHANGELOG.txt file. Fixed bugs mostly, added the ability
to arrange any form in drupal, and added a new config dialog
which lets you specify the wrapper width, height, and whether or
not the field's label is inline.
Getting ready to put out a "beta" release instead of all these "alpha"s, and set the "recommended" flag for it-- exciting!
Added preliminary support for Webform in addition to CCK. Also, fixed a bug where the CSS and JS were not being re-added if the form failed validation.
A user found another bug-- another oversight on my part (I had a type when looking for a particular CSS ID). I also updated the menu hooks to better integrate with CCK.
Fixed a bug with the preview button I noticed just after I did my initial commit. Stupid oversight on my part. I also added the ability to make taxonomy a draggable field.