• Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    How does http://$MY_CHURCH.church.tools/api work?

    Fragen
    4
    4
    192
    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.
    • T
      tomzi
      last edited by

      In the release notes https://intern.church.tools/?q=churchwiki#/WikiView/filterWikicategory_id:30/doc:Changelog/ it says that I could access http://$MY_CHURCH.church.tools/, but for our hosted CT installation it only says
      0_1554203950398_016fbb08-a226-4860-b395-2bc352955407-image.png

      aschildA 1 Reply Last reply Reply Quote 0
      • aschildA
        aschild @tomzi
        last edited by

        @tomzi Append a simple / after the /api and it works.
        It's a know small issue for now

        3.x kein Selfhosting mehr

        1 Reply Last reply Reply Quote 0
        • H
          hallo144
          last edited by

          @aschild
          It's the opposite

          With "/api/" I get the "page not found" message, "/api" or "/api#/" work well.

          3.x Hosting und Selbsthosting, ich betreue mehrere Installationen

          1 Reply Last reply Reply Quote 0
          • hbuergerH
            hbuerger ChurchToolsMitarbeiter
            last edited by

            It seems many browser append an slash at the end of the url. This slash causes the error. I just created an patch, such that /api/ would also work and redirect to /api. If this gets merged it will be available with version 3.45

            ChurchTools Mitarbeiter – Trainer – Supporter – Academy

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