We have two Dolibarr in operation in two different domains. One of them has a version 6.0 and another with a clean installation 12.0.
Performing the installation I was able to bring all the content to version 12 from an export-import of the database.
The point is that we are still working with version 6.0 and I want to migrate the Agenda and Third Party events that are taking place day after day to fill in and nurture the CRM. Logically, if I import all the content from CRM 6 to 12, the Dolibarr installation forces me to reinstall and reconfigure everything.
https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/f/f82804018c7ccd1e3ef5c18a4c42d418953e19e3.png
But I don’t see that it can be Imported. No way.
Does anyone know any method that does not involve a mysqldump from the database?
Thank you very much.
If you want go from v6 to v12, with no loss of data, you must install manually v7 over v6, v8 over v7, and so on till v12 over v11.
Then start working production in v12, and you will have all data up to date.
Regards
Eduardo.
Related
We have an application we inherited thats on version 500+, we are not sure why its such a high version, but so be it. We have been using Flyway for a few years on it now, and have multiple releases. Sample would be it started as 500.10.4, and we are now on 500.10.20, so 16 releases containing various flyway scripts on a lot of them, but not all.
Anyway, its been determined that for simplification we are to re-version the application to 6.0.0 in the next release. Is there an easy way to let flyway know of this change, so that if we stand up another instance when it runs through the scripts it would run the 500's first, then go back to the 6's?
Currently our flyway script files are named as such:
V500.10.20_2022.05.12.0000.1__xxxx.sql and so on. So in theory our next would be
V6.0.0_2022.05.13.0000.1__xxxx.sql
I know that flyway would see version 6 as lower than 500 and ignore it. We currently have flyway out of order set to false. Is there any other options to solve this other then to set out-of-order processing to true?
In our situation we do not have any flyway scripts pre version 500. So what we are going to attempt to do is have a manual script run that will update all the data in our xxx_db_version table to be version 5.00.xxxx instead of 500.xxxx. This way when we move to 6.0, all of the scripts would be seen as next in the sequence appropriately. While the versions in this table will then not match previous actual versions of the application this table is not used for the purposes of the actual displayed version of the system or anything, and once we move to version 6, the 500 vs 5 won't really matter. and the order/sequence will still be maintained.
If this does not work, I will post a follow up.
I just encountered the following situtation:
The test-server is currently running Flyway, with version 1 (V1). The test-server is automatically updated (including Flyway scripts) whenever anything is pushed on the develop branch.
A developer decides to start working on a new feature on branch feature/123. This developer creates a database script (Flyway compatible) called V2__cool_feature.sql. In the meantime, another developer also starts working on a feature branch called feature/456. This developer is also in need of an update script, and names it V3__another_cool_feature.sql, because the developer knows that V2 is already used on another branch. This feature/456 branch is finished and is merged, and so the current scripts on the develop branch are V1 & V3. This works well and the V3 script is executed, leaving Flyway its schema_version on version 3.
The other feature branch feature/123 is also merged, which means that the develop branch contains the scripts V1, V2 & V3.
Now this is were I'm having trouble with Flyway:
The build, including Flyway, is executed and it leaves the following message:
[INFO] Database: jdbc:mysql://example.com:3306/my_schema (MySQL 5.5)
[INFO] Successfully validated 2 migrations (execution time 00:00.019s)
[INFO] Current version of schema `my_schema`: 3
[INFO] Schema `my_schema` is up to date. No migration necessary.
What I want to happen is that the V2 script is executed, and I'm not sure how to do so.
I hope I explained my problem well, if not, please leave a comment.
Ugh, I'm not a smart guy. Putting a bit more effort into my Googling skills lands me upon the Flyway documentation, describing exactly my problem:
Option:
outOfOrder
Required:
NO
Default:
false
Description:
Allows migrations to be run "out of order".
If you already have versions 1 and 3 applied, and now a version 2 is found, it will be applied too instead of being ignored. (Even the same versioning as in my question is used >.< )
We are running Microsoft Dynamics AX 2012 R3 CU8.
Our customer wants to start using the rolecenter, but we found problems around importing Web URI into the AOT. There is a hofix for this (KB2894068), but it is for R2. The Microsoft LCS titles it: 'Error message is displayed when importing web URL page in AOT ”The parameter PageUrl is missing or invalid”'
I was wondering if there are 'Best Practices' on how to install an R2 hotfix in R3...
If it is code only, meaning it isn't a kernel hotfix, then you only need to be concerned about merging the code into your environment. You don't want to overwrite R3 code if it isn't necessary for your fix.
There should be an impact analysis tool or a way to use the compare tool to see what code will change. Or, sometimes LCS will show you what the code changes are before you download the hotfix.
I had an environment working with no problems, with Geonetwork harvesting metadata from ArcSDE 9.3. It was done trhu the following libraries, copied from the ArcSDE installation to the Geonerwork lib dir:
jsde_sdk.jar
jpe_sdk.jar
concurrent.jar
icu4_3_2.jar
After upgrading to ArcSDE10, the harvesting stopped working.
It is certainly because I'm using *.jars for version 9.3, while having a v10 ArcSDE, but the new installation doesn't have those jars.
Does anyone knows where to get them?
I realize this is an old question but it still comes up quite a bit. If you have current maintenance with Esri you can request the physical media from your account manager. They are no longer available for download on either the Customer Care Portal or MyEsri.
We recently upgraded (very successfully) to Tridion 2011 SP1. I want to install Content Porter 2009 SP2 and it requires the Hotfix Rollup 1 to be applied.
The Hotfix Rollup 1 is divided into 3 parts:
DB Script
Content Manager
Content Delivery
Is it possible to install the DB Script and Content Manager Hotfix but not the Content Delivery? I ask because our rollout process for Content Delivery files is much more involved than for the Content Manager (and will therefore take more time).
The delivery side of HR1 provides around 10 fixes of which none look related to and changes in the way publishing is done. So, it would follow that you could update the CM without (yet) updating the CD.
However, to remain fully supported you should ensure that the gap in updates to the CM and CD is minimal and must be completed (often, this gets forgotten about). Issues that arise might not be supported unless support is in (advance) agreement with your upgrade process.
I would also advise you to do this first on the test or development environment to ensure that publishing and render on the CD side are working when CM is HR1 and CD is not.