Skip to content
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

Property History CSS being sanitized #319

Open
yunusyerli1 opened this issue Aug 18, 2023 · 1 comment
Open

Property History CSS being sanitized #319

yunusyerli1 opened this issue Aug 18, 2023 · 1 comment
Labels
Area: Frontend Priority:Moderate Issues & PRs that are minor; broken styling; warns; there are practical workarounds Status: Fix Proposed A issue that has a PR related to it that provides a possible resolution Status:Requires Updates Issues & PRs which requires input or update from the author Type: Bug Something isn't working

Comments

@yunusyerli1
Copy link
Contributor

Issue

When creating a Case and pulling in the Property History, the formatting of the Property History looks correct initially (e.g. the CSS is working and it displays properly). However, when you save the Case, the CSS is stripped out. Need to find a way to disable this so the CSS remains after saving the record.

Expected Behavior

Whenecer you save a Case and change tabs in detail view, CSS of the related fileds should take effect.

Actual Behavior

Whenecer you save a Case and change tabs in detail view, CSS of the related fileds does not take effect.

Possible Fix

Add purifyHtml variable in SugarBean.php and get the value from $def['metadata']['purifyHtml'].

Steps to Reproduce

  1. Create a case.
  2. Select a Service.
  3. Fill UPRN and save.
  4. Change tabs.

Context

After filling UPRN, newly created fields are being styled. But after save button, these style disappears.

Your Environment

  • SuiteCRM Version used: 8.3.0
  • Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome Version 115.0.5790.171 (64-bit)
  • Environment name and version (e.g. MySQL, PHP 7): Wamp Server, PHP 7.4.33, MariaDB 10.4.12
  • Operating System and version (e.g Ubuntu 16.04): Windows 11
yunusyerli1 added a commit to yunusyerli1/SuiteCRM-Core that referenced this issue Aug 18, 2023
@gemartin21 gemartin21 added Status: Fix Proposed A issue that has a PR related to it that provides a possible resolution Area: Filters Issues & PRs related to all things regarding Filtering and removed Area: Filters Issues & PRs related to all things regarding Filtering labels Aug 18, 2023
@johnM2401 johnM2401 added Type: Bug Something isn't working Priority:Moderate Issues & PRs that are minor; broken styling; warns; there are practical workarounds Area: Frontend labels Aug 31, 2023
@johnM2401
Copy link

Hey Yunus!

It looks like the Steps to Replicate here are for a specific customized environment.

If possible, when you get a chance, could you add Steps to Replicate for a generic Vanilla suitecrm environment?

Thanks!

@johnM2401 johnM2401 added the Status:Requires Updates Issues & PRs which requires input or update from the author label Aug 31, 2023
mpuyosa91 added a commit to yunusyerli1/SuiteCRM-Core that referenced this issue Nov 10, 2023
mpuyosa91 added a commit to yunusyerli1/SuiteCRM-Core that referenced this issue Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Priority:Moderate Issues & PRs that are minor; broken styling; warns; there are practical workarounds Status: Fix Proposed A issue that has a PR related to it that provides a possible resolution Status:Requires Updates Issues & PRs which requires input or update from the author Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants