worst case: damaged CRM installation (5.5.4 CE)

[kazuoF]

We have been using the same Sugar CRM installation for two years. Due to various requests for customization, we have manually changed the PHP code a few times - every time attempting to follow the advice of experts in this forum.

Several days after the most recent series of changes, a problem with the accounts module (http://www.sugarcrm.com/forums/forum...er=desc&page=2) surfaced which I belief probably resulted from the mentioned modifications. Another obviously unexplainable problem with the module loader (http://www.sugarcrm.com/forums/showthread.php?t=73553) may have the same origin.

While we naturally ran backups before every code modification, it took us several days to notice the described problems. Since our employees have created and changed many entries since then, using the last backup before the code changes is not an option. After all, a lot of data would get lost.

So what options do we have?

------

PHP 5.2.4
Debian Linux Server 8.0.4
MySQL 5

[kuske]

You need professional support.

Ther should be someone who is able to compare your 554 code with the native 554 code and to decide which changes are ok and which not.

Then you need a Backup of the Database and a complete Application Backup which you should send to your professional service.

Perhaps he/she can repair youR application...

[eggsurplus]

If you took backups of the app just restore the app (leave the database alone). You should be ok then.

[kazuoF]

Hello Kuske, hello eggsurplus,
thank you so much for your help! :-)

What exactly do you mean by "app(lication)"? The complete Sugar CRM excluding the database?

@ Kuske: We will definitely do that as a last resort.

@ eggsurplus: We will try that.

[kuske]

Yes he means...

But be carefully, make a backup of your current application before you start any try!

In the application tree (/cache/upload/...) you find the documents and notes which had been uploaded.
So a fallback to e backup can loose these documents and notes..

[kazuoF]

Ok, thank you for the info!

Would it be possible to export all module data, create a new, fresh Sugar CRM installation and import the previously exported data?

[eggsurplus]

I'd advise just pointing a new or restored SugarCRM application (directory) to just point to your existing database. Less possibilities for failure. Your issues are with the application and not the database. The data should be just fine.

[kazuoF]

Thank you very much for your reply eggsurplus!

Would this approach also work if we installed a 6.2.1 CE and pointed to the data from our dysfunctional 5.5.4 installation?

Alternatively, would it work to export the 5.5.4 CE data and import it into the 6.2.1 CE installation?

[eggsurplus]

I'd suggest installing a new 5.5.4 install, point it to your database, then upgrade to 6.2.1 from there. The downside is you'll lose any layout customizations but your custom fields will remain in the database.

[kazuoF]

We installed a fresh 5.5.4, imported all the data from our old 5.5.4 and upgraded to 6.2.1.

With all our customisations we have made and all the problems we have encountered, it was a lot of work. Altogether, we spent two entire days on it.

However, the system seems to run smooth again.