get rid of messages such as; "Super Orders v4.0 install completed!" from the top?

[schoolboy]

... a sorry consequence of blindly re-loading all core files...

As I said, if you ADD something, then be sure you know how to un-pick it. To "panic" and overwrite everything en-masse is a recipe for bigger problems.

Unfortunately, as none of us has any idea of how your structure was set up and modified, there is little that we can suggest.

If you can retreive your database, then at least you will not have lost data.

The remedy may be doing a fresh install, making a COPY of the database, pointing the fresh install to that copied database and seeing how behaviour is affected.

[PetleyJ]

... a sorry consequence of blindly re-loading all core files...

As I said, if you ADD something, then be sure you know how to un-pick it. To "panic" and overwrite everything en-masse is a recipe for bigger problems.

Unfortunately, as none of us has any idea of how your structure was set up and modified, there is little that we can suggest.

If you can retreive your database, then at least you will not have lost data.

The remedy may be doing a fresh install, making a COPY of the database, pointing the fresh install to that copied database and seeing how behaviour is affected.

Thanks SB,

I have a backup of the database, it has been modded heavily, however I have a few ideas that I will use tonight to get it working again. I will remove all the files related to the last couple of days of adding plugins and go from that. Been working in zen for a couple of years so I have a rough idea.

Will let you know how I get on.

[lhungil]

How do I get rid of messages such as; "Super Orders v4.0 install completed!" from the top?

Usually this indicates a number of files added when installing the module have not yet been removed. At the minimum - there is probably a file in the "admin/includes/auto_loaders" and "admin/includes/init_includes". This also indicates the the user your webserver runs as does not have permission to delete the file under "/admin/includes/auto_loader" automatically for you.

To uninstall Super Orders essentially you:
0) Create a backup of the database and all files. This is just to be on the safe side.
1) Remove any new files you added during the installation ("Base Files" in the distribution).
2) Undo any changes you made when merging with core Zen Cart files ("Modified Core Files" in the distribution).
3) Run the provided SQL Uninstall file to remove the database changes (found in "SQL" in the distribution).

If you follow the above steps you should be able to successfully remove Super Orders.

If you have not installed any other plugins / modules which modify the same core Zen Cart files (step 2 of the removal) you can just overwrite those files with ones from the stock Zen Cart files for your version of Zen Cart. If you have installed any plugins / modules which modify the same core Zen Cart files... you will need to use a tool like WinMerge or BeyondCompare to undo the changes (or start from stock Zen Cart files and redo the installation of those plugins / modules).

Otherwise... the remedy (as schoolboy mentioned) may be doing a full backup of DB and files... then doing a fresh install... running the SO db uninstall... and seeing how things go...

[PetleyJ]

Usually this indicates a number of files added when installing the module have not yet been removed. At the minimum - there is probably a file in the "admin/includes/auto_loaders" and "admin/includes/init_includes". This also indicates the the user your webserver runs as does not have permission to delete the file under "/admin/includes/auto_loader" automatically for you.

To uninstall Super Orders essentially you:
0) Create a backup of the database and all files. This is just to be on the safe side.
1) Remove any new files you added during the installation ("Base Files" in the distribution).
2) Undo any changes you made when merging with core Zen Cart files ("Modified Core Files" in the distribution).
3) Run the provided SQL Uninstall file to remove the database changes (found in "SQL" in the distribution).

If you follow the above steps you should be able to successfully remove Super Orders.

If you have not installed any other plugins / modules which modify the same core Zen Cart files (step 2 of the removal) you can just overwrite those files with ones from the stock Zen Cart files for your version of Zen Cart. If you have installed any plugins / modules which modify the same core Zen Cart files... you will need to use a tool like WinMerge or BeyondCompare to undo the changes (or start from stock Zen Cart files and redo the installation of those plugins / modules).

Otherwise... the remedy (as schoolboy mentioned) may be doing a full backup of DB and files... then doing a fresh install... running the SO db uninstall... and seeing how things go...

Hi,

Followed your steps and overided with stock files.

Removed successfully.

Resolved the cart / user problem, I restored both my ZC database and directory from a couple of days ago when it was running fine.

I have made a test site for future and also will follow steps you mentioned in the future.

I'm glad I have automatic backups or I'd be lost without them.

Thanks to both of you guys.

James

[schoolboy]

Well... that's why backups are essential - so you've followed the main cardinal rule !

Best of luck with future plugin installs - and by doing them in a test enviro first, you can't mess up a live site.

One more tip...

Whenever a CORE file is affected, re-name the ORIGINAL to xxxxxxxxxxxx.TEMP

Here's what I do...

Let's say I modify tpl_main_page.php

I rename it to tpl_main_page-php.TEMP

(notice how I leave the "php" in the name, but hyphenate it from the rest).

PS (I do not use "TEMP" as my file extension, but something else consisting of four letters which I do not reveal in public forums.)

Anyway... if things go belly up, then I remove my edited version of the core file, and name the original back to tpl_main_page.php

[PetleyJ]

Well... that's why backups are essential - so you've followed the main cardinal rule !

Best of luck with future plugin installs - and by doing them in a test enviro first, you can't mess up a live site.

One more tip...

Whenever a CORE file is affected, re-name the ORIGINAL to xxxxxxxxxxxx.TEMP

Here's what I do...

Let's say I modify tpl_main_page.php

I rename it to tpl_main_page-php.TEMP

(notice how I leave the "php" in the name, but hyphenate it from the rest).

PS (I do not use "TEMP" as my file extension, but something else consisting of four letters which I do not reveal in public forums.)

Anyway... if things go belly up, then I remove my edited version of the core file, and name the original back to tpl_main_page.php

Thanks Schoolboy, Will use that tip in future. :)

James