-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken HTML in new module dialog in module builder #5054
Comments
@michalhudecek thanks for the bug report, but please do fill in the entire issue template. How can we even begin to take a look at this without having any idea what your version of SuiteCRM is? Or your PHP, etc.? |
SuiteCRM PHP 7.1.13 Windows 10, Google Chrome 63 I would test the issue in your online demo but I don't see admin options there. |
There is a live demo with admin access here: https://www.softaculous.com/demos/SuiteCRM But it is still on 7.9.9 and this bug doesn't show there. I have a 7.9.10 (PHP 7.0) and I get the grey overlay bug, but not the broken HTML. Can you try a few Repairs from Admin / Repair? Javascript stuff, etc. |
This was a clean installation, I haven't done anything besides hiding some modules in **Display Modules and Subpanels , editing items in Dropdown Editor and adding new fields in Studio for Clients and Contacts modules. Apart from that I recently upgraded to 7.9.10. I have never tried Module Builder before though so I do not know if it was working before the upgrade or not. |
@michalhudecek Have you tried the proposed fix here? #5056 |
@Dillon-Brown Yes, that helps. Is the fix coming to LTS version as well? 7.9.X versions seem to be very buggy. |
@michalhudecek Yes, this issue will be fixed in both 7.9.x and 7.8.x LTS. |
Fixed #5054 - Broken HTML in new module dialog in module builder
Clicking on New module in Module Builder shows a broken dialog with an error and broken HTML . No way to continue.
The gray overlay is probably caused by #4983.
The error shown is probably related to #4139
The broken HTML is however a separate bug.
The text was updated successfully, but these errors were encountered: