Save as...

Hi there,

I enter sculptor over the preset manager. I choose my layout and hit edit.
When I made some changes and click finish, it directly saves the changes over my coosen layout. The box, where I will be asked pops up and dissapears directly.
I got no chance to save my changed layout with an other name :-(

Any suggestions?
Denis

Does this happen with every sculptor preset that you edit?

Were you able to save changes to the layouts previously?

Did you make any changes to the Configuration/Commands/wacs_savedesign.js file or the Configuration/Commands/wacs_savedesign.htm file? The Configuration folder is the one referred to in the common installation issues file:
common_installation_issues.pdf

Can you send me these two files so I can take a look at them?

Hey Jimmy,

I will try it again, yeserday it works. I think it depends on, from where I start to edit the layout. I will let you know.

Denis

The error comes agin, but only after it worked 5-10 times :-(

I open the preset manager, select my layout, hit edit. make changes, click finish. then the saveAS window pops up and cloeses directly. the changes an saved, but I am not able to change the name :-(

When I make changes to TYPE the popup window lets me choose an other name ??? very strange.

Where can I send you the files?

Denis

It looks like I am able to reproduce this issue when I am editing the preset using the preset manager. If I go to Insert->WebAssist->CSS Sculptor and make the changes using that interface, I can save the preset with another name. It will generate a page when you save the preset, but it is a workaround that would allow you to save the preset you generated under a different name.

Another workaround would be to duplicate the design before editing it, that way you'd have the original and the duplicated preset.

I will log a bug for this issue. Please use the workarounds to get around this issue.

Hi Jimmy,

thanks for your answer.

I really thought I am to stupid to save :-)))

Cheers
Denis

Thanks for bringing the issue to our attention. It should be fixed in a future release.