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.
for inserting macros into the config. The new method is much cleaner
and uses the Config API.
Updated the docs for the RootTitle macro, both POD and online help.
- fix: Asset Manager displaying incorrectly
- fix: Cannot paste from clipboard
- Made the search indexer mor compatible with Chinese and other non-ascii
characters. (Thanks to Zhou Xiaopeng)
- fix: Editing Products Template wipes out SKU
- fix: Email to RFE List Going to Spam
- fix: 7.0.0-7.0.1 upgrade -- op called w/o passing session
- fix: spectre.pl daemon error
- Changed the Spectre tests to be a seperate option on the spectre.pl command
line, which fixed a problem with the WRE monitor, and also enabled us to
add more complete connectivity testing.
Added more docs for find method in Group.pm
Fixed a latent bug that would probably never occur in Macro/GroupAdd.pm
If Group->find is called with the name of a group that doesn't exist,
then Group will return an object with defaults, and the guid of the
group is undef, not ''. However, since by default autoAdd is off,
the Macro will still do the right thing.
GroupDelete has the same bug, but it shouldn't be patched until there's
a test written for it.
