After a long time of work, the Serendipity team is very proud to announce the first public beta version of Serendipity 2.0.
Our main goal for Serendipity 2.0 was to clean up our backend structure, both in terms of coding and especially in terms of design and usability. We firmly believe to now be at a point where we want to show off our hard endeavours, and feel Serendipity 2.0 can now be properly used.
The new Backend
The most striking difference on the new Serendipity version will be the look of our new backend, patterned to match the 2k11 theme that you might already know from its frontend. We have replaced our old default backend theme with the new one. It looks fresh, is responsive, but still both easy to use and offering flexible customization.
In the technical structure of the backend, we have ported all output from internal PHP code to the Smarty template files, so everything you see is now much better separated from the underlying PHP code. Even though this enables our users to actually create their completely own backend-themes, we will NOT provide easy upgrading of the backend to customized themes. Every developer who adapts the backend will have the responsibility to adapt his theme to newer Serendipity versions. The reason for that is that we need to stay flexible with our backend and be able to add new features without thinking about compatibility to custom backend themes. However, we will try to modify backend template files with care, and always think about compatibility, an integral part of Serendipity.
Have a look at a few screenshots covering the new design:
Also there's a video tour available showcasing the backend, made by YellowLed:
Here's a small feature list of the new backend:
Responsive theme, usable for desktop, tablet and mobile devices
Uses off-canvas navigation for small screens
A new frontpage (aka "Dashboard") shows you the most notable things on your blog
A redone navigation tries to structure the backend tasks in a better way
"Themes" is now the definitive word, where we previously used "Template", "Style" or "Theme". We're committed to stick with this now. ;-)
The bundled WYSIWYG editor has been changed to CKEditor, offering a more modern and flexible approach to easily edit your blog entries. The TinyMCE-Plugin only works with TinyMCE 2.x, since recent TinyMCE versions have changed too much of their API to adapt to. If there's some developer who like to add support for TinyMCE 3.x+, we'd be happy to help. The FCKEditor plugin has been outdated by CKEditor. So the currently available alternate option to CKEditor is serendipity_event_xinha, which provides basically the old editor - however, we really suggest you to use the bundled CKEditor, or its sibling serendipity_event_ckeditor, which provides the best integration. Since the WYSIWYG-implementation has been reworked, please report issues you might find with this.
The current Theme options now have their own configuration page
A new option "simple filters" allows you to make filtering options for the media database or entry manager appear more focussed. You can still access the "power-user" filtering options, if this option is disabled. Simple filters are now by default enabled.
A conservative but thorough rework of the Media Library, with bigger thumbnails by default, nicer filter, fast type selection (Image/Video/Others), and use of an overlay for display the media item
Uses Modernizr for HTML5/CSS3 compatibility and feature detection.
In the PHP core, we restructured code and removed some older cruft. We introduced the ability to use Composer for packaging our external libraries, however those are still bundled within our repository, so that users who check out Serendipity do not need to care about installing or using Composer themselves.
We also added the opportunity to use the Zend::DB database framework. We still provide our own, simple Database API - available for PostgreSQL (PDO&native), MySQL, MySQLi, SQLite (PDO&native). The new Zend:DB framework can currently only be enabled by developers, but we will work in improving this layer so that it can be chosen during installation. If it works, this will then enable you to use any other database engine that is supported by Zend::DB.
A few things should be noted for plugin developers to take note off. If you have created custom plugins, you might need to take care of those changes. All available Serendipity Spartacus repository plugins have already been touched up to work together with Serendipity 2.0 already. Changes are:
SetCookie() to Serendipity.SetCookie()
spawn() to Serendipity.spawn()
The addLoadEvent() function is unchanged for important BC
All functions of serendipity_editor.js have been put into the "Serendipity" scope, so use Serendipity.getSelection() now instead of getSelection()
The static serendipity_editor.js file has been removed and is now part of the backend theme itself, and can be parsed by Smarty (templates/2k11/admin/serendipity_editor.js.tpl, with templates/default/admin/serendipity_editor.js as a fallback for other backends). It is automatically included in the backend.
The bundled and integrated jQuery no longer uses the noConflict mode in the backend.
A new API function serendipity_smarty_show() is available to easier parse and return a template file
Internal serendipity functions that previously echo'd output now consistently always return the content.
The internal plugins that we stored in include/plugins_internal.inc.php now properly reside as individual plugin directories in the plugins/ directory tree. This allows us to possible maintain core plugins also through spartacus, to push updates to those plugins without needing to wait for new Serendipity releases. An upgrader task migration makes sure that the renamed plugins on the installation will be migrated to the new names.
The entryproperties-Plugin will now purge it's cache when it is uninstalled.
A new section called Maintenance now bundles administrative tasks like import, export on its own dashboard. This new section now also enables admins to purge compiled template files.
Compatibility Changes / Theme developer information
The support for themes using "layout.php" has finally been removed. Themes have not used this for ages, since Smarty was added to Serendipity. Previously the file added it's own "workflow" to the frontend display of entries, but that can be solved much easier through Smarty and a theme's config.inc.php now.
All new backend admin Smarty files can currently be found in templates/2k11/admin/. The alternate XML/XSLT and PHP templates (templates/default-xml, templates/default-php) are still proof-of-concept. Those themes use a "template.inc.php" file to allow substituting the Smarty template API to a custom one. An example for that can be found in include/template_api.inc.php - however this API is so rarely used, that we did not yet properly test it with Serendipity 2.0 and our Smarty3-Framework. Theoretically it still works. So anyone who actually uses it, please tell us if you find issues with it.
A couple of new language constants have been added. If you are a translator, please check the lang/serendipity_lang_XX.inc.php file of your own language (also the file in the UTF-8 subdirectory) and contribute translations. Be also aware that we plan to soon rephrase some of the language constants currently used in 1.7, which will be put to the bottom of the language file for translators to check if they still match properly.
Accompanying Serendipity 2.0 is our new tool Metatron which can perform a number of administrative tasks on the command line. Still in its early stages, Metatron can be helpful for administrators and Serendipity developers. It currently prints out a lot of information about a Serendipity installation, flushes the file cache, and can be used to moderate comments. More features are planned according to user feedback. Metatron is based on the Symfony2 Console component.
We would love for our users to now test our beta candidate. At this point we are very open to user feedback - but we are quite confident that we already provide you with a great updated experience of Serendipity. At this early point of the beta, you should probably only upgrade your productive Serendipity installations to the new version if you know what you are doing and are able to downgrade. Better set up a clone/copy of your blog, or a new experimental blog to test Serendipity 2.0.
Upgrading to Serendipity 2.0 from older versions still works the same like in any other upgrade. Before you upgrade, you should make sure to update all used plugins, so that they work fine with Serendipity 2.0. If you do hit problems, have suggestions or get errors, please do report them on the Serendipity Forums (http://board.s9y.org).
Many, many thanks to the team (in no specific order): onli, YellowLed, mattsches, Ian, and many users on the forums giving feedback and their testing.After a long time of work, the Serendipity team is very proud to announce the first public beta version of Serendipity 2.0. Our main goal for Serendipity 2.0 was to clean up our backend structure, both in terms of coding and especially in terms of design and usability. We firmly believe to now be at a point where we want to show off our hard endeavours, and feel Serendipity 2.0 can now be properly used. The new Backend The most striking difference on the new Serendipity version will be the look of our new backend, patterned to match the 2k11 theme that you might already know from its frontend. We have replaced our old default backend theme with the new one. It looks fresh, is responsive, but still both easy to use and offering flexible customization. In the technical structure of the backend, we have ported all output from internal PHP code to the Smarty template files, so everything you see is now much better separated from the underlying PHP code. Even though this enables
Nach langer Entwicklungszeit ist nun die Beta von Serendipity 2.0 erschienen. Die Ankündigung erklärt nahezu alle Änderungen, deswegen hier nur ein kurzer Überblick: Neues, responsives HTML5-Backend, mit vielen kleinen und größeren Verbesserungen Integri
Tracked: Apr 14, 11:51
Das hat sogar mich jetzt überrascht. Mit heutigen Tag wurde auf der Serendipity/S9y Website die Serendipity 2.0 beta veröffentlicht. Da gibt es einiges Neues. Das auffälligste ist natürlich das neue Backend, dass Matthias Mees, alias @yellowled in einem
Tracked: Apr 14, 18:12
Es hat lange gedauert, aber heute hat Garvin die erste Beta der neuen Serendipity-Version 2.0 freigegeben. Serendipity ist ja bekanntlich die Software, die auch unter der Haube dieses Blogs läuft. Die Änderungen sind oben unter dem Link alle
Tracked: Apr 14, 21:26
Es gibt eine neue S9y-Version, die sich – neben deutlich verbesserten Innereien, von denen ich aber nichts verstehe – vor allem durch ein neues, schickes Backend-Template auszeichnet. Tollkühner Wagemut zeigt sich darin, schon die jetzt erhältliche Beta z
Tracked: Apr 14, 22:13
ACHTUNG: Beta-Version, nur benutzen, wenn Ihr mit einem eventuellen Ausfall Eures Blogs leben könnt! Gestern wurde die Version 2.0.0beta1 von der besten Blogsoftware der Welt veröffentlicht, Serendipity 2.0 beta release. Die Download-Version bei Sourcefor
Tracked: Apr 15, 11:44
Aktuell läuft mein Blog mit Serendipity 1.7.8. Gestern wurde die Beta-Version 2.0 zum Testen freigegeben. Sobald ich ein Backup gemacht habe, werde ich die Beta einspielen und schauen, was passiert. Falls das Blog also demnächst noch merkwürdiger aus
Tracked: Apr 15, 13:22
sounds great, thank you!
However, after uploading the 2.0 beta 2 files (overwriting the previous 1.7.8 installation, all plugins were updated as well, PHP version is 5.2.6), I get the following error message on accessing my blog's index page:
Warning: require_once(__DIR__/composer/autoload_real.php) [function.require-once]: failed to open stream: No such file or directory in /bla/bla/bla/main/bundled-libs/autoload.php on line 5
Fatal error: require_once() [function.require]: Failed opening required '__DIR__/composer/autoload_real.php' (include_path='.:/usr/share/php:/usr/share/pear') in /bla/bla/bla/main/bundled-libs/autoload.php on line 5
What do/did I miss, and what can I do to fix this?
Thanks in advance!
Could it be your PHP-Version is too old? It seems that "__DIR__" (a constant introduced to PHP 5.3.0) is not existing.