Fork CMS 3.3.3 released

Written by Matthias Mullie on Tuesday 3 April 2012
5 comments

Today we released Fork 3.3.3. You can also follow Fork on GitHub.

Changelog

Improvements

Core: added template-modifier to parse widgets.

Bugfixes

Spoon: Multicheckboxes and radiobuttons could have ids with spaces in them. Fixed thx to Anysurfer.
Core: when using Fork in non-multilanguage-mode the links for the internal pages weren't generated correctly, as mentioned on http://forkcms.lighthouseapp.com/projects/61890/tickets/285-editor-adding-intern-links-error.
Spoon: The selected element for a multiple dropdown were forgotten when the form failed.
Core: upgraded the Akismet class, which fixes an error of double encoding, as mentioned on https://twitter.com/#!/tellyworth/status/180138255340142592.

Comments

Jean wrote 12 years ago

You should write a more detailed tutorial on theming, this would greatly increase the number of users of Fork-CMS.

joshua wrote 12 years ago

I would like to see a auto upgrade feature to allow fluid upgrades

Frank Fechner wrote 12 years ago

Every time I'm editing an page (new or existing) i get the following error:

Internal error

There was an internal error while processing your request. We have been notified of this error and will resolve it shortly. We're sorry for the inconvenience.

I assume you are not getting informed because this development machine sits behind an firewall and cannot connect into the wild or send email. also there is absolute no logging information (php-error.log, syslog, apache, or in any logdir of fork cms).

The system is an Ubuntu precise (development branch) (GNU/Linux 3.2.0-16-generic x86_64) completely patched running also typo3 ;) sitting on a VMware host.

will try it on an mamp on my macbookpro tonight...

Frank Fechner wrote 12 years ago

Results on my MacBookPro with MAMP (most recent version): it works just fine. No internal error so far.

mlitn wrote 12 years ago

Frank: we are indeed not informed. If anything goes wrong, an email is sent (if it gets out, past your firewall) to the email address specified in library/globals.php

You could also change the value of SPOON_DEBUG to true (same file) to display the error(s) that have occured. If you'd be so kind to create a ticket at http://bugtracker.fork-cms.com then, with the errors :)