KPI to be measured
Ask a question
Was this article helpful? 0 out of 0 found this helpful
In this short article we are going to explain you how to activate the WordPress Connector. Once the application has been activated through the Marketplace, using its management console you will be able to download a .zip file which is the plugin that has to be manually installed within the dashboard of your WordPress account, like any other traditional plugin. Besides this, you will also find some information such as the clientId, the app-id and the application’s owner; take note of these information as they will be used during the plugin's configuration in WordPress, along with the folder where the content will be imported.
Along with these required information you will be able to configure how content will be embedded into your articles, by customizing the embed code’s parameters. Available parameters are:
- Hide controls
- Hide Player’s skin
- Display linked content
- Display attachments
- Context (you will be able to select any of the available contexts)
- Content cache lifetime (seconds)
Once the plugin's configuration has been completed, content synchronization process can be initiated by clicking on a specific button in the plugin's console.
Any available content will be imported in THRON, will be linked to the folder on which the application has been installed and will be assigned to the application’s owner; this will also happen to any other content which will be published into WordPress whether they are audio, video, images or articles/posts (they will be imported as Pages in THRON). Moreover, these content will be subject to all the THRON functionalities, such as: semantic engine scan and automatic tagging, behavior engine tagging, manual tagging, recommendation, etc.
Beside this procedure, the application behaves like any other THRON application: it can be found in the “Console” section of Marketplace and it can be managed by authorized users.
In order to allow THRON to create new content starting from a URL-related source file, the plugin must be installed on an entity which has to be publicly accessible with a proper registered domain and, in case of HTTPS, with a valid and non self-signed certificate.
If you plan to have an "always-on" staging website parallel to that in production:
The code of the plugin (the .zip file) is the same regardless of the application to which it is linked, so it can be installed on any server.
As regards the application itself, we recommend you to install two different applications on two different folders, in order to avoid potential overwrites and collisions.