I've been using Algolia Search for Magento 2.1 for 2 weeks.
Somehow I accidentally ran the composer command and updated Algolia to version 1.10.0.
Now I want to downgrade it back to version 1.8.5.
Could you please show me how to do that?
Related
My projects java version runs on 1.7.0_71. and my elastic search version is 1.4.3 . Now we want to upgrade the es to 2.3.5. Is it ok to simply upgrade the elastic search version from 1.4.3 to 2.3.5. or should i upgrade the java to 1.8 then migrate it to 5.1 .. because my ultimate target is to for elastic search 5.1 version.
It should be ok to upgrade from 1.4 to 2.3, but it will be trickier (impossible) to go straight from 1.4 to 5.1 or 1.4->2.3->5.x without reindexing.
Segments created two Lucene major versions back are not supported.
So, even if you updgrade to 2.3, there still might be old segments (created in 1.4) when you upgrade to 5.x. There is an upgrade indices API, but as the documentation says it will not be useful for a 1.x -> 5.x upgrade.
Regarding the Java version, yes, you need Java 1.8, at least update 73: https://www.elastic.co/guide/en/elasticsearch/reference/5.1/setup.html#jvm-version
I have a site built in Laravel 5.0 and would like to upgrade to Laravel 5.2
Do I have to first upgrade to 5.1 and then upgrade to 5.2 or is it possible to upgrade directly from 5.0 to 5.2
The only guides I can find at the moment don't seem to offer the option from 5.0 to 5.2 so I was wondering if there are too many changes to jump from 5.0 directly to 5.2.
Since the migrations between releases is a manual migration, you may follow the instruction for every single migration in chronological order and then run the composer update only once.
Nevertheless, I think the optimal approach is to migrate to the next version, verify everything works, and repeat until you get to the last release.
I am new in elasticsearch and I have by mistake installed 0.90.7 version in my server. Now I want to install shield for this I have to upgrade my elasticsearch version to 1.5 or above. So I need to Upgrade version without loosing existing data. Can anybody help me how to upgrade version to 1.6.1?
You can upgrade your Elasticsearch version from 0.90.x to 1.x in the following way
Cluster restart upgrade process
Before upgrading Elasticsearch, it is a good idea to consult the breaking changes docs.
As per Elasticsearch Documentation before performing an upgrade, it’s a good idea to back up the data on your system.
I have an app built using the legacy 2.x (2.1.4 to be exact) version of CodeIgniter. Now I want to upgrade. How would I do that?
Or is it even possible and easy?
Upgrade first from 2.1.4 to 2.2.0 by replacing all files in the "system" folder and then use the tutorial on the official codeigniter site.
I haven't tried this but it seems logical.
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?