[claudiobosticco]

Hello, any news about this issue (posts #27/28)?

[claudiobosticco]

Hello, I need to apologize. I realized that the issue is due to my oversight. I’ve now added a WARN in the Maven build to remind myself about it.

Basically, the problem is related to what I mentioned in posts #4 and #5, which is that the template folder is missing in the skin folders present in the runtime, and therefore my Maven build cannot copy it. So, I need to remember to update it manually. The error was caused by some variable missing in my (old) _base.scss file.

Would it be possible to add an artifact that allows obtaining those folders through Maven?

ok, I see in the skinEditor.jsp that the actionURL is modified to that path if the user is authenticated.
I've actually modified skinEditor.jsp to work with my local authentication. Am I actually supposed to do that?

If I comment out the line where the actionURL is modified, the skinEditor doesn't find any skin because it's looking for the template folder inside the skins folders, which is absent in my deployment. On the other hand, also the skinEditorOperations folder is absent.

So I need to ask: is the skin editor actually ready to deploy in our own project? Am I missing some steps?

I must specify that I'm using maven. Maybe am I missing some maven dependency to have the "template" folder for the skins?