- Shift ProfileField API so that new returns undef on invalid fields.
This makes it possible for Shortcut::www_saveUserPrefs to execute.
The class methods in ProfileField are now also actually class methods.
+ Also fix up other modules that created dummy ProfileFields so that
they don't need to do that anymore, because it's now invalid.
- Merge contradictory-looking code from Shortcut's view and www_view
into a reasonable compromise in view, and then have www_view call
$self->view in a manner similar to that of the default Asset::view.
+ The profile field overrides still don't work, because there's no
obvious mechanism for "transclude asset in context". This may
require some fiddling to get right...
- Shortcuts that are dashlets no longer mysteriously mutate into
their parents.
- Saving edits to dashlet preferences no longer kicks you out of
your version tag.
- Perform RFE "js-confirmation-operation/user.pm".
- Perform RFE "js-confirmation-operation/group.pm".
- Perform RFE "locked-by-who".
(Displays in title and alt of img, but not in body text.)
- Probably fix "more-geturl-bugs", but hard to verify.
- Fix "last-modified-problem", approximately. (Difficult or impossible
in the general case for externally-retrieved content.)
- Fix "rss-syndication".
- Fix unnamed bug where Database caches would try to Storable::freeze
non-references and thereby crash.
- Fix "apache-version-component-in-wrong-place".
- fix: cacheTimeout not respected as Visitor (Eric Kennedy).
- fix: Email address with just one character in the user part not accepted
- fix: Image (file) added to page shows before committing changes
- fix: Typo in fileImport.pl at line 265 (zxp)
no className is passed and the invocant's class is Asset. This is
due to the root. In the db, the root Asset has the className WebGUI::Asset,
and the getRoot method matches this.
Changed the failing test in Asset.t to look for a WebGUI::Asset to be returned.
Added two tests to Asset.t to validate the object returned by Asset->getRoot method.
Reverted previous work and updated the POD for Asset->new.
- fix: Search results not showing synopses
- fix: Redirects get displayed inside page layouts as '0'
- fix: Mysterious "0" Appearing When Admin Is Off
- fix: Deletion of Products
The check for rolling back the pbversion0000000000001 tag wouldn't log any
errors because it was after the return 0 statement.
If a set of assets that were programmatically generated were rolled
back, and the assets had a parent child relationship then there's
a race condition that could cause the parent to be purged before
child. Since purging the parent _also_ purges the child, the system
would try to purge the child twice and this causes a fatal error.
Programmatically generating the assets causes their revisionDates
to be the same, and that causes the return order of the assets to
be uncertain.
The solution is to generate the list of assets to be rolled back
by revisionDate _AND_ lineage. This guarantees that children are
purged first.
This bug was exposed in t/Macro/RootTitle.t However, the bug
seems to be system dependent since the revisionDate depends on how
fast the system can create assets.
