Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    change Kopano Webapp Manual URL

    Kopano WebApp
    2
    4
    225
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rgsell
      rgsell last edited by rgsell

      Hi,

      I would like to change the webapp manual URL to a corporate website with translated content.
      Therefore I thought it is possible to change this variable in the config.php:

      define("PLUGIN_WEBAPPMANUAL_URL", "https://ticketsystem.company.at/help/de-de/58-kopano-mails-termine-kontakte/");
      

      However, the webapp clients add a ‘\mail.html’ to this URL, which results in a “page not found”.

      Then I checked out this file:
      /usr/share/kopano-webapp/client/kopano.js

      and in line 3263 I changed mail: “mail.html” to mail: ""

      to make it work.
      However I don’t know if that has any side effect and it’s not update persistent either.

      Why is it possible to set this variable in the config.php if it doesn’t work in the end?

      Cheers,
      Roland.

      1 Reply Last reply Reply Quote 0
      • rgsell
        rgsell last edited by

        I changed the URL to this:

        define("PLUGIN_WEBAPPMANUAL_URL", "https://ticketsystem.company.at/help/de-de/58-kopano-mails-termine-kontakte/#");
        

        as a work around without client changes.

        However, this could be handled much better. ;-)

        fbartels 1 Reply Last reply Reply Quote 0
        • fbartels
          fbartels Kopano @rgsell last edited by

          Hi @rgsell,

          looking at the deployed functionality it looks like it wants to link to mail.html when someone is within the mail context and link to eg contacts.html when the user is within the contacts context.

          So the current implementation tries to show the user the most relevant part of the documentation, but at the expense that alternative documentation locations would need to follow the same overall structure as the Kopano provided one.

          Regards Felix

          Resources:
          https://kopano.com/blog/how-to-get-kopano/
          https://documentation.kopano.io/
          https://kb.kopano.io/

          Support overview:
          https://kopano.com/support/

          rgsell 1 Reply Last reply Reply Quote 0
          • rgsell
            rgsell @fbartels last edited by

            @fbartels Ah, that actually makes sense. :-) Thanks for the clarification.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post