AnsweredAssumed Answered

What, precisely, does "export customisations" cover/not cover?

Question asked by Phil Gibbs on Aug 30, 2017
Latest reply on Sep 1, 2017 by Matt Marum

Hello,

 

We're trying to migrate some of our work between development instances.

 

I was under the impression that only changes made through Studio gets exported when using "export customisations", and any code written manually (e.g. new files) needs adding through a separate hand-made package with manifest.

 

However... when we use "export customisations", many of the new files we've written manually are actually included in the export. But not all of them. This leaves us a bit confused over what precisely gets included in these exports, and what we need to package together ourselves.

 

Example:

/custom/modules/Accounts/CheckOverallAuthorityAssigned.php (new file) - did get exported

/custom/modules/Contacts/clients/base/views/validate-contact/validate-contact.js (new file) - did not get exported

 

Our only thought is that validate-contact.js didn't get exported because it's in a brand new directory, whereas CheckOverallAuthorityAssigned.php lives in a pre-existing directory. Does anyone have any insight

 

Thanks in advance.

Outcomes