Upgrade Guide
Please follow these instructions carefully
If you're upgrading from JEvents 1.4 beta1 or later please see the note at the bottom of this page.
REMEMBER it is always a good idea to backup your database before this type of upgrade.
Upgrading the component
There are 2 approaches.
1. (Preferred) You can uninstall the existing component and install the new version YOU MUST EDIT YOUR EXISTING events.xml FILE BEFORE YOU DO THIS
1.1 edit events.xml (in administrator/components/com_events) of your existing installation
1.2 remove the following from this file BEFORE you uninstall the existing component:
<uninstall>
<queries>
<query>DELETE FROM '#__events'</query>
<query>DROP TABLE '#__events'</query>
<query>DELETE FROM '#__events_categories'</query>
<query>DROP TABLE '#__events_categories'</query>
<query>DELETE FROM '#__categories' WHERE 'section' LIKE 'com_events'</query>
</queries>
</uninstall>
1.3 uninstall the existing component
1.4 install the new version of the component
2. (Alternative) Upload the patch file to the root of your Joomla installation and extract the archive from there using a tool like JoomlaXplorer?. Or extract the archive in a temporary directory on your computer and FTP the files (preserving the directory structure!) to the server. This approach will not update your admin menu items so you will not have the new 'archive' menu option but you will still have access to most of the functionality.
You can safely uninstall the modules and mambots before installing the new versions
Upgrading from earlier version of JEvents 1.4
If you are upgrading from JEvents 1.4 there are no new changes to menu items so the easiest upgrade path it to use the patch file to upgrade your JEvents component (see 2 above). You will still need to uninstall the modules and mambots before installing the new versions - make a note of your config settings. Alternatively you can unzip the module/mambot files and overwrite the appropriate files. Note that the patch file does not include the events_css.css style sheet or a config file so your current settings should be preserved. Having said this it is always a good idea to do a back up before any upgrades.
If you choose to do a full install and have modified the CSS files supplied with Release Candidate you should make backup copies since both the install file will replace these.
|
