MarmotBlog

2/18/2004

Running post-merge changelog

Filed under: — tim @ 2:38 pm

Changes made since the merge

7 Responses to “Running post-merge changelog”

  1. Tim Says:

    MU_Move_List:
    Modified value() to also return value of a hidden element
    Modified add_hidden() and add_list() to trigger errors on name collisions between the two
    Renamed orig_value() to original()
    Modified value(), original(), added(), removed() to return a flat array of the short names/ids of the appropriate elements
    Renamed and deprecated add_action() to add_user_action()

  2. dirk Says:

    All DBH classes

    Updated all current DBH classes to trap for empty statements on run and prepare.

  3. dirk Says:

    MU_Form class
    Added a check for use of min or max validation rules without validating as a numeric type. The class will automatically add ‘number’ to the validation rule.

    Fixed a bug which caused input items of type ‘option’ which were set to allow single selection but had only one value where incorrectly returned as an array.

  4. dirk Says:

    MU_Tabulator class
    Changed input attribute input_size to size for consistency with forms. Use of input_size will trigger a warning.

    Added a check for non-numeric start_record specification. The tabulator will revert to 1 in such a case.

    Changed add_input() to add_input_item() for consistency with forms. add_input() will still work but is deprecated.

  5. dirk Says:

    MU_XML_Element class
    Fixed a problem that caused invalid dates to not appear in the date/time structure type inputs. (While this is manifested on forms, it is currently implemented in the XML element.)

  6. dirk Says:

    MU_Form class
    Improved handling for file input types on forms. The value of a file input object is now the corresponding array from the $_FILES global. It will be returned from either the value or values method of the form.

    Improved (actually enabled) requiring a value for input items of type file. PHP errors regarding size and partial uploads are also handled as part of requiring the item.

  7. Tim Says:

    MU_Logger
    MU_Simple_Logger
    MU_Logger is currently an empty class that extends MU_Simple_Logger, a very basic logger class with no persistence between page requests. The deprecation logging has been rewritten to use an MU_Logger object.

    mu_logline() will write a single line to this global log object

    mu_stdlib.php
    _mu_deprecated has been deprecated. (It still works, I just wanted to say that.) We now have _mu_error() which should be used to throw Marmot-level errors. There are currently two types: ‘warn’, which displays a warning in development stages (just like _mu_deprecate does now), and ‘fatal’, which logs an error, displays the error, dumps the logger, and exits.

    mu_autoprepend.php
    Includes MU_Logger.php and creates a new object in $GLOBALS[’_logger’]

    Update:
    Since I’m an idiot, I originally made these changes on naslnx07 (Don’t ask why, I was playing with KDE apps remotely via X at home), which was on the dev_1-1_branch. I have finally re-applied those changes to the trunk and reverted the changes on the branch. All is believed to be well.

Powered by WordPress