The Welkin Suite Forum

Build Selection: Static Resource zipped version was modified outside of The Welkin Suite



Build Selection: Static Resource zipped version was modified outside of The Welkin Suite

started by Ryan.Sullivan 24 Apr 2017 - 03:51 PM
  • Please log in to reply

#1
windows version welkinsuite

Ryan.Sullivan

    Posted 24 Apr 2017

    I have a zipped file static resource containing various javascript files.  

    When I use The Welking Suiite to edit a javascript file inside the zipped static resource and execute Build Selection, the static resource is saved to Salesforce etc and everything works fine with the following exception.  I get an error in the Error List inside The Welkin Suite stating:

     Error 1 Zipped version of ContractsBatchUpload.resource was modified outside of The Welkin Suite. It was renamed to ContractsBatchUpload.resource.bak1 and changes from the unzipped folder were used.

    Every time I build changes, a new BAK file is saved to the project -> src -> staticresources folder.

    So I get, for example:

    zipfile.resource

    zipfile.resource.bak

    zipfile.resource.bak1

    etc


    After a few edits I get multiple BAK files accumulated that I periodically delete to clean things up.

    Any ideas what is causing that / how I can prevent it? 





    1 replies to this topic

    #2

    kate.dulko

      Posted 24 Apr 2017

      Hi Ryan,


      Thank you for your bug report.


      This is known issue to us and it is present in our backlog to be fixed.

      Currently, as a workaround, you can follow the next steps to build your statics:

           1) please open the menu Project -> 'Project metadata components';

           2) disable the checkbox for the Static Resource metadata - it will be removed from your TWS project;

           3) after this, please open the 'Project metadata components' again and enable Static Resouces;

           4) please pull from Salesforce.


      I want to draw your attention that the described workaround works for one build, the further one will be failed with the same error again. We understand that it can be annoying to refresh static resources each time before editing, however, our developers will solve the issue soon.

      I will let you know when we will release the fix for this issue.


      Regards,

      Kate




      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        

      Back to General talks


      Boost Your Productivity. Get Started Today

      Try Free Trial