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.
Related
I had to remove Tosic Dll's to get the server to boot. Tried restoring old Dll's; (I made a backup) and Desktop Modules files. I have tried to install an older package: that resulted an error message saying newer version installed.
Any help would be appreciated.
Given the details you've detailed so far; the install and then manually changing/deleting things "under the hood" - I am pretty sure the only way forward is to restore from a backup from before you installed 2sxc.
Dnn and the modules/extensions have no concept of undo or rollback from installs or upgrades.
To rollback an unfortunate upgrade, just do this:
In DNN go to the Extensions and set the version of "Content" and "App" down to a version before the version you want to go back to.
See checklist: https://azing.org/2sxc/r/6z3lel3k
help regarding the issue below would be really appreciated :
Command 'Q#: Create new project...' resulted in an error (Running the contributed command: 'quantum.newProject' failed.)
I was trying to follow this exercice : https://learn.microsoft.com/fr-fr/learn/modules/qsharp-create-first-quantum-development-kit/2-install-quantum-development-kit-code
after downloading and running the latest versions of .NET CORE, VSCODE, I can run "Q# Install command line project templates" but can't run "Q# Create a new project : See screenshot1 screenshot 2 CODE SOURCE ERROR
I already done this exercice in May last year but for some reasons I get stuck at the very beginning of the process now.
Could it be a version issue ? I remember that the tutorial was different (May 2020) than the one above I shared to you. Unfortunately I can't find the previous tutorial as it has been updated since.
I tried to uninstall the latest versions to reinstall the versions I downloaded in May : useless, I get the same issue.
Many thanks for you help !
I decided to go with an older version v0.14.2011120240
It seems the new version isn't stable yet.
Install NodeJS: https://nodejs.org/dist/v14.15.4/node-v14.15.4-x64.msi
Then restart VS Code.
"The below steps currently has a dependency to install node.js including npm. We are working on removing that dependency. Alternatively, use our the command line templates to create a Q# project , or use Visual Studio."
https://learn.microsoft.com/de-de/azure/quantum/install-command-line-qdk?tabs=tabid-vscode
I am planning to upgrade artifactory-pro from 4.14.2 to 5.7. Has anyone done this so far? We use npm, bower, debian, yum repositories. Any recommendation or insight is appreciated.
As I see it, the upgrade depends on two main factors:
Your installation type(ZIP/RPM/RPM OSS/Debian/Docker). Here you can find detailed instructions for each type:
ZIP installation
RPM installation
RPM OSS installation
Debian installation
Docker installation
In case you use an HA cluster, here are the instructions.
While no special operations are required except those are mentioned in the instructions - please pay attention to updates and other special instructions since there are specific instructions to upgrading from Artifactory 4.x to 5.4.x and above. As can be seen here (for example).
Like in any other upgrade process, make sure you have a full system backup (Artifactory configuration, metadata, and artifacts)
I have deployed graphite with nginx some time ago, with chef, but didn't froze versions to be installed. Thus now, trying to install with the same recipe i get errors because of missing something related to versions.
I need to find what version of Graphite I have installed on my other CentOS machines, to be able to figure out how to repair recipe.
Thank you.
Gabriel
If you have web access to the Graphite installation, you can also see the currently running version under the /version/ path.
I had the same issue. I solved it running a pip list, which displays every package you installed with pip. You can also run pip show graphite-web or pip show whisper to get more specific information.
I am having a sudden issue with installing Plone 4.2.4. I have pinned PloneFormGen to 1.7.11 but the buildout fails with the following error:
The version, 1.4.4, is not consistent with the requirement, 'plone.app.jquery>1.6'.
While:
Installing client1.
Error: Bad version 1.4.4
If I remove PFG from the buildout, it runs fine. I have pinned plone.app.jquery to 1.7.2 (even though it states its not compatible with < Plone 4.3) and the buildout runs successfully, but afterwards, if I update PloneFormGen from 1.7.6 to 1.7.11, it breaks the site.
The buildout is a standard Unified Installer build of Plone 4.2.4, using the out of the box version.cfg. I have extended this with my own config to add other components.
This build recipe I created months ago and it has worked flawlessly on other systems, but my most recent use of this recipe gives me the failures.
Any ideas would be greatly appreciated.
UPDATE:
I found an email on the Plone Users group by someone who was having a very similar issue to this. The fix seems to be to pin plone.app.jquery to 1.7.2 as well as pinning collective.js.jqueryui to 1.9.2.0. I did this and the issues I was experiencing appear to be resolved. However, I'm not comfortable with this solution as it appears to be an underlying issue with these two packages.
As you mentioned in your question update, you need to additionally pin plone.app.jquery to a newer version.
This is a fine solution and, if anything, PloneFormGen is just lacking in documentation so people are aware of it.
Please consider contributing to the README to help provide better instructions to install on the version of plone you're using: https://github.com/collective/Products.PloneFormGen/blob/master/Products/PloneFormGen/README.txt