What are the files in Sugar 11 that are called orderMapping.php?

If I use the .gitignore you're providing (and if I'm reading correctly), those ordermapping files will be versioned, but you're telling use they shouldn't be, I guess we can agree on that being ambiguous? :)

In general, I wonder,what do you call "generated files"? As far as I know, every time someone creates a field, or does basically anything in the studio, some files are generated (vardefs, view files, dependencies...), but we should indeed be versioning those. I'm being picky, but newer developers will be confused.

There is a lot of confusion around the subject of versioning with this product, that's because the knowledge that some generated files should be versioned and some shouldn't only comes from trial and error, and that's not ok at all. We have a perfect example here : a new type of file appears in a new version, no one knows what to do with it. We had the same issue with role-based view files back then if I remember correctly : they are views so they should be versioned, but they're named after a technical ID that is environment-specific by nature... We figured it out, but it wasn't the best experience ever, to say the least.

Any product or framework should provide a default .gitignore that doesn't need too much tweaking, default git hooks if needed, and developers (especially newer ones) shouldn't have to worry about making a mess in their repository by clicking a button.

But anyway, good to know we can ignore those files, but I wonder how my client's instance will know about file orders if that order has been decided on my local instance, and the order files haven't been packaged or versioned? Will that be an issue?

Hi Chris,

The .gitignore provided in developer guide was intended to just be an example. But I can make sure it gets updated to properly exclude generated orderMapping.php files.

I think it's helpful development model to work from a Module Loadable Package like we've done with Professor M.

https://github.com/sugarcrm/school

That keeps your source code pristine and separate from the Sugar instance. It's also necessary anyway when developing code for SugarCloud.

Matt Marum said:

We have provided guidance in past that you should not be versioning generated files within source control and not something you'd want to include in Module Loadable Packages either.

Yes true. But the only mention of the files are in the release notes. There are no mentions on where these files are stored and how they work. Thats what I was looking for. If we don't have to add them to a module loadable package that's fine but just let the documentation be clear about that its a generated file and should be treated as such.. 

How does this work for on-premise installs that, because of VCS, have systems where all files have the same date?

The first time the orderMapping is created it will do its best to place them into a particular order based upon the date. You can touch a file and remove it from the orderMapping.php to move it to the end; this will place the file at the end.

OK, I got around to testing this and while I am sure it fixes something it doesn't fix any of the problems I have day to day.  I explain one of my biggest language issues in this video.

https://www.youtube.com/watch?v=Xb-7zSjJqTw

The audio is low so you might need to turn the volume up.  Pretty much any bug that related to labels on relationships is still a big in Sugar V11.

Problem is that it should always put the xx_xx.lang.php file at the top no matter what.  When you put the custom relationship language files first they override changes made in Studio and saved to the xx_xx.lang.php file.

<?php
// created: 2021-06-13 20:01:09
$extensionOrderMap = array (
  'custom/Extension/modules/Accounts/Ext/Language/en_us.customaccounts_accounts_1.php' => 
  array (
    'md5' => '8d357aebaac0fe931d15f22d5658566b',
    'mtime' => 1623614400,
    'is_override' => false,
  ),
  'custom/Extension/modules/Accounts/Ext/Language/en_us.customaccounts_accounts_2.php' => 
  array (
    'md5' => 'e8964d384c639690c66cd92bec940bff',
    'mtime' => 1623614415,
    'is_override' => false,
  ),
  'custom/Extension/modules/Accounts/Ext/Language/en_us.lang.php' => 
  array (
    'md5' => 'e560cbfb628ea8d32d637b2b4b558479',
    'mtime' => 1623614430,
    'is_override' => false,
  ),
  'custom/Extension/modules/Accounts/Ext/Language/en_us.customaccounts_accounts_3.php' => 
  array (
    'md5' => '68a9830d27b43e24b1a087eaa5e41354',
    'mtime' => 1623614467,
    'is_override' => false,
  ),
);

Hi,

Matt Marum gentle reminder that the dev documentation hasn't yet been updated here support.sugarcrm.com/.../

Thanks, I'll update it.