A new branch of Zenario is now publicly available, with some small improvements in a few areas of the CMS.
If you have signed up for an API key for Google ReCAPTCHA, there's now an option to enable a CAPTCHA on Zenario's admin login screen.
The administrators panel in Organizer now shows which admins are currently logged in.
If your screen is wide enough, selecting an item no longer hides the buttons for a panel. When an item is selected, you will see the buttons for the selected item alongside the buttons for the panel.
We've added quick links from the Content Items Panel and the Users Panel to the site settings that affect those panels.
You can now customise any phrase that a plugin uses directly from its settings box.
(Note that this is a separate feature to translating phrases, and that if you have a multilingual site you can customise phrases and then also translate the customise phrases separately.)
Email templates have had a small redesign. They can now use a common header and footer.
Using a common header/footer means that you can easily achieve consistency in all of the emails that your site sends, without needing to edit multiple email templates to keep them in sync.
If a PHP warning/notice appears on a page, you'll now receive an email to the support address (limited to one email per web-request).
By default, Zenario will no longer send emails using base-64 encoding.
If this change causes problems, you can switch this back on in the Email site settings after updating to this version.
If a plugin uses a custom framework, and the custom framework is missing in the filesystem, Zenario will no longer silently fall back to the default framework when displaying the plugin. Instead an error message will be displayed on the page.
We've added two new functions to help control the email alerts mentioned above:
ze::ignoreErrors()
You can call this this function to disable the "PHP error at" emails from being sent.
ze::noteErrors()
You can call this function to re-enable the error emails.
You can use these functions if you have a bit of PHP code that regularly generates random warnings/notices, and you don't want an email being sent to the support mailbox each time.
You should call ze::ignoreErrors() to start suppressing errors, and ze::noteErrors() afterwards when you are done.
Note that these calls can be nested; i.e. if ze::ignoreErrors() is called twice then ze::noteErrors() must also be called twice before errors stop being ignored.