Database crash notice

Hi, I got the following erro msg when I try to open my ZenCart site.

145 Table './herbal11_zc1/zen_whos_online' is marked as crashed and should be repaired
in:
[delete from zen_whos_online where time_last_click < '1319649963']

I know how to fix this problem. My question is, is it possible to turn off this detailed msg, just show customer "Sorry, we got some technical problems, will be back soon", and send an email to the store owner?

Thanks
Davis

Yes, upgrade to v1.5.0 and a friendly message will be displayed instead of the ugly technical message.

DrByte:

Yes, upgrade to v1.5.0 and a friendly message will be displayed instead of the ugly technical message.

Upgarding to v1.5.0 is the only solution? I have made a lot of customziations, upgrading will take a lot of time.

y051313:

Upgarding to v1.5.0 is the only solution? I have made a lot of customziations, upgrading will take a lot of time.

Don't confuse 'customisations = changes to the core code' with 'customisations = using a template other than the Classic Green' or 'customisations = lots of 3rd party addons being used'

If your customisations revolve around using a different template only, the upgrade is very simple and will only take a few minutes.

If your customisations revolve around lots of 3rd party addons being used, then as long as the addons are V1.5 compatible it'll take a little longer because you'll need to upgrade those too.

It is only if your customisations revolve around changes to the core code that it could take a lot of time to merge all the changes into the updated code, but most people are not in this situation (and those that are are usually skilled enough that they can do this with very little effort.

Cheers
Rod

RodG:

It is only if your customisations revolve around changes to the core code that it could take a lot of time to merge all the changes into the updated code, but most people are not in this situation (and those that are are usually skilled enough that they can do this with very little effort.

Cheers
Rod

I'm afraid that's the situation I'm facing, we have added some fileds in the databases, and also changed core code...