I am using Vue 2 with composition api at the moment with Primevue2. I want to do Vue3 upgrade to my application and I want to upgrade Primevue version to 3 from 2 along with Vue upgrade. I have been noticing there are different class names for responsiveness in the latest Primevue release. Is there any commands or tools that I can update those changes with Primevue upgrade? Appreciate if anyone could help on this
Thanks
Related
To my knowledge, the latest non-alpha version of the #ui5/cli and #sap/ux-ui5-tooling (as of 2nd March 2022 - version 2.14.6 and 1.5.0 respectively) are the ones to use.
However, I wanted to confirm as my organisation has multiple ui5 projects and so having a standardised version of the #ui5/cli and #sap/ux-ui5-tooling dependencies could prevent issues around bugs in tooling.
If the advice is just to use the latest non-alpha version, then I just need to update the dependencies regularly.
The versions you mentioned should be your choice to use in a productive environment.
The upcoming UI5 tooling 3.0 is not.
I don't think you will achieve the same version in every app because of the lifecycle.
The packages are fast paced and when u have a stable app deployed you will not update it every month I think.
I would not invest time to find the perfect tooling version.
If I upgrade the angular version of my project to the latest one, do I need to upgrade my ag-grid version also to the latest one to make it work? Or, my ag-grid will work without any change?
Generally, an old version will work without change.
I'm currently using version 20.2.0 with Angular 8 (the current ag-grid version is 23.1.0).
I'm not sure what will happen if you try to use an older version with Angular 9, using the Ivy Renderer. I expect that it will work ok, but I haven't tried it yet.
why the Core update shows me "No regular update available" and upgrade wizard shows me "No updates to perform!"?
I'd like to upgrade from 7.6.31 LTS to the latest 8.7.x LTS version.
The wizards for upgrading in the TYPO3 install tool always only performed upgrades on the same main-branch. So a change from version 7 to 8 or 8 to 9 was never considered and has to be done manually. One reason might be that also some extensions follow the same concept and it will be hard to keep the site running with automatic updates between branches.
Especially problematic would be an automatic upgrade from 8 to 9, because many things changed technically (t3_ckeditor instead of rte_htmlarea, Doctrine Dbal instead of the old TYPO3 database-layer).
So, currently there is just no option to upgrade from 7 to 8 and you've to accept to have to do that upgrade manually.
Nevertheless the upgrade-wizard is still supporting you with required database-updates and other actions to perform.
Some upgrades also require an update of PHP which would be impossible for the wizard.
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
we are going to upgrade our typo3-instance from version 6.1.5 to 7.6. Since we need to clone the instance and afterwards upgrade it in two steps (6.1.5 -> 6.2, 6.2 -> 7.6) we wonder if it was easier to setup a clean 7.6 instance and migrate the data (templates, sites, binaries etc.) afterwards.
There are multiple instruction pages on the web describing how to upgrade to 6.2 and to 7.6 but it seems to be a really tricky process.
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
What do you think of the approach?
Thanks,
Thomas
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
Most likely this process will not go without troubles.
Best advice I can give, is to upgrade to 6.2, do the upgrade wizards in the install tool. After that upgrade to 7.6 and do the upgrade wizards in the install tool again (those will be different ones).
Your content should now be fine.
You can keep incompatible extensions uninstalled during this process as it is merely targeting content migration. Don't bother with extension code while doing this. Just the core and your content is enough to provide a working content structure for 7 LTS. Migrate the extensions afterwards.
I prefer the upgrade way to do it, because the t3d export / import thing may work, but may cause some troubles too, especially if this is a bigger site.
If you update the extensions on your 6.2 site to current versions, fix the namespaces and deprecation log entries in your individual extensions, the 6.2. => 7.6 upgrade should be quite smooth. In my experience it is much more convenient than a 4.5 => 6.2 upgrade.