Exponentcms Exponent CMS → 2.0.2

Comments and changes to this ticket

• 

  dleffler October 12th, 2011 @ 06:13 PM

  • State changed from “new” to “open”
  • Assigned user set to “dleffler”

  Actually this issue was injected in 2.0.1 as a fix for the bad behavior of the cancel button in multi-level editing screens like the forms module. The actual code was expHistory::getLast() which replaced the expHistory::getLastNotEditable().

  The solution I'm working on is to add a property and 5th __construct param of 'returntype' or something. The default behavior would be as in pre-2.0.1, but you could send a 'returntype' param to get it to use the 2.0.1 behavior instead.

• 

  expNinja October 18th, 2011 @ 02:46 PM

  (from [bccfb3ba679ebd17fdc929532d703fb61242929b]) Initial Fix for Cancel Button problem [#355 ] https://github.com/exponentcms/exponent-cms/commit/bccfb3ba679ebd17...

• 

  expNinja October 19th, 2011 @ 12:45 PM

  (from [11d042b6b824ac88872916dcdcd86fd00f64979e]) Fixes for nested editor toolbar configuration screens [#355 ] https://github.com/exponentcms/exponent-cms/commit/11d042b6b824ac88...

• 

  expNinja October 19th, 2011 @ 02:03 PM

  (from [46ec44b7610530eff5e025c4cd3bce1a6d330bbb]) Deprecates expHistory:flowSet in favor of expHistory:set since the flow stuff was not being used and fell through to a generic expHistory::set call always setting them as 'viewable' history entries [#355 ] https://github.com/exponentcms/exponent-cms/commit/46ec44b7610530ef...

• 

  expNinja October 19th, 2011 @ 02:26 PM

  • State changed from “open” to “resolved”

  (from [d3a972cc8b80eb33d63b233f89e45223dc6eeb97]) Updates 'cancel' buttons with form modules to use the new button returntype param. Also did this for the NON-Simple controls (with a form method) in case we want to use them as simple controls in the future. I'm not aware of any other nested edit/manage screens, but hey could be updated in a similar fashion [#355 state:resolved] https://github.com/exponentcms/exponent-cms/commit/d3a972cc8b80eb33...