• False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • -

      As you can see Istio option has some more unwanted text at the Product Settings page (/apiconfig/services/{service_id}/settings)

      See THREESCALE-8557

       

        1. image.png
          image.png
          13 kB
        2. image-1.png
          image-1.png
          13 kB
        3. image-2022-07-25-15-40-14-456.png
          image-2022-07-25-15-40-14-456.png
          13 kB

            [THREESCALE-8556] Unwanted text in product settings RadioGroup option

            This issue has been addressed in the following products:

            RHOAM-1-RHEL-8
            RHOAM-1-RHEL-7

            Via RHEA-2022:6942 https://access.redhat.com/errata/RHEA-2022:6942

            Errata Tool added a comment - This issue has been addressed in the following products: RHOAM-1-RHEL-8 RHOAM-1-RHEL-7 Via RHEA-2022:6942 https://access.redhat.com/errata/RHEA-2022:6942

            Seems like a reasonable solution to me.

            Catherine Bartlett added a comment - Seems like a reasonable solution to me.

             So we found that this unwanted text was hidden a long long time ago (v2.7), you can find out more here

            https://github.com/3scale/porta/pull/1334

            After some discussions, josemigallas and I have considered simply deleting that unwanted text at the en.yml file. 

            Luis Villen Jaldon added a comment -  So we found that this unwanted text was hidden a long long time ago (v2.7), you can find out more here https://github.com/3scale/porta/pull/1334 After some discussions, josemigallas  and I have considered simply deleting that unwanted text at the en.yml file. 

            Well, look at commit above. Without it all HTML in i18n was escaped. With that commit this stopped happening. Why is this particular case different? If we figure that out, I assume there will be some solution to it. We can't just leave it like that.

            Aleksandar Kostadinov added a comment - Well, look at commit above. Without it all HTML in i18n was escaped. With that commit this stopped happening. Why is this particular case different? If we figure that out, I assume there will be some solution to it. We can't just leave it like that.

            Luis Villen Jaldon added a comment - - edited

            After some investigations, the problem seems to be that the way Formtastic is escaping HTMLs has changed. The way to do that at the previous version is not working now, but just because Formtastic changed, so I don't think this issue is a regression. There is no way of solving it.

            Luis Villen Jaldon added a comment - - edited After some investigations, the problem seems to be that the way Formtastic is escaping HTMLs has changed. The way to do that at the previous version is not working now, but just because Formtastic changed, so I don't think this issue is a regression. There is no way of solving it.

            This can be related to formtastic upgrade which was mitigated with

            https://github.com/3scale/porta/commit/5d3149ebb0c53178df133c2476fecb0b521921c5

            Or maybe someting similar with another component.

            Aleksandar Kostadinov added a comment - This can be related to formtastic upgrade which was mitigated with https://github.com/3scale/porta/commit/5d3149ebb0c53178df133c2476fecb0b521921c5 Or maybe someting similar with another component.

              Unassigned Unassigned
              jaurban Jakub Urban (Inactive)
              Jakub Urban Jakub Urban (Inactive)
              Luis Villen Jaldon Luis Villen Jaldon
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: