Upgrading ezfind 1 to 2

Next topic

Author	Message
Andreas Kaiser	Saturday 21 February 2009 3:28:59 am Hello, I have a site using ezfind 1(Solr as service on Debian 4 - 32bits) and was thinking of upgrading to version 2. In ezfind2 I've found that reindexing is necessary when upgrading from 2.0 alpha1 to 2.0 beta, but no documentation about upgrading from 1.0 to 2.0. Should I: 1. Backup 2. Stop Solr 2. Upload new ezfind2 extension 3 Start Solr Any comments or upgrade documentation? Thanks! eZ Partner in Madrid (Spain) Web: http://www.atela.net/
Andreas Kaiser	Monday 02 March 2009 4:45:15 am Confirmed it was very easy and no problem with upgrade: 1. Backup 2. Uploaded ezfind2 extension 3. Configured ezfind2 extension 4. Stopped Solr (had it as service in Debian) 5. Copied ezfind2 service script to /etc/init.d 6. Started Solr (service) 7. Activated new extension (deactivated old extension) 8. Regenerated autoload and removed cache 9. Regenerated solr index 10. All working :) eZ Partner in Madrid (Spain) Web: http://www.atela.net/
Nicolas Pastorino	Tuesday 03 March 2009 12:37:05 am Hola Andreas, Sorry for the late answer. Good to see everything went smoothly. I would gladly have added to your migration todo-list to port the potential changes made to schema.xml and solrconfig.xml, but apparently you did not have to. This surely means you had left them in their standard state. Now that you have put eZ Find 2.0 stable on production, do you have any feedback on that release ? Best Regards, -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Andreas Kaiser	Thursday 05 March 2009 2:37:48 am Hi Nicolas, About changes in schema.xml and solrconfig.xml I will check it, but the changes should be upgraded in this case, because ez publish is using the new extension and all indexes were regenerated with ezfind2 (like in the case of a fresh install). But perhaps I'm missing something... (Anyway we changed index location two times, first to the directory under extension directory, and last to the default directory at /srv/sorl) About feedback of ezfind I've posted it in this post: http://ez.no/developer/forum/extensions/ez_find/use_ezfind_as_regular_fetch We have OptimizeOnCommit enabled and good performance (the site is even hosted on a XEN VPS with 2GB). We have made test creating and deleting objects and there is no personal perception of being slower. I was told by some partners they had problems with OptimizeOnCommit enabled (because when a new object was created it took a lot of time...) About performance, we need to update search templates of the site to use the new fetch functions of ezfind2... I'm sure this will improve performance and user interaction... eZ Partner in Madrid (Spain) Web: http://www.atela.net/