If only it worked!
Jimmy Wu of Web Assist gave a lot of his time in finding a problem with Site Assist Pro (Ticket #109965). He needed to locate then delete a line of code in the web assist wizard JavaScript that appeared to be causing the crashes in Mac Snow Leopard. We eventually managed to build a basic site with Site Assist Pro, and although the close document line of code at around line 630ish was no longer active, all seemed OK.
So, I installed Web Assist's CSS Menu Writer V2 as this furthers the capabilities of Site Asist Pro. Big mistake. Here's the error that now appears whenever Site Assist Pro runs (even after reinstalling):
------------
While executing onLoad in wasap_wizard.htm, the following JavaScript error(s) occurred:
in file "wasup_wizard":
initializeUI is not defined
------------
OK, so Site Assist Pro just isn't working on the Mac, let's try this on the Windows XP SP3 PC. I spend another lengthy period defining a site only for Site Assist Pro to freeze again as I click the next button at the Header/Footer stage.
Enough! I have to say that over the years, and although they offer great promise, WebAssist extensions have far too many bugs. I've spent too much time hoping that the latest version will deliver a pain free solution - it hasn't. Heck, it took several stabs in the forum before it was even escalated to a ticket, and then I had to provide a great deal of information before the WebAssist team eventually twigged there was a very real problem that wasn't a simple error.
Why bother saying this here? Well, I didn't want to make a song and dance of it on the forum, so I tried adding feedback to the ticket, and guess what happened when I clicked the submit button? "Error, that page doesn't exist on our server... says it all...
