talque
  • External integrations for talque
  • JSON API (readonly)
    • General
      • Locales and Text
    • Organization
      • Read
    • Lecture
      • List
      • Read
      • Files
      • Authorization
    • Speaker
      • List
      • Read
      • Authorization
    • Participants
    • Vendors
      • List
      • Read
      • Authorization
    • Room
      • List
      • Read
    • Enumerations
      • Locale
  • Deep links
    • General
    • Organization
    • Profile links
    • Lecture links
    • Partner links
    • Post links
    • Map links
    • Video rooms
  • Webhooks
    • General
    • Authentication
    • File upload
    • Users
    • Invites
    • Tickets
    • Vendors
      • Create
      • Update
      • Delete
    • COMING SOON: Announcements
    • COMING SOON: Lectures
    • Map Data
      • Map layer
      • Map features
      • Update references
  • COMING SOON: Chat Bots
  • Wordpress Plugin
    • Installation
    • Pages
    • Shortcodes
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Javascript plugin
    • Introduction
    • Installation
      • Initial page
      • Filters
      • Optional settings
    • Routing
    • Configuration
  • Single Sign-On
    • OAuth2 Login
    • Website data
    • OAuth2 Flow
      • Request an Authorization Code
      • Exchange for Access Token
      • Authorized Requests
  • SELF-SERVICE LINKS
    • Event Ticket Token
  • Old Wordpress Plugin
    • Download
    • Pages
    • Shortcodes
    • Filter Options
    • Style Options
  • Old Javascript Plugin
    • Introduction
    • Routing
    • Installation
  • Troubleshooting
    • Firewall Configuration
  • Talque Plugin
    • Download
    • Installation
    • Configuration
Powered by GitBook
On this page
  • Hosting as static files
  • Hosting via a Content Management System

Was this helpful?

  1. Talque Plugin

Installation

PreviousDownloadNextConfiguration

Last updated 2 years ago

Was this helpful?

For the plugin installation you need to pick a path on your web server where the talque plugin will be located. For example, users could load the plugin by going to, https://my-server.com/talque-plugin. In this example the plugin path would be talque-plugin. You can choose the path arbitrarily for your installation, but it must match the base href setting (see below).

Hosting as static files

In the simplest case, you just host a set of static files under that path. That is, on your web server

  1. Create a subdirectory (for example talque-plugin) on your web server.

  2. Unzip the content of talque-plugin-LATEST.zip into that subdirectory, so that the index.html file is at the root of your subdirectory.

  3. Edit the <base href="/talque-plugin/"> tag in the index.html file to match.

  4. You should now be able to see the plugin by opening https://my-server.com/talque-plugin.

  5. in the index.html to match your network.

  6. on top in the index.html file.

Hosting via a Content Management System

In this case, also download the assets and make sure they are served as static files. You can generate the index.html file via your backend, just copy the meta, base, script, and style tags from our template. Then place the <rli-tq-plugin-root> tag at the appropriate place in your page layout.

Note:

  • Copying the <meta> tags is optional but recommended

  • The <base href="..."> the serving url

  • The multiple <script> tags have cache-bursting identifiers, copy them as is.

  • Copy the <style> tag as is

  • Attach to the <rli-tq-plugin-root> tag

  • The talque plugin needs to cover most of the screen and there should not be a scrollbar. We recommend a flexbox layout where you provide a fixed-height custom header, and the talque plugin is placed below (with flexbox settings so that the plugin grows or shrinks to fill the available space).

  • We use and include , so you can use their utility classes for alignment.

  • For styling your either also use tailwindcss or scope your css to only apply to the header and not to the rest of the page.

https://tailwindcss.com/
your directory name
Edit the org-id and config-id
Add your own menu header
tag must match
the org id and config id for your network
own header / menu