In one of our website we are using CKEditor version 4.5.4. After Penetration testing, upgrading the CKEditor version to the latest one is recommended.
Functionality point of view we don't want to change anything. So, to which version we should upgrade either to 4.20.0 or to version 5. The target is to remove vulnerabilities.
Related
We have a vue.js project in which we are using Vuetify 1.5.2. We want to upgrade to the latest version of Vuetify. Our first attempt to do this proved disastrous as it is an all-or-nothing move and as soon as we upgraded our version of Vuetify, everything across the site broke.
Now we are considering this again but we are looking at code splitting. What we are wondering is can code splitting be used to slowly migrate from Vuetify 1.5.2 to the latest version (2.3.19 right now)? Can we package our code in such a way that newer code is packaged the latest version of Vuetify but older code is packaged with the older version of Vuetify?
I'm afraid it will result in even more conflicts, and more time to ensure specific parts call the older version and some the newer. I'm afraid you will have to go the painful route of branching your project and slowly go through all the Vuetify issues.
Unless your front-end consists of multiple independent projects (each with their own package.json), then it could be done.
I just upgraded from SonarQube 6.1 to 6.7.7. For SonarJava, it automatically installed 4.15.0.12310 (it was 4.10.0.10260 before). In the Marketplace, when I hover over the available versions from 5.0-5.13, it says “Incompatible”. When I hover over 5.13.1+, it says “Requires system update”. What does it mean for it to be incompatible if it doesn’t require a system update?
I am seeing this with various other plugins as well, such as SonarPython, which had 1.8 automatically installed. I had to manually install 1.9.1 in order to get this bug fix (which is why I originally upgraded the server): https://community.sonarsource.com/t/python-s1481-code-smell-unused-local-variables-should-be-removed-false-positive-with-string-interpolation/8961
I could manually install newer versions of other plugins as well, but I don’t know if that’s safe.
I also can’t find an official plugin compatibility matrix, since this only shows 7.9+: https://docs.sonarqube.org/latest/instance-administration/plugin-version-matrix/
Incompatible means that the plugin does not work with the version of SonarQube you have installed.
An example of an incompatible plugin would be one where the plugin relied on an API that was removed in your current SonarQube version. You may be able to use that version of the plugin if you downgraded your SonarQube instance to a previous version.
Requires system update means you need to upgrade SonarQube in order to install the plugin.
For what it's worth, the states as described by the API documentation are:
Update status values are:
COMPATIBLE: plugin is compatible with current SonarQube instance.
INCOMPATIBLE: plugin is not compatible with current SonarQube instance.
REQUIRES_SYSTEM_UPGRADE: plugin requires SonarQube to be upgraded before being installed.
DEPS_REQUIRE_SYSTEM_UPGRADE: at least one plugin on which the plugin is dependent requires SonarQube to be upgraded.
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.
I don't know why joomla is not updating mootools with their updated version, joomla 1.5 still use mootools v 1.1, i tried to replace it with latest mootools version, but results are horrible, website stops working, everthing gone worst.
so please suggest me how to update mootools version into joomla without any problem.
Joomla 1.5.20 has plug-in for the Mootools 1.2.4 called "Mootools 1.2.4 Upgrade", but the plug-in is disabled by default.
If you are making a clean installation go "Admin->Tools->Plug-ins" find and enabled "Mootools 1.2.4 upgrade plugin".
If you are updating older Joomla system to 1.5.20, the plugin will be installed but it will not be visible because it will not have plug-in record in the database, therefore the plugin cannot be used. Here is a tutorial showing how to add this plugin when updating Joomla system from older version - http://www.boolcast.com/updates/mootools-124-upgrade-plugin-for-joomla-15.
Now that Mootools core 1.2.5 is out, i'd bet on it (hopefully) for J!1.6 RC.
And be aware that 1.5.20 mootools.js (in mtupdate plugin) contains More 1.2.4.2 (current version version is More 1.2.4.4).
Search the Joomla forums, there are several threads on updating Mootools.
In general, you can update the frontend pretty easily (assuming you don't want the built in Joomla functions or have components that rely on them). The backend is more problematic as it's built heavily around 1.1
Having said all of that, the latest versionof Joomla 1.5.20 has a plugin to allow you to update to 1.2. You could try updating?