Uploaded image for project: 'Translation Flagging'
  1. Translation Flagging
  2. TRANSLATION-24

The translation button should be disabled on virtual pages

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 2.15.0
    • None
    • None

      Hi,

      When I try to report a translation for a user-id's page, it doesn't work.
      The information is not stored in the JCR.
      What's more, even if I manually add an “ametys:translations” node to the user's jcr, the translation is still not supported.

      Ametys version : 4.8.10

        1. signaler-une-traduction.JPG
          signaler-une-traduction.JPG
          5 kB

          [TRANSLATION-24] The translation button should be disabled on virtual pages

          Jean-Baptiste ABADIE added a comment - - edited

          OK for the "UserXSLTHelper.getUserContent(lang, userIdentitty) followed by USERXSTLHelper.getUserPage(content, sitename)"i'll try.

          So there is no bug i thnik, and you can close the ticket because the translation flagging button in the ribbon does'nt appear by default.

          Jean-Baptiste ABADIE added a comment - - edited OK for the "UserXSLTHelper.getUserContent(lang, userIdentitty) followed by USERXSTLHelper.getUserPage(content, sitename)"i'll try. So there is no bug i thnik, and you can close the ticket because the translation flagging button in the ribbon does'nt appear by default.

          Raphaël Franchet added a comment -

          The bug is the button should be disabled on the user's pages.
          Ineeded, virtual pages does not support translation.
          I move the ticket to the translation flagging project.

          In the meantime, in the rendering you can use the UserXSLTHelper.getUserContent(lang, userIdentitty) followed by USERXSTLHelper.getUserPage(content, sitename) to find to potential translation of the current user

          Raphaël Franchet added a comment - The bug is the button should be disabled on the user's pages. Ineeded, virtual pages does not support translation. I move the ticket to the translation flagging project. In the meantime, in the rendering you can use the UserXSLTHelper.getUserContent(lang, userIdentitty) followed by USERXSTLHelper.getUserPage(content, sitename) to find to potential translation of the current user

            Unassigned Unassigned
            jbabadie Jean-Baptiste ABADIE
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: