SCHLIX CMS 2.1.7 build #2 has been released

SCHLIX CMS v2.1.7 build #2 has been released today to fix some minor bugs:

  • Fixed: CSS on installer page
  • Fixed: Dropdown box CSS not visible on Chrome
  • Fixed: Slideshow ~ ensure data directory exists before upload
  • Fixed: Slideshow ~ drag and drop (1st item)
  • Fixed: Blog ~ drag and drop (1st item)
  • Fixed: Menu block ~ added block name in front of id (e.g. block_topnavigation_id-1) to handle a case where some themes use more than one block in one page
  • Enhancement: Frontend edit control now shows Options instead of just icons for better visibility

SCHLIX CMS 2.1.7 released with new look and feel

SCHLIX CMS v2.1.7 (build #1) has been released today. The base theme has been changed to dark by default, inspired by KDE's Dark Breeze and Ubuntu's Unity theme. The light theme will still be available as a separate download at the end of December 2017 (or maybe January 2018) and you can customize it with your company logo. This will be useful for web design agencies and freelancers out there. In addition to this, there is already a custom admin theme that you can download from the Themes directory.

Other important changes:

  • Fixed some of the Macedonian and Indonesian translations.
  • Fixed URL for content fragments for Landing Pages. The URL will be set to / instead of /lp if the frontend application is set to Landing Pages. If your frontend application is set to Web Pages (html), this will not affect you. For the change to take effect, you must manually edit the menu item from Menus and save it.
  • Enhancement: Contact form is now using fully AJAX so it can be inserted in the middle of the content.
  • New InsertContactForm macro to embed contact form in the middle of any content text

Download now


SCHLIX CMS 2.1.6 has been released in 35 languages

SCHLIX CMS v2.1.6 build #1 has been released. Other than bug fixes, the highlight of this release is its first ever localization of SCHLIX CMS. We have decided to shift the priority for our e-commerce system to the end of second quarter of 2018 so the core of SCHLIX CMS could be translated into 35 languages: Belarusian (Беларуская мова), Bulgarian (Български), Chinese Simplified (简体中文) and Traditional (繁體中文), Croatian (Hrvatski), Czech (Čeština), Danish (Dansk), Dutch (Nederlands), Estonian (Eesti), Filipino (Tagalog), Finnish (Suomi), French (Français), German (Deutsch), Greek (Ελληνικά), Hindi (हिन्दी), Hungarian (Magyar), Italian (Italiano), Japanese (日本語), Korean (한국어), Macedonian (Mакедонски), Norwegian (Norsk), Polish (Język polski), Portuguese (Português), Romanian (Română), Russian (Русский), Slovak (Slovenčina), Slovenian (Slovenščina), Spanish (Español), Swedish (Svenska), Thai (ไทย), Turkish (Türkçe), Ukrainian (Українська), and Vietnamese (Tiếng Việt),

Please note that there may still be some mistranslations, however we are planning on correcting these until the end of December 2017. System translations for Right-to-Left languages (Arabic, Hebrew, Persian, etc) will be released at the end of Q1-2018 once we have consulted with subject matter expert since we don't have an in-house expert for this.

You can change the language by clicking Global System Configuration or simply click Change under System Information.

Change Language in SCHLIX CMS

Localization in SCHLIX CMS v2.1.6 (September 2017)

Special thanks for Jarrod Farncomb from Datacom TSS (Australia) and Gjoko Krstic from Zero Science Lab (Mакедонски) for helping us test v2.1.5-4 before v2.1.6 release and pointed out possible bugs.

The following items were fixed and/or added: 

  • Fixed: blog URL could be empty when saved
  • Fixed: typos in the language string
  • Fixed: tags resulted in 404 errors
  • Fixed: new macro/block installation did not refresh the content immediately and would not show up until the next reload
  • Fixed: duplicate tags in applications table during upgrade
  • Fixed: adding www during installation caused www.www to be written in the multisite-config file
  • Removed: default site meta keywords and meta description from the sub-site config file (moved to inside individual applications)
  • New: ability to change language and other site information from the main admin page
  • Enhancement: add some icons to item edit form for Blog and Web Pages for better visual cues

Download SCHLIX CMS v2.1.6 now.

If you are upgrading from a previous version, simply click Settings, then click System Update. Please note that due to session name change in this version, you will be automatically logged out after the upgrade.

Errata - SCHLIX CMS v2.1.5 build #4 fix typos

SCHLIX CMS 2.1.5-4 (build #4) has been released to fix the bug in system updater for non-CURL based system as well as typos on the table names in the installation.

SCHLIX CMS 2.1.5 released with new features: JSON feed and Open Search

SCHLIX CMS 2.1.5 has been released today with new features: JSON Feed (in 'blog' application) and Open Search (in 'search' application). JSON Feed was recently created by Brent Simmons and Manton Reece and we want to encourage the adoption of JSON Feed, since it is lighter than RSS. OpenSearch XML was also added to the search application. We have also added the JSON feed link to the two sample themes included in the release.

Other than the two new features, most other changes in this release have been focused on bug fixed on Windows/Apache/PHP (IIS/PHP have always been okay). Apparently there have been some issues for development under Windows using WAMP Server and EasyPHP. This is due to the default thread stack size in the default Apache settings if you use mpm_winnt_module. We have issued a workaround specifically for development servers in Windows using WAMP Server and Easy PHP. IIS/PHP/MySQL stack, Linux and OS X stacks are not affected.

Errata - SCHLIX CMS v2.1.4 build #2 fix for menus

SCHLIX CMS 2.1.4-2 (build #2) has been released to fix the bug when creating a menu item from an item inside a subcategory.

Roadmap update for July - December 2017

Back in January, we announced our plan for the first half of 2017. 5 out of 6 have been completed. We have to postpone the development of integrated market application until January 2018. The following is our updated road map:

July - December 2017

  • New extension: e-commerce (full shopping cart). We should have this completed before the end of December 2017.
  • New extension: forum (das Forum). Currently, we are already using this forum extension and it will be released publicly before the end of December 2017.
  • Update to the official Jäsenlehti Newsletters extension to include additional features such as bounce checker, analytics, and click tracking.
  • A concrete example of backend admin theme where you can customize the logo (this is intended for web development agencies as well as freelance web developers).
  • More extensions that can help you with your SEO (search engine friendly). e.g. Open Graph.

January - June 2018

  • Translation for the following languages: French, Spanish, Portuguese, Russian, Simplified Chinese, Japanese, Korean, and Indonesian.
  • Integrated market app where you can install/uninstall extension automatically.
  • More integration with cloud based services
  • More themes

July - December 2018

  • SCHLIX UI v2 implementation (already in the works). SCHLIX UI is the Javascript framework for our user interface
  • More to be announced.

Official extension update: Plugin Creator and Newsletters

As per our previous post, we have released Jäsenlehti Newsletters. Despite its BETA status (not final release), the extension is fully functional and has already been used with one of our clients. We will make an update anytime between November or December 2017 to add the following:

  • Export express consent records
  • Bounce checker
  • Analytics
  • Click tracking

SCHLIX CMS Newsletters extension

An update has also been made to Plugin Creator. You can now create sub-applications. A sub-application is an application inside the main SCHLIX CMS Application. As you can see in the screenshot above, the "Subscribers" sub-application within Newsletters. Please note that you must first save the application in Plugin Creator first before you can create a sub-application.

SCHLIX CMS 2.1.4 has been released (updated installation options)

SCHLIX CMS 2.1.4 has been released today. The following is the list of changes:

If you change the Main application for the frontpage settings (from the main administration page » Global System Configuration), the application will now appear above Web Pages (the default frontend application). Prior to v2.1.4, you have to click Applications and select it from there regardless of its status as the main application for the frontpage.

Change frontpage application

As you can see below, now Landing Pages is shown above Web Pages.

Change frontpage application

There is also a new option visible in the installation to allow you to enable SSL by default, especially since some hosting control panel have the option to offer Let's Encrypt SSL certificate for free. Previously, this setting has to be edited by hand after the installation. 

The other option is to make the domain name accessible with and without www. (Please note that the host name below is a local host and not connected to the internet, so the option does not make a difference). In production environment, you are recommended to check this option by default. Previously, you have to add the www. manually to to (unless the multi-site is disabled and a wildcard is specified in that file) and it will return a white screen with the following error message: There is no website configured at this address.

New install option

Other than that, there is a bugfix for TinyMCE where upon closing the source editor (CodeMirror), it will add an empty paragraph tag (<p>&nbsp;</p>) at the top. We have now set as the default option to set force_p_newlines value to TRUE and forced_root_block to FALSE and these options can no longer be changed.

Errata - User Registration fix - SCHLIX CMS v2.1.3 build #4

We have released SCHLIX CMS v2.1.3-4 (build #4) to fix a bug in the user registration process where the email was not queued properly.