Upgrade Issue

jcvieira

Hi guys,

Im currently trying to update my system from version 1.6.3 to the latest by copy the new files into the site dir...
But when i try to login on the update.php script it redirects to the same page...

Any ideias?

ajb

yes - session issues. I see two possibilities:
1. Wrong EPESI_URL in config - may cause that session cookie will be set for the wrong domain, so your browser won't pass proper cookie.
2. Session storage - your session is not stored properly and your browser has a proper cookie, but server doesn't store session properly.

Try to update with the update.php script. Grab latest release, copy only update.php file to your site directory as up.php file (do not replace existing file: update.php). Open browser to the new up.php file and try to do the update.

Best regards,
adam

jcvieira

Thank you ajb.

This has pointed me in the right direction.

jcvieira

HI again,

Ok so now after im up and running on version 1.8.1-20161121 when i click on Companies the call process.php fails with the following output:

<span style="display:none;" class="Base_Help__screen_name" value="browse_company"></span>Invalid request
: Array
(
[mode] => company
)

Any clues?
Thank you again ?

ajb

Well, try to cleanup your installation as I've described here: http://forum.epesibim.com/d/4800-add-meeting-stuck
Then clean cache & rebuild theme.

Best regards,
Adam

jcvieira

ajb Thank you this fixed the issue... ?

jcvieira

ajb Hi again... XD Just a quick question, when i do the procedure above my custom module gets uninstalled, so i went to the module admin and i reinstalled it, told me that there was an entry on the database with the same key, went on the modules table and delete that entry, then it allowed me to install it...
However it cleared all the record browser records associated with that module, so all the data was erased from the table, how can i keep my data with the above procedure?

Is there any easier way than importing all the module tables?

Thank you

jcvieira

jcvieira Updated with the latest version epesi-1.8.1-20161121 and the problem does not occur...
Thanks guys ?

jasiek

jcvieira When you uninstall the module it should remove all tables that where created during installation. Of course all data will be erased.
It looks like your module uninstall is not complete - do you remove tables created during module's installation?
If you don't then nothing is really uninstalled other then entry in the module's table. Code and tables are still there. When you reinstalled the module it already had first entry which was leftover from the old install - and your duplicate key error.

Try to uninstall process and see if tables are dropped. Do it of course on development server.

If you want to preserve data you should write a patch. More about it here:
http://www.epesi.org/Patches

Alternatively you could:

Make a backup of tables that will be uninstalled/reinstalled
Uninstall module
Reinstall module - you will have brand new tables with the latest table schema
Delete all records if any in newly created tables (common recordset name)
Import data from the first step.

But you can not expect users to do this complex procedure every time there is an upgrade.
This is why you write a patch which just alters data structure as needed by new module's features.

ajb

Probably your module has been "disabled" not uninstalled. It's been fixed in 1.8.1 that all modules disabled are trying to be reenabled during update and just after it.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge