I want to Upgrade from Kentico 9 to Kentico 11 ans skipping upgrade K9 to K10. Is it possible?
No, you cannot (and should not) do this.
Please note: The upgrade procedures are not cumulative and you may need to use several upgrade procedures if you're using an old version of Kentico.
https://devnet.kentico.com/download/upgrades
While it may seem like this will save you time, the upgrade scripts are designed only to work between major versions (7 > 8, 8 > 9, 9 > 10 etc.). If you try to run the v11 script on a v9 database, you can expect failures in the upgrade process.
Running through each upgrade in order will reduce the risk here and give you the confidence that your site has migrated correctly.
Read the release notes before you start and make note of the breaking changes (there are quite a few)
Kentico 10 Release Notes
Kentico 11 Release Notes
It is strongly recommended not to do that. You must always upgrade one version (major version) in ahead.
Best regards,
Dragoljub
Related
Understand from: https://www.enterprisedb.com/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/11/EDB_Postgres_Advanced_Server_Guide.1.80.html
that PL/Java is deprecated in Advanced Server 11 and will be unavailable in server versions 12 or later.
May I know:
What is the recommended replacement for PL/Java in PostgreSQL12?
For my existing UDF in PostgreSQL 9.6.x, etc., which is using the PL/Java, how could I move over to PostgreSQL 12?
Thanks in advance.
Edit: Come to think of it, there was an issue reported back in September 2020 (PL/Java issue 260) about failing to build against EDB PostgreSQL 11. It turned out that EDB had made an API-breaking change to upstream PostgreSQL, by changing an API function and leaving behind only a macro with the old name, instead of a (possibly inline-qualified) wrapper that could be addressed.
That ended up requiring an EDB-specific workaround to be shipped in PL/Java, and that fix has been included since PL/Java 1.6.0 and since PL/Java 1.5.6, which both were released in October 2020.
I am sorry that I did not see this question earlier.
I maintain PL/Java, and I have had no notice from EDB concerning why they have deprecated it. Perhaps they are simply no longer providing a binary package prebuilt by them.
I know of PL/Java in use with PostgreSQL 12 and 13. I believe that to build it from source for use with EDB, it should be built with Visual Studio, following these instructions.
If you are able to learn anything more from EDB about the deprecation, or if you have any difficulty building from source, please feel free to open an issue. Thanks!
I'm currently preparing to update my TYPO3 8.7 site to a 10.0, this update is set for April since that's when the LTS release will be. However, I was wondering if it's best practice to update to 9.5 first or to skip said version and go straight to 10.0.
Of course, backups will be made before doing any of this work and my server can handle the 10.0 version since we have an empty one running at the moment.
You should upgrade to 9.5 first to execute all the core & extension updaters (database)
see documentation
In my experience, you can just do the extension updaters and then go to the next version but you will have to fix your site extension in version 10. See the changelog for all breaking changes
To migrate from Typo3 7.6. to 9, do I have to make an intermediate step via Typo3 8?
I have a Linux Server and the current PHP is 7.0. PHP would be updated as well.
Would like to get to the current version of Typo3 but not sure if a direct jump would cause more problems. (This is aided by an agency, but would like to get second opinion whether intermediate step makes sense)
You should always do an upgrade step by step.
It's also good to have this step for all the DB migrations and some manual stuff like raising PHP version.
Depends on the extensions and the level of your knowledge. I would also prefer the step from 7.6 to 9/10 via 8, but if the Extension is still from pi Age or early extras, i would prefer to rebuilt it from the scratch, also because of changing db routines and other depreciation stuff.
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.
I am seeing 2 versions (9.0.1 vs 8.2.1) of wildfly which were released on the same day. What is the difference between two versions and why there are 2 versions exist in parallel? I couldn't find it over the internet.
Wildfly ships on a very fast development cycle. Each major release 8.x, 9.x, 10.x contains major changes from the previous version. All current major work is being done on the 10.x beta versions.
The minor versions are for bugfixes related to that particular release. Since there are now people in production with both 8.x and 9.x, any critical bugs or security patches go into one of these releases. It is very possible a security issue could exist and be fixed in both 8.x.1 and 9.x.1.
JBoss EAP, which is based on WildFly, deliberately has a slower release schedule. For each major version they release they offer paid support for 4 years, so they change major versions much slower.
There is a good slide of the lifecycle of WildFly/JBoss on page 9 of this slide-deck from the RedHat Summit in June:
http://videos.cdn.redhat.com/summit2015/presentations/12186_red-hat-jboss-enterprise-application-platform-7-roadmap-new-features.pdf
Here is the official announcement for the pair of releases: -
http://wildfly.org/news/2015/07/23/WildFly-901-and-821/