I updated my local instance from the new Plone 5.2 with the latest changes, created a copy of the Barceloneta theme and made some edits on its styles. It worked as expected. I could view my changes directly. Great tool!
I expanded the buildout from the Volto Github repository with one of my former Plone addons: tdf.extensionuploadcenter and added a new default view for it inside my own Volto app. I use this new view to improve my knowledge on Volto.
I made a quick test with a currently published LibreOffice extension and it seemed there were no accurate review of the file before it and the project were published. Sad situation.
I read about a new Plone UI named ‘Volto’ and created a new instance from the Github repository: https://github.com/plone/volto
I had to install node.js and yarn on my notebook. I created a new volto package with ‘create-volto-app my-volto-app’. I could build my volto app with the command ‘npm start’. This build everything and the instance is available at port 3000 of your URL, e.g. ‘http://localhost:3000’. But you need to fire up the Plone instance too with e.g. ‘bin/instance fg’ too (otherwise you will get error messages).
The screenshot above shows the Plone site within a resolution for mobile devices. The Volto app uses the Pastanaga theme and is ‘mobile first’.
I finished my migration of a first Plone addon some a week ago sucessfully and started with migration of a further addon, collective.dexteritytextindexer to Python 3 compatibility. I was able to migrate the source code of the addon itself, but run into issues with the behaviors test script. The tests ran successful on Plone 4.3 to 5.2 and Python 2.7, but failed on Plone 5.2 on Python 3.
I worked on my first migration oft a Plone addon to Python 3 during the last days. There were some instructions available on Github how to procide and I followed them. I was able to run the addon inside my local environment, but I got some issues with the continous integration test on Travis-CI, once I submitted a pull request. I had to fix the scripts inside the addon for building and testing on Travis-CI and was successful with the great support from a member of the Plone community. He merged my pull request and released a new version of the addon cioppino.twothumbs today: https://pypi.org/project/cioppino.twothumbs
I usually don’t configure a mailhost for my local development environment. Thus I use the Products.PrintingMailHost to stop Plone from sending out emails and print into the shell instead.
I read about the porting work of this product/tool to Python 3 on:
https://www.starzel.de/blog/python-3-and-more and wanted to try this version out. I added the product to my buildout script ‘local.cfg’ but without success. Buildout fetched the product and I could change its branch to ‘python3’ but it had didn’t work. Its patch wasn’t applied to the Plone mailhost.
I solved this issue by adding ‘ENABLE_PRINTING_MAILHOST True’ to the ‘environment-vars =’ entry of the ‘[instance]’ of ‘core.cfg’.
It looks as follows yet:
environment-vars = zope_i18n_compile_mo_files true ENABLE_PRINTING_MAILHOST True
The printing mailhost is working as expected yet.
I created a new clean buildout from the Plone coredev Github repository using a checkout of the 5.2 branch. I added a local.cfg file to my local repo and added some packages to this file. This packages were checked out within the next run of buildout using the new local.cfg buildout file, extending buildout.cfg.
I created the local.cfg using the pointer from this webpage:
I added a further section to the local.cfg for ‘mr.bob’. Thus my local.cfg looks like this:
[buildout] extends = buildout.cfg parts += mrbob always-checkout = true custom-eggs += collective.dexteritytextindexer bobtemplates.plone test-eggs += collective.dexteritytextindexer [test] auto-checkout += collective.dexteritytextindexer bobtemplates.plone [mrbob] recipe = zc.recipe.egg eggs = mr.bob bobtemplates.plone [sources] collective.dexteritytextindexer = git git://github.com/andreasma/collective.dexteritytextindexer bobtemplates.plone = git git://github.com/plone/bobtemplates.plone.git
I created a new branch inside the collective.dexterity local repository with ‘git checkout -b python3’ and did on this branch the steps that are described on this website:
I run sixer and python-modernize on the package and was able to get it running with Plone 5.2 on Python 3.6. I already created a new Plone site from scratch for this.
Then I created a new Plone add-on package using mr.bob and run sixer and python-modernize against the new package. Once this was finished I added the package to the local.cfg buildout script and run buildout again. I was able to start the Plone site with ‘./bin/instance fg’ without issues again. I installed the new addon within the ‘Site Setup’ page of Plone. The new addon had no real content at that time (only the necessary boilerplate / template).
This created the environment to migrate the current state of my Plone addons to the new Plone 5.2 version and Python 3. This migration is necessary because the support for Python 2, currently used by Plone, ends within a year.
It’s interesting how much spare you gain once you withdraw from a busy message environment. This helps to invest more time into more healthy acitivities (like outdoor runners training). It makes it also possible for me to concentrate more on improving my skills on Plone and Python and work on the migration of Plone addons to the next Plone main release, 5.2, running on Python 3.
And it is also interesting to notice the difference between the official speach of people about the volunteer work you have done and the real rating of that work. That helps to reclassify things and justify my direction.
I started with my work to migrate a first Plone addon to Plone 5.2 on Python 3. I did this work on the addon cioppino.twothumbs. I first applied ‘sixer’ on it and than run ‘python-modernizer’ as described on this page. But I got some errors with the imports afterwards, once I started the Plone instance with ‘fg’. This imports were implicite relative. I changed them to explicite relative or absolute. The addon is running yet in the Plone instance. But there is a remaining issue with the css-file of the addon. I pushed my changes to the new git branch ‘python3’: https://github.com/tdf/cioppino.twothumbs/commits/python3.