Not sure what's going on yet but I will say you can't expect for publish to handle an external script.
I'm not sure what you mean by publish handling an external script but to try and clarify what I mean....
OK I think I understand better. Can you give me steps to reproduce or a simple project that shows the issue? I'm thinking this is a bug
No worries. Here are the exact steps to reproduce:-
1) Create a new Architect 3 project
2) Drag a JS Resource from the Toolbox over to the Resources in the Project Inspector
3) I populate the url config variable with js/routines.js
4) I set my publish path to the site root arc3.
5) I save the project and publish.
At this point the js/routines.js will be overwritten with an empty routines.js
My workaround is to cut and paste the code from routines.js into the code window before saving, that way it's not overwritten with blank content.
Thanks for looking at this. That sort of makes sense except its a shame that I cannot work relative to the publish directory rather than have to specify a full URL. That necessitates changing those references when I want to publish to another site URL :-(
Also, given that I specify the source of the ExtJS library relative to the site route would it not make sense to keep it consistent?
Yeah I see what you mean. The library path does not have the need to be included in the canvas as we know how to include it regardless of what you set as library base path. Js and css resources however must be included either locally (from w/ in the project) or externally http://
We agree this is not ideal and we should look into making this better.