Monat: April 2016

I worked a bit on the way the educational add-on creates URLs for new projects. It uses the title of a project now. I added also a feature to validate the project name uniqueness. I’ll work on the view of the projects next time.

I worked again with the index and search feature of Plone to finish the search function in the new add-on that could be the main part of a new LibreOffice educational site. I fixed the last bits and added some more entries to the categories fields. The index is working fine now. Committed my changes under GPL to TDF’s github repository.

I worked with the index and search feature of the Plone add-on for a LibreOffice educational site. I added also some more dexterity form fields and changed some field names. The search feature needs another day of love.

I worked a bit further on a Plone add-on that could be used for a website with educational content provided under free licenses. The add-on itself will be available under GPL.

I worked with the portal catalog of the current LibreOffice extensions and templates website to search for content that is not already set to language independent. There are some extensions and template projects and releases that has not this metadata. I changed some of them to that label today.

The current LibreOffice extensions and templates website runs with custom Plone ATContent-Types. The ATContent-Types were the default content types for Plone up to version 4.3.x. The new Plone 5.x versions uses the new Dexterity content types as default. The new LibreOffice extensions and template website will also use (customized) Dexterity content types. Thus the content from the current website has to be converted to the new framework. I currently investigate a simple and easy way to do this conversion.

I got already a local copy of the site content running with a newer Plone 4.x version and will investigate the further steps to map the types and fields from the current content types to the new ones.

I added more dynamic content to the new front-page and worked a bit on translation of strings. I added another language to my Plone instance and played a bit with the language settings and the view. The instance shows a dynamic page with translated strings to the user now.

The localisation files are located in the locales subdirectory. First I had to create a pot-file with i18ndude and then sync this file for every language with a po-file in language specific subdirectory. The translation itself was done by poedit, which creates the mo-file too. Once the mo-file is created I had to restart the Plone instance and my translated strings are there.