Which good version combination of RelStorage for Plone 5.x - plone

I tried to install Plone5.1RC1 / RelStorage2.x / psycopg2.7x, but I got an error. then I tried to install Plone5.0x / RelStorage1.6x-2.x / psycopg2.7x, but I got an error.
Please let me know, best version combination of RelStorage for Plone 5.0.x and Plone 5.1.

For Plone 5.0: Relstorage 1.6.3
For Plone 5.1: Relstorage 2.0
However, be sure to have your Python version up to date. (>=2.7.9) or you'll have an issue with Plone 5.1 requiring ZEO 5.1.1 and Relstorage requiring ZEO < 5.0
Source: https://github.com/zodb/relstorage/blob/5ab2840552066d0cca4db85ac8b51041ef778357/setup.py#L127

Related

Update QSSL libraries in order to use OpenSSL 3.x

I've installed Qt 6.3 in Ubuntu 22.04 and I discovered this:
Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x)
The backend "cert-only" does not support QSslKey
Active TLS backend does not support key creation
As far as I understand, that means,Qt 6.3 was built with the old OpenSSL 1.x, but my systems have the newer 3.x.
Because I can't wait the next fall for Qt 6.4 I ask if there is a workaround to fix this issue.
Is it possible to re-build only this module with OpenSSL 3.x and overwrite the libraries?
Any other suggestion?

Error occurs when updating to meteor1.4

My current version is 1.3.5, and I tried to update my meteor to 1.4.
However it stop in lineļ¼š fourseven:scss 3.8.0 1.
I think I install meteor 1.4 successfully.(i'm not good at English...)
Try to reinstall and be sure to have proper internet connection

old plone 2.5 dump on mavericks or ubuntu 12.04

i have a folder with an old plone version 2.5 and i would restore it on mac os mavericks or ubuntu 12.04. I know, that this really old plone version need python 2.4. I get it form python.org for mac os x but i don't found anything for ubuntu 12.04. I tried to restore this dump but it's not easy without a good documentation for version 2.5.
How can i restore this dump?
Start with an installer from https://launchpad.net/plone/2.5/2.5.5 . That will take care of not only Python, but also handle other binary components.
Install Plone on the target server, then transfer any custom add-on Plone products from the source server. Test it.
When that's running, copy the Data.fs file from the source to overwrite the Data.fs on the target.

Using Products.ResourceRegistries 2.1.2 on plone 4.1.4

I would like to use plone.app.jquery 1.7.2 on my plone 4.1.4, but it doesn't work because plone 4.1.4 use an old version of Products.ResouceRegistries that doesn't enable the "bundle" option.
So I figure myself that I have to update Products.ResouceRegistries to 2.1.2.
I have modified the versions.cfg and run buildout, but with no effect (no download of the new version).
How could I update the version ?
Why not just upgrade to Plone 4.2?
The problem was there is a kgv in the buildout that pinned Products.ResouceRegistries to 2.0.6 :
http://good-py.appspot.com/release/dexterity/1.2.1?plone=4.1.4
Removing the ?plone=4.1.4 and pin Products.ResouceRegistries to 2.1.2 make it works.

Upgrading Plone 4017 to 4018

I really need some help with Plone. I am experiencing some issue upgrading from 4017 to 4018.
All the Plone websites say "The site configuration is outdated and needs to be upgraded."
When I press Upgrade I get the following error:
"Starting the migration from version: 4017
End of upgrade path, migration has finished
The upgrade path did NOT reach current version
Migration has failed"
I was really hoping someone could help me sort out this issue and also help me get to the latest stable build of Plone 4.1.
Thanks.
This happens when there is a discrepancy between the current Plone setup profile version number and the upgrade steps final version number. Because there is no step from 4017 to 4018 you get this error message.
This is not necessarily a problem. Your upgrade to version 4017 worked without a hitch. What exact Plone version are you upgrading to, 4.0.9? It may be worth reporting this as a (low priority) bug, but I doubt there is anything there to prevent you from using your site.
To illustrate, I see this all the time when using the latest development version of the Products.CMFPlone package, because that'll be one version 'tick' further than the latest release of the plone.app.upgrade package can upgrade me to.

Resources