Specific order of extension vardef rebuilding?

Hi Everyone,

Hopefully an easy question here for someone who is more in the know than myself:

Is there a certain order that files in custom/Extension/modules/%MODULE%/Ext/Vardefs are rebuilt?


The reason I'm asking is because when some fields were originally created (before my time) they were done as an array with a list of keys and values.

Since then, we've upgraded to 7.6 and some of them need to have the readonly property set to true. However, when I've deployed a package including this vardef, the field creation vardef occurs later in custom/modules/Accounts/Ext/Vardefs/vardefs.ext.php . This means that the readonly settings in another file are being overidden when the array is re-created later on.

Is there some sort of order that these need to be created, or ordered in? If so, what are they?

Thanks!

Parents
  • Coincidentally, an internal discussion on this very topic has been taking place recently. Long story short, there is some unpredictability to the order as there are some rather low level operating system factors that influence how files are read. A future version of Sugar will hopefully have a more predictable approach.

    For the meantime, the best suggestion I can give you is to fiddle with the file names and the last modified date for the files.

Reply
  • Coincidentally, an internal discussion on this very topic has been taking place recently. Long story short, there is some unpredictability to the order as there are some rather low level operating system factors that influence how files are read. A future version of Sugar will hopefully have a more predictable approach.

    For the meantime, the best suggestion I can give you is to fiddle with the file names and the last modified date for the files.

Children