Changes to detailviewdefs.php lost after deploy

[bperciac]

I have made some extensive changes to my accounts detailviewdefs.php file, and the behavior of SugarCE 5.0.0b and 5.0.0c are VASTLY different.

In 5.0.0b:
Changes made to detailviewdefs.php were not effective until the view was opened in Studio, the view loaded, and then applied. Once this was done, the changes were immediately visible in account views.

in 5.0.0c:
The exact opposite is true. When the file is edited and saved, the changes are immediately effective. However, if any layout changes are made and applied, then the manual changes are lost.

HELP! I am working on a custom application, and this is MAJORLY problematic... My use case is admittedly odd, but this is the ONLY issue I am bumping in to

Thanks!

[SugarDev.net]

I don't think this is exactly how it happens. I don't recall seeing this kind of change in the upgrade (I code review Sugar's patches).

Please make sure you have a good thorough understanding of the way Sugar overrides the default metadata files with custom files, and where Studio makes its modifications. Also, check out the rebuild extensions functionality, developerMode, and Repair.

[bperciac]

I don't think this is exactly how it happens. I don't recall seeing this kind of change in the upgrade (I code review Sugar's patches).

Please make sure you have a good thorough understanding of the way Sugar overrides the default metadata files with custom files, and where Studio makes its modifications. Also, check out the rebuild extensions functionality, developerMode, and Repair.

While I appreciate that this should not be the case, I assure you that it is. I have been fighting with this for over a week, and have rebuilt cache, deleted the files, etc. When I restore my 5.0.0b from backup, this behavior does not exist.

Comments welcome, as this has this project at a dead standstill.

Bob

[DragonflyMaster]

While I appreciate that this should not be the case, I assure you that it is. I have been fighting with this for over a week, and have rebuilt cache, deleted the files, etc. When I restore my 5.0.0b from backup, this behavior does not exist.

Comments welcome, as this has this project at a dead standstill.

Bob

Since you are not the first one who say so, I believe you.
As for me, after upgrading to 5.0.0c I haven't noticed this behaviour , because I'm actually so used to manual customizations that I haven't had this particular situation yet.
Maybe someone from Sugar Team could ping in and say something about it?

[bperciac]

Any word on this? This is an issue, and any help or pointers is recommended..

Help!

Bob

[DragonflyMaster]

Any word on this? This is an issue, and any help or pointers is recommended..

Help!

Bob

Since no Sugar Team member has chimed in yet, I think you should send a private message to one of them.

[ToniFatec]

We had the same problem in here with Sugar 5.0.0c.
Up to now Studio read the files of the module and copy them to /custom/working/module/metadata.
By knowing it I use to make a manual modification in code. Then copy it manually to working of Studio. Them edit the layout in Studio and click "Save and deploy" option, which until 0b version copy the layout changes WITH the manually added changes to the final /custom/module/metadata folder, and all worked fine. But now it appears Studio is writing its "working" files in other place, and is from there the current deployed files appear to come from.

I believe we have a new bug, or Studio has changed its behavior.