We are proud to announce the release of apostrophePlugin and apostropheBlogPlugin 1.5.1. This release reflects all of the fixes and associated improvements that have been made in the 1.5 stable svn branch since the release of 1.5.0. In fact, we strongly encourage you to set your svn:externals to the 1.5 stable branch so that you can receive important fixes like these on a regular basis just by typing "svn update". But we know that's not for everyone, and point releases help to provide a sense of how much has been accomplished.
For those who are still unaware, Apostrophe is a content management system and framework built on Symfony 1.4. You can find more information here: http://trac.apostrophenow.org/ Here's a full list of major fixes and improvements in the 1.5.1 plugins. Quite a bit has been done to improve stability, ease of migration and the overall user experience. apostrophePlugin: * Users with "Add/Delete Pages" can add pages without validation errors * "Add/Delete Pages" and "apply to subpages" work properly again for view and edit permissions * Fixed many issues regarding cropping, strongly recommend an upgrade for those who like the cropping feature * Lots of fixes to apostrophe:migrate-data-from-pkcontextcms and apostrophe:migrate. The former now triggers the latter on success since it is required to complete the job. Please, take the plunge and get off pkContextCMS * File slot now allows filtering by type, and lists only types that are downloadable * New .a-editing and .a-normal classes replace .editing-now and provide a class for the case where the slot is not being edited. Much easier to customize slot styles based on whether the user is editing * getPagesInfo never returns virtual pages. Helps with custom navigation * Google Analytics is supported out of the box in Apostrophe via app.yml * Cancel button works properly when editing media items * Video selection fixes, various jQuery double binds eliminated * Eliminated more usages of self:: to allow overriding of the related methods * Applied gido's patch to provide a transition duration option for slideshow slots. Thanks gido * Behaves properly if an embedded media service is deconfigured and a linked account still exists * Admin generator theme no longer caching CSRF inappropriately, fixes issue for multiple admin users. Thanks Jeremy * --verbose option to rebuild-search-index, it now runs quietly otherwise * Small CSS changes to button colors and color selectors * UI improvements and fixes to media editing * i18n fixes * Fixes to cache-friendly email obfuscation * Removed obsolete columns from apostrophe:migrate * Easier overrides in various places * Many CSS and UI fixes * Gave the user administration filter links better UI treatment * css-colors-report task reports all colors used in apostrophePlugin CSS files, plus your project level CSS files * Fixed a bug in the button slot where you ccouldn't set the FCK toolbar for the richtext * Workaround for http://trac.symfony-project.org/ticket/8861 * Media type detection improvements * Improvements to button.css, notably the .icon-right class * Scoped the audio slot ui to be more specific to avoid css conflicts * Media selection UI fixes * Images can be selected successfully for a file slot (this downloads the original of the image) * Clean off leading zeroes in a cross-browser fashion using a regexp. Fixes a bug with one-digit dates in the date widget * Styles for our "do not edit, this is a staging site" banner are now included * For the oldest formerly-pkcontextcms sites, create the media admin engine page. For everybody, make sure it stays published * Moved jquery.jplayer into the /js/plugins folder, added it to the JS in BaseaTools, made sure to use_helper(a) in the partials * Added jquery.scrollTo for the Cropper. When you are building a slideshow and have numerous thumbnails, often the cropper opens below the fold. Now, the cropper will scroll into view when you engage it, and return you back to you to the top of media when you are finished * Updated the look / feel of the slideshow controls when selecting * aString::limitWords now has a 'characters' option, which can be used to limit by characters rather than words, but otherwise behave exactly like limitWords (notably, all whitespace is converted to single spaces). The benefit is that methods that layer on top of aString::limitWords() can be called with a character limit instead. Set 'characters' to true and the 'word_limit' parameter becomes a character limit apostropheBlogPlugin: * Categories are correctly mirrored to the virtual page, fixes search problems * Tag import is now supported * Some adjustments to disqus, added ability to enable developer mode in app.yml, added the comment count to the blog meta partial * Import task cleanup * i18n fixes * No more defaults for blog import, you have to specify --events=filename.xml and/or --posts=filename.xml. This way you are not surprised by a double-import from the default location * disqus comment code was showing up even when disqus was disabled (fixed) * aBlog.js needs to be in view.yml, period, due to blog slots (sandbox fix, removed nonfunctioning code to load it) * Fixed missing tag widget label * Blog header appears properly when logged out * Many fixes to apostrophe:migrate to ensure category information is brought over from the 1.4 plugin, alpha versions of the 1.5 plugin * Behave gracefully when blog posts no longer have an author (author deleted) * UI improvements and fixes * getRichTextForAreas method, convenient for lightweight views where you don't need independent slots * Admins were losing their ownership upon saving of the blog post form because the list of allowed authors did not contain them (fixed) * Author filters are now alphabetically sorted * You can now filter by "No Author" * Category filters are now alphabetically sorted * You can now locate uncategorized posts by selecting "Uncategorized" from the Categories filter dropdown * Author and category filters can be combined with other filters properly * Google Calendar URLs were often too long; imposed a character limit rather than a word limit to ensure this does not happen -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
