Im developing a shopping cart system for PyroCMS, but moving my code to 2.2.1 is causing me a few headaches.
I cant find any links that describe the technical changes or how to migrate my existing code over to it.
Is there a public list of technical changes that I can use as a reference?
thanks in advance.
this is the change log, you can take a look at new changes
http://docs.pyrocms.com/2.2/manual/reference/changelog
Upgrade guide from 2.1.x to 2.2.0 (note step 8 for addons)
Upgrade from 2.2.0 to 2.2.1
Essentially 2.1 to 2.2 needs some care, 2.2.0 to 2.2.1 should be a straightforward backup and replace of the system directory if you're not using Git (if you do have the time/ability to learn/use Git, it's hugely beneficial for keeping track of changes).
…and of course always do PyroCMS upgrades on a dev server because it invariably breaks in a way you're not expecting.
Related
My team has just upgraded from SpringBoot 1.5.12.RELEASE to 2.4.1 but only to discover that a few days after this major upgrade the documentation references for 2.4.1 have suspiciously and unexpectedly vanished from the documentation page at https://spring.io/projects/spring-boot#learn
We cannot afford that frequent upgrades.
The current GA release is 2.4.2
Why did 2.4.1 disappear?
Was there something fundamentally wrong with 2.4.1 that we should be aware of?
Is there a release plan we can follow going forward?
The Spring project pages only list the most recent patch versions.
I believe this answers my question.
I'm working with a Grails application version 2.2.4 and I need a procedure for upgrade to latest version (I hope it can be possible). I have thought as a first step to follow the indications of the official site, but that let me to upgrade to version 3.
I'd like to know if anyone already did it or have experience about that. How long take it?, the process and the main problems.
Many thanks in advance.
I think you need to follow both upgrade instructions. the one for 3.x and the 4.x.
start with the 3.x and them move to the 4.x changes.
Another approach I think may be better is to start an empty 4.x application and then start moving you code there. also check first that all the plugins that you are you sing have 3+ version.
The effort required to upgrade can change massively depending on multiple factors, including the size of the project, the quality of the original code, were plugins used and if so have they been updated or will the functionality need replacing, were deprecated taglibs used, e.g remoteFunction etc. etc.
There is not a great deal of difference between 3.x and 4.x so it makes sense to upgrade to 4.x.
Tackle it in stages from the basis of a new project, attempting to rebuild the project between stages.
Reestablish configuration, you don't have to use application.yaml (the default in 4.x) so can create an application.groovy with the same parameters as per your old project.
Move over domain objects but use a new database URL, compare the schema's between the old db and new db to ensure the database is the same. Unless you don't rely on GORM to recreate/update the schema.
Move over any other source and command objects ensuring the project will build. You may need to modify buildconfig at this stage to bring in dependencies and plugins.
Move over services, ensure all compiles and make sure transactions are behaving as intending.
Move over controllers ensuring any tests run successfully.
Move over the views.
Hopefully if the project is still building at this stage, you can run it!
I need Propel 1.3.0 for my existing php and mysql versions to create model classes. From where I can download Propel generator 1.3.0?
Your help is appreciated
Thanks
The oldest I could find was 1.7.1
https://github.com/propelorm/Propel
I have a copy of 1.6.7 but that's the oldest I have
Up to 1.7.1 does have a lot of backward compatibility, it was only when they went to Propel 2 that things really started to break. There were changes at 1.5, but they were relatively minor.
I have a large project running on Laravel 4.2 and now I would like to upgrade it to the latest release (5.4)
On the upgrading guide I can see the steps to upgrade from each release to the next one, but the 4.2 to 5.0 requires a fresh install. Hence the question: should I install 5.4 (and fix problems) or 5.0 (running each upgrade)?
I'm possibily using any Laravel functionality, and have organized repositories for my own custom methods; I also need to maintain the database. I need to upgrade because I would like to use event bradcasting with Laravel Echo.
Thanks
To those looking for an answer: update directly to latest version, then fix changes along the way.
Explanation:
At first I tried to upgrade version by version; it was a pain. Every single vendor had different packages for each version and that caused issues even before correcting the code. I couldn't start fixing my code because the installation requirements of the vendors were failing at a certain point of the upgrade process.
Upgrading directly to latest version requires the correction of many things, but at least those are only related to your code. In my case I had to remove Sentry (authentication), Laravel OAuth, and some others I don't remember in favor of some native packages which I hope will be maintained properly. The upside of this approach is that once you have all the packages you need installed you can work directly on your code... which is what you have to do anyway.
I'm updating a Joomla page for a friend of mine - and the version currently online (when it's not being brought down by hackers) is 1.5.20. As far as I can see, there are no update patches available to bring this up to date. I'm aware that I can't update this to a 2.x or a 3.x version, but if I at least could bring this up to the newest version of the 1.5.x releases, that'd be good for security.
So, what patch should I choose, and where can I find it?
From the Joomla docs;
If you are on the version prior to the current one, use the file that updates from the prior version to the current version (for example, Joomla_1.5.25_to_1.5.26-Stable-Patch_Package).
If you are on an older version, use the 1.5.0 to current version file (for example, Joomla_1.5.0_to_1.5.26-Stable-Patch_Package).
In your case, since you currently have 1.5.20 and 1.5.26 is the latest 1.5.x version released, the latter would be the correct choice.
Further update instructions are at the above linked docs, read them first, esp. when it comes to backing up the existing site.
There is no patch to upgrade from any Joomla 1.5 version to the current release.
The current Long Term Release (LTR) is Joomla 2.5, the lastest Short Term Release (STR) is Joomla 3.0.
Both of these are not directly upgradeable from any 1.5 version.
Your best bet would be to migrate using a tool such as:
http://extensions.joomla.org/extensions/migration-a-conversion/joomla-migration/15609
Please note that Joomla 1.5 is now unsupported, with no security patches issued to fix any vulnerabilities. Your Joomla 1.5 install will be getting unsecure, very quickly.
As Joachim said, backup first, restore at your leisure.