Can I upgrade my SuiteCRM instance to any version or I must respect the order of upgrades, for example to upgrade from 7.4.3 to 7.7.9
Do I have to upgrade first from 7.4.3 to 7.6.10 then from 7.6.10 to 7.7.9 or I can upgrade directly from 7.4.3 to 7.7.9 ?
Thank you very much.
The SuiteCRM Downloads page has a list of upgrade version options, currently this lists:
SuiteCRM-Upgrade-7.8.x-to-7.8.3
SuiteCRM-Upgrade-7.7.x-to-7.8.3
SuiteCRM-Upgrade-7.6.x-to-7.8.3
If your on a version previous to any of those listed, you will need to upgrade to one of the previous upgrade packs also listed, then upgrade from there to current.
So for example you want to go from 7.2 to 7.8.3, you will need follow the following upgrade process:
SuiteCRM-Upgrade-7.2.x-to-7.3.2
SuiteCRM-Upgrade-7.3.x-to-7.4.4
SuiteCRM-Upgrade-7.4.x-to-7.6.10
SuiteCRM-Upgrade-7.6.x-to-7.8.3
Related
I want to update my TYPO3 8.7.8 to the v8 LTS, but i can't seem to find any way to do this via the Backend. Do i need to manually install the new version as a fresh installation?
You don't need to add TYPO3 Source manually if you have create symlinks in your typo3 installation and already running with TYPO3 Version 8.7.x.
If your TYPO3 Version running in 6.2.x Then First you need to upgrade TYPO3 Version 7.6 and after TYPO3 8.7. You can't upgrading Directly version 8.7 if your systems is running in 6.2.x.
Just you need to follow below steps.
Login TYPO3 BE and Go To Install Tool.
In Important actions you see the Check for core updates button. click on this, Here you can find latest TYPO3 version.
After download latest TYPO3 Version. Click on Compare current database with specification and update typo3 core Database.
After compare DB Go to Upgrade Wizard and perform all required steps.
Note: When performs all above steps first you need to take a backup of your database. So, in case of any problems then you can restore old DB.
Follow the upgrade guide in the docs
https://docs.typo3.org/typo3cms/InstallationGuide/Upgrade/Index.html
I installed the payum/payum-bundle with composer (using the PHP Storm Plugin).
I couldn't install a version newer to 2.0.1 because the newer version seems not to be marked as stable (minimum-stability in composer.lock is "stable").
I too installed the payum/paypal-express-checkout-nvp bundle to add paypay express support.
I set everything up, created a controller to test it and ended up getting the error
Attempted to load trait "GatewayAwareTrait" from namespace "Payum\Core".
Did you forget a "use" statement for another namespace?
According to this (closed) issue the problem seems to be that payum/core is at version 1.2.8 but should be at least 1.3
https://github.com/Payum/PayumBundle/issues/367
Obviously the payum/bundle installation in version 2.0.1 installed the core-part with 1.2.8.
Now... How can I force composer to update the payum/core to at least 1.3?
What I need to do is either tell composer to ignore the minimum-stability for this single bundle or to set the minimum-stability to something less then stable (which I assume not being the best idea especialy when not permanently following all dev branches of all used packages) and a hint on how then to update the payum/core part.
Any hints are very wellcome - I am stuck here...
Your assumption is wrong, the version 2.1.0 of payum/payum-bundle is marked as stable.
In order to find out why you don't install it, we need your content of composer.json.
Did you run composer update in order to try to update to the latest packages of everything?
Since 1.3.0 Payum require a virtual package http client. You must add one of its implementations as a package, after that composer will allow you to upgrade payum.
The doc suggest you to install php-http/guzzle6-adapter but you can choose any other implementations of the client.
Do
php composer.phar update payum/core php-http/guzzle6-adapter
I use grafana 2.1 and created multiple dashboards, templates etc.
I would like to upgrade to grafana 2.6. Is there any way to upgrade to 2.6 without affecting the existing dashboards?
There are no breaking changes between 2.1 and 2.6. In theory upgrading should be a simple matter of installing the new packages. I personally have upgraded from 2.1.3 to 2.5 to 2.6 with no issues.
For windows version, I just had to copy the data/grafana.db and the data/plugins directory from the old installation to the new installation directory. Just make sure the newer version does not have any breaking changes.
You can upgrade Grafana to higher versions for better features and also import your previous dashboard to the new version without any problem by using Import/Export feature.
I am trying to update my product to a later version. Let's say product I am trying to update is at version 1.0.0 and there are two update sites available, one that has version 1.5.0 and another that has 2.0.0. Both update sites are in the update site manager. When I click "Check for Updates" I find only version 2.0.0, not 1.5.0. If I disable update site for 2.0.0 then 1.5.0 shows up during update check. Is there a way to control what updates make into available updates? Is there way to make it so both 1.5.0 and 2.0.0 show up so I can choose?
The short answer is "no". The check for updates feature is not designed to give user a selection of versions. In Juno and earlier, it will attempt to update to the latest known version and fail if that's not possible. In Kepler, it will attempt to update to the latest version that can be installed given system constraints, so the update is more likely to succeed. In either version, the user doesn't get to pick among versions when updating.
How do i upgrade osCommerce v2.2 to v2.3.1? Is there a upgrade script available for that?
Do I have to upgrade it to v2.3.0 before upgrading to v2.3.1?
Download and unzip the latest version of osCommerce v2.3.1. Inside the folder you will find an upgrade_guide.pdf - open it. On the very first page, it tells you how to go about upgrading.
On page 2 you'll see a reddish shaded box and it says the following:
This upgrade guide only provides the minimum required changes in the form of security updates and bug fixes. These changes will not upgrade your store to a complete v2.3 version. Please continue to use v2.2 add-ons and do not install v2.3 optimized add-ons as the may not function with your installation. If you wish to upgrade to a full v2.3 version, perform only (SQL) Database Changes and use the database with a new v2.3 installation.