Reason Developer Notebook
Posts tagged with “Minisite Modules” (All posts)
- April 13, 2011 at 2:10 pm
As of April 14, 2011, jQuery UI 1.8.11 is distributed in Reason, and can be added as a head item and used in a module in a similar way to…
- March 5, 2011 at 10:48 am
Many modules that show images can now be configured to present those images at custom sizes. In all cases, image sizes are configurable through page type parameters. Read on for a list of the updated core modules, information about how to control image sizing, and how you can build image sizing into a custom module.
- July 29, 2010 at 2:38 pm
We have created a new folder within the core/local split called config. The intent is to provide a space to configure components of Reason while also providing access to the…
- May 12, 2010 at 6:16 pm
Generic3 can have terrible performance when multiple relationship filters are applied to a page. I have committed two changes today which should help the situation.
1. generic3 will automatically cause mysql…
- May 3, 2010 at 7:02 pm
The thor class and reason forms have previously supported a specially named button called "reset" that would serve as a reset or clear button for a form.
Support for this special…
- April 14, 2010 at 11:54 am
Form pages extended ContentModule instead of EditableContentModule, and so inline editing was not available for the page content area of form pages. This has now been resolved so that inline…
- April 9, 2010 at 5:14 pm
Reason 4 Beta 8 was released on April 9, 2010. This post names some of the major changes, provides some links to more details and svn revision numbers.
- March 8, 2010 at 3:54 pm
Inline editing in Reason has been more fully implemented, and template cruft removed. There is no longer any direct connection between a template and support for inline editing - it is entirely module based.
- March 2, 2010 at 2:12 pm
We've overhauled the API for dealing with breadcrumbs. These changes will, hopefully, make dealing with breadcrumbs significantly easier – particularly when developing modules that are more complex than a single…
- December 29, 2009 at 6:42 pm
The most recent nightly builds of Reason contain a resolution to bug #80. All modules should now be able to register their last maintained date/time with the maintained module after the init phase, and, as long as modules are run before the maintained modules, they can even now report their last updated date/time after their run phase (this is a little more iffy, as it relies on modules being run in a consistent order.)
In layman's language: before this fix, some modules, even when they attempted to report when they were last modified, the page footer did not properly reflect that. With this fix, the page footer should now properly report on all modules' last modified times.
- August 6, 2009 at 11:04 am
- August 29, 2008 at 2:26 pm
The login script was triggering a warning when unique names not in the database were requested. Since these values are coming in from userland, this could cause lots of unneccesary…