opened
mcsheaj
username_0
**This issue was imported from [CodePlex](http://SPEasyForms.codeplex.com/workitem/12)**

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-19 at 11:47
I'm clicking "Save" and nothing is happening. I'm pretty sure it's because that library isn't on the site. I remember you mentioning it at SPS VA Beach, but I don't see any documentation about it.




Thanks!

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-19 at 11:59
It also appears that when the solution was activated, all files in the Style Library were not automatically checked in. I got them checked in, but the "Save" button still isn't doing anything. (And, it was the Style Library I was thinking of.
 It is at the root of the site collection that this sub-site is on.) Using IE 10.0.9200.17183.

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 19:32
All of the files I install during deployment are saved to the root Style Library, but the configuration files for a given site are saved in the Site Assets library (which should be at the URL <web>/SiteAssets). The library type should theoretically
 be Site Assets, but I believe it wouldn't matter if it were just a plain document library as long as it's url is SiteAssets (no spaces).

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 19:40
Just to make sure I understand what you're seeing, when the form first loads the Save button should be quasi-transparent. Once you make a change, it should change to solid (any change, add a container, create a visibility rule, whatever). Once it is solid,
 if you click it, it should save the config and turn back to quasi-transparent. If you click it when it is quasi-transparent, nothing will happen.



Does any of this make sense with what you're seeing? i.e. does it start transparent, go solid on a change, and stay solid after you click it? or does it never go solid (i.e. the button always looks the same no matter what you do)? etc. There is nothing to indicate
 a save has occurred other than the change in the appearance of the button (and a couple of other buttons on the ribbon actually change too, generally when you have changes that need to be save or when you do a save).

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 21:20
Also, on the check-in issue, this is a known issue with sandbox solutions on SP 2010 (you didn't say, but I assume you're on 2010). The only way around it right now is to turn off 'require checkout' on the style library before you install the solution.
 If you've already activated the solution, the easiest fix is to disable the solution, delete the SPEasyForms directory in the Style Library, and then re-install the solution. I haven't seen this issue on 2013 or Office 365.

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-20 at 08:49
It was the SiteAssets library I was missing on the site! Would you add this into your installation instructions for others?



Now that I have the library, the "Save" button behavior is how you mentioned above.




And, thanks for the quick response! I'm rockin' and rollin' now!!!



Erin
What's the library name/type that must be on the site where the config files get saved?
issue
closed
mcsheaj
username_0
issue
opened
mcsheaj
username_0
**This issue was imported from [CodePlex](http://SPEasyForms.codeplex.com/workitem/12)**

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-19 at 11:47
I'm clicking "Save" and nothing is happening. I'm pretty sure it's because that library isn't on the site. I remember you mentioning it at SPS VA Beach, but I don't see any documentation about it.




Thanks!

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-19 at 11:59
It also appears that when the solution was activated, all files in the Style Library were not automatically checked in. I got them checked in, but the "Save" button still isn't doing anything. (And, it was the Style Library I was thinking of.
 It is at the root of the site collection that this sub-site is on.) Using IE 10.0.9200.17183.

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 19:32
All of the files I install during deployment are saved to the root Style Library, but the configuration files for a given site are saved in the Site Assets library (which should be at the URL <web>/SiteAssets). The library type should theoretically
 be Site Assets, but I believe it wouldn't matter if it were just a plain document library as long as it's url is SiteAssets (no spaces).

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 19:40
Just to make sure I understand what you're seeing, when the form first loads the Save button should be quasi-transparent. Once you make a change, it should change to solid (any change, add a container, create a visibility rule, whatever). Once it is solid,
 if you click it, it should save the config and turn back to quasi-transparent. If you click it when it is quasi-transparent, nothing will happen.



Does any of this make sense with what you're seeing? i.e. does it start transparent, go solid on a change, and stay solid after you click it? or does it never go solid (i.e. the button always looks the same no matter what you do)? etc. There is nothing to indicate
 a save has occurred other than the change in the appearance of the button (and a couple of other buttons on the ribbon actually change too, generally when you have changes that need to be save or when you do a save).

**[username_0](http://www.codeplex.com/site/users/view/username_0)** wrote 2015-01-19 at 21:20
Also, on the check-in issue, this is a known issue with sandbox solutions on SP 2010 (you didn't say, but I assume you're on 2010). The only way around it right now is to turn off 'require checkout' on the style library before you install the solution.
 If you've already activated the solution, the easiest fix is to disable the solution, delete the SPEasyForms directory in the Style Library, and then re-install the solution. I haven't seen this issue on 2013 or Office 365.

**[ebglenn](http://www.codeplex.com/site/users/view/ebglenn)** wrote 2015-01-20 at 08:49
It was the SiteAssets library I was missing on the site! Would you add this into your installation instructions for others?



Now that I have the library, the "Save" button behavior is how you mentioned above.




And, thanks for the quick response! I'm rockin' and rollin' now!!!



Erin
What's the library name/type that must be on the site where the config files get saved?
issue