After Hard Disk crash and restore, problems Publishing to existing web server.

[Fulltimer]

I have an A5 web app running on a remote server (hosted by ZebraHost) and generally it has been running fine for over a year. I suddenly had a hard disk crash tried to restore my files as best as I could.

I needed to make a change to one of my components and then tried to publish that SINGULAR component and I get the preemptive message that several other files will need to be published also. In panic mode I stopped the procedure:

The additional files were:

a5_application.a5i
Doctor_lookup.a5wcmp
Guid.SecuritySettings
Project.SecuritySettings

The "Doctor_lookup.a5wcmp" is MY file that I recently edited. During publish I made sure that I didn't want "other files" to publish along with this one. I carefully unchecked all the options.

Somehow, A5 sensed that something was different and aggressively wanted to update or publish these other files. I always aborted the continue to publish process ( out of fear ). I do not use the A5 security model in my apps ( I write my own ). I don't know why A5 selected the specific files listed above under these conditions.

Questions:

1. Are you familiar with a similar situation and have a possible solution/reason?

2. I am afraid to use direct FTP (with Filezilla) because I may be wrongly stepping on a protected procedure?

3. Can someone use direct FTP to alter a singular file on the server without harming the WHOLE system?

4. Is the publishing aspect of A5 too complex to troubleshoot if something goes wrong?

Please help if you can provide any useful information.

Thanks.

[Steve Workings]

Re: After Hard Disk crash and restore, problems Publishing to existing web server.

Tom - You have a minor issue, I think, not a major one here. I've never fully investigated the publishing process, but from what I understand, Alpha keeps a history of what's been published, or changed since last published. In this case your list may not be 100% accurate. That's OK.

So yes, it's perfectly fine to use FileZilla to publish just the single component file and nothing else.

In fact, I have two sites where I use FileZilla to publish, and even under "normal" circumstances, Alpha sometimes presents me with files that I haven't changed and don't want to load. So, I just edit the component, let the publish process push files to FileZilla, then I just pick the one component file I want to update. Works just fine.

[Fulltimer]

Re: After Hard Disk crash and restore, problems Publishing to existing web server.

In fact, I have two sites where I use FileZilla to publish, and even under "normal" circumstances, Alpha sometimes presents me with files that I haven't changed and don't want to load. So, I just edit the component, let the publish process push files to FileZilla, then I just pick the one component file I want to update. Works just fine.

Steve,

Thank you for your response. It is encouraging information. I would however like to "drill down" a little further because these situation is critical.

You said you "let the publish process push files to FileZilla". I'm not quite sure what that means. I've never used FileZilla with A5 but I have used FileZilla in general.

-- What does "push files" mean in this scenario.

-- Also one of my greatest fears is that A5 V11 will try to rebuild or re-invent itself (on the server) if it senses that a singular file is out of sync (because of a third party upload of a component).

-- If I wanted to protect myself from unexpected (negative) results, what files (<dirs> and other settings locations) can I backup to get me absolutely back to "SQUARE ONE"? I don't know if A5 on the remote server stores stuff all over the place or even in the registry etc. I need to be able to return an errant update back to good working order without a single thing being pushed out of place. Bottom line, what's my most aggressive backup scenario (hopefully keeping all files on the server)?

Thanks,

Tom

[Steve Workings]

Re: After Hard Disk crash and restore, problems Publishing to existing web server.

I have an idea you're worrying about this too much, but I'm hardly one to complain about that....

Do this:

1. Make a backup of your folder on the web server. Then you always have it.

2. Set up a publishing profile to publish to that server by publishing with FTP. I notice that my Profile radio button is actually set to "Prompt at Publish Time" but you'll find what you need.

3. Get Filezilla set up to connect to your webroot on the server.

4. Go ahead and publish your component by using the Publish via FTP. Alpha will present you with a source folder to paste into the FileZilla source. Do that, see the list of files you have. Just pick the one(s) you want to publish and go ahead. You have plenty of stopping points along the way if you want to stop and think about what you're doing. It's a bunch of little steps -- nothing big and drastic is going to just happen to you all at once. Filezilla even will warn/prompt you about overwriting -- lots of safety points in here.

[Fulltimer]

Re: After Hard Disk crash and restore, problems Publishing to existing web server.

Steve,

After years of using A5, I never needed to use a third party FTP program in order to publish. With your help I was able to take the extra steps to perform this important procedural activity.

Thanks,

Tom W.