CMS Builder in own (sub) directory
Please could you provide step by step directions how to install CMSBuilder into its own directory, and still be able to do all that it is supposed to do.
I have installed to a directory (by defining that folder as site root in new DW definition) - and copied the connection folder to main site root connections folder, so have CMS - but still no DW interaction.
As this *has* to be in a sub-directory - because of duplication of file & folder names, and a jumble of folders in my site root etc - please could you provide a thorough guide to getting all of the functionality when working with CMS Builder from DW site root while CMSBuilder is in its own directory,
P.S: I have bought this for the unlimited sites benefits, and am happy to enter serial number and have it logged with your servers when I first install the extension, but why does it have to be re-submitted to your servers each time I use it on a site? (It's nobody's business but mine what sites I'm working on, or how often I use the extension!). How to disable the second unnecessary (and somewhat obtrusive) 'per-site' activation?