Buy Now
Sign in

ChronoForms v4 for Joomla! 1.5/1.6/1.7 RC1.9 bug fixes

GreyHead , June 26 2011


  • Please see the CFv4 RC1.8 list here I think some of these were fixed of RC1.9 but it may be worth checking back if you find a bug that isn't listed here. Bugs reported more recently are still included in this list.

  • There appears to be a serious bug in Joomla! 1.6.2 that fails to load the core JavaScript files in the Forms Manager view. A workaround is in this post. Fix is to upgrade to 1.6.3

  • The date-time picker has some minor bugs in Joomla! 1.6 - this is not strictly a ChronoForms bug, just that the datepicker library hasn't been updated to work with MooTools 1.3 :-(

  • Bizzynate identified a bug and fix in the File Upload action. See this post

  • abeletsky identifed a bug with ChronoForms on the home page. See this post. See the fix from Buro26
    here. (This fixes problems with SEF URLs.) There are also repeated reports of problem with the ChronoForms plug-in, these may well be related. See a fuller list of module/plug-in problems here and the plug-in code re-written for Joomla! 1.7 by mgroeben here

  • There is a bug in the interation of the datepicker and validation scripts. The datepicker script moves the original input off screen and the validation error message is also off-screen (it partially appears at the top left corner). This appears to be fixed in RC1.9

  • Mr CompTech noted some data losses when switching from the Advanced Mode Editor to the Easy Mode. See this post

  • Mr CompTech also noticed that it would be helpful to have the Menu Item event default to 'load'.

  • chrissy6930 noted some Browser specific formatting issues in the Admin area (see later post in this thread).

  • tsrlinkan found a bug in the Validation code for check-box groups. The fix is here

  • There's a bug in the Admin Table Saving code. Line 534 is JError::raiseWarning(100, $row->getError()); but $row is not defined, it needs to be JError::raiseWarning(100, $database->getError());

  • The ChronoForms module has BOM bytes at the beginning of the files that can break page layout. There's a fixed set of files here

  • Castaigner and colleagues identifed a bug in the Multi-Record loader for drop-downs with multiple selections enabled. Fix in this post

  • There are reported problems with the Admin area in IE8. I ran a quick check in IE9 and that seems OK, also IE9 in IE8 Browser mode seems OK but IE7 Browser mode is badly broken.

  • The DB Record Loader action has a bug that means it cannot handle array results correctly e.g. list of values for Checkbox groups. Contact Max for a fixed version if needed.

  • lowrykun found a bug in the Multi_Language action in Joomla! 1.6/1.7. See this post for details and a fix.

  • lowrykun also suggested adding language tags as labels to the Multi-Language actions. See this post for a fix.

  • There's a bug in the code that handles events that adds the ChronoForms strap line to new events and breaks Ajax responses. See this post for a fix.

  • dyoungers found a bug in the PayPal Listener action. Bug report and fix here.

  • The Confirmation page action adds Confirm and Back buttons but the visible labels are 'Submit' and 'Cancel'. They can be edited in lines 16 & 17 of administrator/components/com_chronoforms/form_actions/confirmation_page/cfaction_confirmation_page.php
  • [/list:o]

    ChronoForms technical support
    If you'd like to buy me a coffee or two, thank you very much


    Hi Bob,

    I don't know if it's a bug or it's only me having this error.
    The validation error message is off-screen for checkbox.
    I have managed to extract the code:

    For checkbox we have this left: -9855px (WOW!!!)

    				<div class="fc-tbx" style="visibility: visible; opacity: 1; position: absolute; float: left; left: -9855px; top: 1000px;">

    For other fields, the error box appear just fine and the code looks like this:
    				<div class="fc-tbx" style="visibility: visible; opacity: 1; position: absolute; float: left; left: 678px; top: 732px;">

    Maybe you can give me a hint. I know that the code is rendering from formcheck-yui.js. I also mention that using a simple checkbox I was unable to validate it for errors so I used the multicheck-box with only one value in order to have the validation working.

    The version of Chronoforms is 4.0 RC2.0.
    You can test this using the form that I have uploaded in my post here