NOTE 1: you may post in forum about this FAQ article to give some feedback and provide corrections/suggestions
NOTE 2:please do not ask for support with "questions like":JUpgrade freezes will updating NNN part,
e.g. JUpgrade will give an error if extra columns exist in some tables and the effect will be to make the process freeze, you can find about the error that made JUpgrade fail/freeze by examining the HTTP responce via a tool like firebug
NOTE 3:if you need help to upgrade your site, ask a professional or ask us at email This email address is being protected from spambots. You need JavaScript enabled to view it. and we will give you a price quote
STEPs for using JUpgrade (modified version)
Download modified version: here
(official site of JUpgrade)
http://matware.com.ar/proyects/jupgrade.html
- Using JUpgrade will not damage your old site, but we strongly recommend that you backup your site first, e.g. use Akeeba Backup
- Download and install modified version jupgrade v2.5.x
- the modified version will upgrade the category tree properly, also including sections at top level
- Run JUPGRADE, (it requires the mootool upgrade system plugin to be enabled)
(before running you may select not to include some data, e.g. skip weblinks component, etc)
- If the JUPGRADE fails, correct the error,
then delete folder: siteroot/jupgrade/ and then retry (the new tables j25_* from failed step, will be deleted automatically)
- After upgrading finishes, open http://siteroot/jupgrade/administrator/ and immediately install FLEXIcontent
- after installing you get a warning message about 2 missing XML files, but ignore it,
... it is because the installation process tries to get version number of previous installed FC version
- Goto FLEXIcontent dashboard and click to complete any post installation tasks,
NOTE: all parameters except for component are transfered, but component settings are lost,
you will have to re-enter them by looking at the old installation, OR use the query provided in next step
- in phpmyadmin, (default DB prefix used by JUpgrade is j25_) execute:
- for J2.5 / J3.x
UPDATE PREFIX_menu SET link = replace(link, 'index.php?option=com_flexicontent&view=items', 'index.php?option=com_flexicontent&view=item')
the above is need because item view in J2.5 is called 'item' instead of 'items' (J1.5)
- for J2.5 / J3.x
UPDATE PREFIX_content SET `introtext` = replace(`introtext`, 'index.php?option=com_flexicontent&view=items', 'index.php?option=com_flexicontent&view=item');
UPDATE PREFIX_content SET `fulltext` = replace(`fulltext`, 'index.php?option=com_flexicontent&view=items', 'index.php?option=com_flexicontent&view=item');
the above will update links inside text description text of the content items
- for J2.5 / J3.x
UPDATE j25_menu SET component_id=(SELECT extension_id FROM j25_extensions WHERE element='com_flexicontent') WHERE link LIKE 'index.php?option=com_flexicontent%'
the above will update FLEXIcontent menu items to have correct component ID
- for J2.5 only
UPDATE j25_menu SET ordering=0
the above will make sure that you will not have problem re-ordering you menu items
e. for J2.5 / J3.x
UPDATE `j25_extensions` SET params=(SELECT params FROM `jos_components` WHERE `option`='com_flexicontent') WHERE `element`='com_flexicontent'
which will copy component parameters from old installation to the new,
then visit FLEXIcontent backend and click to edit and re-save FLEXIcontent component configuration
- Go to content types, and edit-save them once
- Now you need to UPDATE the XML FILES of ALL custom templates (built-in are already up-to-date)
So go to folder
siteroot/jupgrade/components/com_flexicontent/templates/
and follow these instructions to update them:
{jb_purple}Updating your FLEXIcontent J1.5 templates to work with FC v2.x for J2.5 / J3.x
{/jb_purple}NOTE 1:
(you may want to do a careful recursive text search and replace in your text editor, if you have many templates)
NOTE 2:
Clean cache every time that you change XML files of templates (if you have J2.5, if you have J3.x you don't need to clean cache)
NOTE 3:
After cleaning cache and visiting the templates TAB will show if you have an error if your XML files were not updated properly. If there is an error, then move 1 template file at a time inside the templates folder, clean cache and refresh the templates listing, to see if the template XML files are good
- The PHP files of your custom templates may have J2.5/J3.1 removed functions e.g. JPane is removed in J3.1
(you will have to edit the PHP files to replace the removed functions)