We have modified the Edit and Detail View layouts for some modules from the standard two-column display to a three or four column display. We found that this was a better use of the screen real estate and eliminated the need to perform so much vertical scrolling/paging.
After our upgrade, we now notice that these modified views now have an undesired horizontal scroll bar because the individual columns are now much wider than before. We use SuiteR and Suite7 themes and I have tried the following approaches to resolve this issue.
Attempted solution 1:
I have attempted to resolve this issue by editing the metadata file detailviewdefs.php in my custom directory to reduce the widths array label & field size for each of my columns. Now when I refresh the Detail view for this module, I see a temporary flash of a corrected/narrow display but something is then altering this display back to the undesired wider layout.
Attempted solution 2:
I see in the upgrade scripts that changes have been made to Suite7 & SuiteR, so I copied the folders from version 7.7.9 into my custom/themes directory and have set developer mode and performed a Quick Repair. I am not noticing any difference after this change.
Does anyone have a suggestion as to what else I can try? Does anyone know what might be causing the phenomenon in my attempted solution 1 where my screen appears to display as desired but then something updates afterwards?
Thanks,
Dianna
Dianna, if you’re going to try this, don’t try it for 7.8.x, go straight to 7.10 LTS or 7.11 and try to fix it there.
Since 7.9, with theme SuiteP, which is the only option you will have, bootstrap was introduced and that gives you a different way of setting up columns. I am not sure if it will be easier or harder for you, depends on how you did the column changes before.
But I don’t think it’s worth fighting this problem in a version that is already being deprecated. Going to the latest seems a better idea, imho.
Anyway, what you’re seeing now is probably just some CSS settings differences. With some extra changes to margins and paddings things should fall in place.
Thanks for the response.
Unfortunately, the fact that SuiteP is the only theme available after version 7.8.x is what is keeping us from upgrading beyond that.
SuiteP, even with the numerous improvements, has the following limitations:
- Does not appear to support more that two columns in the Detail and Edit Views
- Breaks our Login/Sudo Plugin which allows admins to login as a user to test issues or setup dashboards
- Still wastes a lot of screen real estate compared to Suite7
And I did perform a test upgrade from 7.8.31 to 7.10.18 today to see if these issues have been resolved and saw that they have not so we are stuck at 7.8.31 for awhile. 
Thanks,
Dianna
We’re doing a lot of work to try and avoid situations like these where people feel the need to be “stuck” in an older version.
https://suitecrm.com/suitecrm/forum/suitecrm-7-0-discussion/24652-suitecrm-7-8-x-reaching-its-end-of-life
I’m currently working on a lengthy migration guide (opinions welcome): https://deploy-preview-305–suitedocs.netlify.com/blog/larger-upgrades/ (that is only a preview of a draft)
And we made our sprint planning public, and had a couple of sprints dedicated to the 7.8 EOL:
https://github.com/salesagility/SuiteCRM/issues/7358
https://github.com/salesagility/SuiteCRM/issues/7499
You can even follow the Kanban here: https://github.com/salesagility/SuiteCRM/projects/7
(the columns issue is there: https://github.com/salesagility/SuiteCRM/issues/3310 and also the spacing: https://github.com/salesagility/SuiteCRM/issues/7373
Now, the reason I write all this is that we really need the Community to pull together creatively in order to achieve our goals. SalesAgility cannot possibly handle such a huge project alone, and that was never the intention. Some of those tasks in the Kanban need to be taken by developers from the Community, and where the development capabilities are not enough, then other solutions like what I suggested here should be considered.