Since this is the most common CMS not yet integrated into the CMP, we first started with creating plugins for the Drupal versions 6, 7 and 8.
An example use-case:
- Add the Drupal website url in the Website+CMS page under Settings.
Our drupal demo link are:
- We need a feed channel where we are going to publish content and then have the content ingested into our Drupal site. We can either create a new one or use an existing feed to publish to. In our case, we are going to create a new feed.
- Let’s now create a Quick Article Post with an article selected from the CMP’s Content Explorer and select a feed channel to publish to.
- Publishing an article to Facebook requires that content to have a canonical link. So let’s select a Facebook channel in our task for publishing along with the feed channel.
- Hit the publish button. We will see the post successfully published to the feed channel. The Facebook channel will show pending publishing as it waits for the article content to be updated with the canonical link.
- We will now ingest the published article from our feed to the Drupal site. We do this by copying the json / atom api link which is exposed when the Export Feed button is clicked, and adding in that link on our Drupal site.
- Finally we go back to our task page and should see the pending Facebook channel content has been successfully published.
To summarize, the following steps needs to be done for this feature to work -
Integrate CMP feed in Drupal and install the Drupal modules by following the instructions given here
Make sure the drupal website is added in the CMP here
Url examples -
Article canonical link: http://drupal-demo.com/node/12-05-17/old-school-vs-new-school
Website url in the CMP: http://drupal-demo.com/
The `http` protocol must be included.
- No need for the user to visit the article after publishing
- Near real time, as our API service will be called as soon as there is a new publish
- No need for figuring out the regex for the website url pattern
- Until the CMP has native integration with whatever CMS is being used by the clients, a plugin for each type of CMS has to be developed.
- Since there are many bots that ingest content from various sites, the API service maybe hit with many different website urls for the same article. In order to prevent updating the article with wrong canonical links, the client needs to add the CMS base website url as is in the CMP settings page under the Website+CMS tab.