Hi,
Not sure if it is a bug, or I am missing something, but I am getting a bit frustrated with the new build window and build changes in V11. It is working inconsistently for me when trying to build/publish a Webhelp output.
First I do miss the popup window that used to display when you published an output. It would allow you to verify your destinations and destination settings etc. Now you don't get this chance, and have to rely on the settings all being correct prior to publishing. I can see why it was removed though, to streamline processes and allow for more automated/scripted processes etc.
Anyway, my main issue or query is how the Build / Publish process is supposed to work now.
I do a Webhelp build – all good. Then if I select the Publish button, Flare usually rebuilds the whole thing again! Sometimes it does what I expect and just publishes the output.
As the build process takes an hour +, this is getting time consuming and frustrating.
If you have any tips on this, or what the process should be etc, please let me know!
Thanks,
New Build window issue/query in V11
-
wclass
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: New Build window issue/query in V11
There has been a recent release, v11.1, that has fixed the rebuild before publish bug, so check you have the latest version.
However, I don't think it has been fixed properly.
We publish to several destinations - a test site and a production site.
We build and publish to test to check it first. If OK, we just want to publish to production but we have to go into the target and change the destination settings (I really want that pop-up back). This change triggers a dialog saying something has changed and it is not up to date (but it really is). We then publish anyway to avoid another long build, but ignoring this warning could get us in to strife.
The change might have been made to automate things a bit more but it has really broken some existing use cases. Flare needs to rethink the publishing dialog.
However, I don't think it has been fixed properly.
We publish to several destinations - a test site and a production site.
We build and publish to test to check it first. If OK, we just want to publish to production but we have to go into the target and change the destination settings (I really want that pop-up back). This change triggers a dialog saying something has changed and it is not up to date (but it really is). We then publish anyway to avoid another long build, but ignoring this warning could get us in to strife.
The change might have been made to automate things a bit more but it has really broken some existing use cases. Flare needs to rethink the publishing dialog.
Margaret Hassall - Melbourne