The default author did not work, at least on my installation. I believe this is a better solution (although of course you can argue whether it should be getName() or FirstName).
BUG Fixed incorrect encoding of SelectedAuthor and SelectedTag; Now correctly cast for templates using the `cast` config, not within filtering.
BUG Fixed TagCloudWidget.popularities config from being incorrectly accessed as a static property
BUG Fixed TagCloudWidget::getCMSFields triggering extend('updateCMSFields') twice
BUG Fixed TagCloudWidget::getTagsCollection discarding tag label capitalisation
BUG Fixed TagCloudWidget::getTagsCollection not correctly respecting minimum tag counts (as well as maximum tag counts) when determining the popularity CSS class to assign.
Test cases for TagCloudWidget
API BlogEntry::TagNames now safely extracts tags from a blog entry as an associative 'lowercase' => 'Entered Tag' format
PHPDoc fixes
Removed trailing '?>' tags from PHP files
Our build infrastructure still runs an ancient 5.3.3,
and given this is the only blocker for it, worth
complicating the code a bit to retain this compatibility.
- TagCloudWidget not wrapped with if(class_exists('Widget')) check for dependency module
- Default titles for RSS Widget and TagCloudWidget not being translated.
- Fixed poor indentation, and excessive line length (scrutinizer errors)
- Removal of several blank 'private static $relation = array()' that added no value
- Missing PHPDoc for widget classes
- Fixed missing EOL and removed closing ?> from php files for consistency
Was saving to live before overwriting with draft again.
Since no write to draft ocurred before, this broke
the publish() call - e.g. visible by the test breakage
in BlogHolderFunctionalTest.
Removed BlogTreeExtension in favour of the new WidgetPageExtension
in the "widgets module". Use the following code to update:
Object::add_extension('BlogTree', 'WidgetPageExtension');
Object::add_extension('BlogEntry', 'WidgetPageExtension');
The template placeholder has been renamed from $SideBar to
$SideBarView. In case you're overriding blog templates,
please adjust accordingly.
This change means that widgets can theoretically be applied
to individual blog entries as well, since they need the
"SideBar" relationship as well. In practice, this defaults
to "InheritSideBar" though, which pulls them from the BlogHolder as usual.
It was disabled since migrating the module to SS3,
and the whole concept has become less relevant since spammers discovered trackbacks
(ref http://en.wikipedia.org/wiki/Trackback#Spam).
Since we don't have the resources to make a spam-proof trackback system,
its prudent to remove it instead.
