Publishing screw up - How do I get back the business space?

JonP

I'm still ascending the learning curve when I comes to publishing. I published what I'm working on by mistake and lost the business space (BS). I can't log into the configurator using that BS and if I login as another BS, the BS I'm looking for is not there. If I try to create a new BS under that name, I'm told it already exists. How do I get it back?

aware_support

You restore it from the database backup - that's why there are so many warnings before you publish.

BLOMASKY

I feel your pain Jon,

I decided early on, since all my work is stored in a database, When I installed Aware, I created a BS that I never use, its just for the registration info and logging on. All of my "real" BS are separate.

I know that does not help you now, but after you restore, you might want to leave that one Pristine, export and import your work into a "new" bs to use.

Bruce

JonP

Thanks Bruce for the advice going forward. Someone can benefit from it. Last night Mark took pity on me and walked me through some best practices.

Some things I learned:

The advice you gave about a separate BS for registration/login. Why doesn't AIM automatically create one for this purpose (or better yet, not tie registration/login to a BS)?
Never publish with your development machine.
It's actually OK to publish the latest version of the BS (I assumed that was where I screwed-up), but make sure the database is backed-up first (my bad) because AIM is unstable when it comes to this feature.
Check your version updates. Sometimes they don't work (at least a minor version update didn't).
Running test in order to clear your test data before publishing doesn't prevent AIM from corrupting the database.
It's best to import new BSVs into the production server by logging into the production business space as admin and importing from the Standard menu - very slick.

tford

Re: backups - I use Navicat to do automatic scheduled backups of AwareIM multiple time per day ... 24 x 7. You can also trigger it to run before a BSV is updated as well.

Re: Standard menu that Mark mentioned in #6 .... YES, that's definitely the best way to go!

6. It's best to import new BSVs into the production server by logging into the production business space as admin and importing from the Standard menu - very slick.

One control I wish was in place as a safety measure is a BSV name. Here's how it would work:
==> If you are logged into SampleBSV & trying to Import a new BSV via the Standard menu, AwareIM would not allow you to upload any BSV other than one with the same name. The name I name I am referring to is NOT the file name, but the name of the BSV.