Info: This feature is marked as deprecated in Enterprise Server 10.6.0 and higher. Integrators are advised to migrate their solutions to Aurora publishing through the use of Digital articles instead.
Show me the technical details
The following has been made deprecated:
Each type of story or content that is going to be published requires a unique Publish Form and therefore a Publish Form template on which that Publish Form is based. Differences in templates could be the number and type of fields that the Publish Form includes, the location on a Web site where it is posted to, and so on. It could therefore be possible that new Publish Form templates need to be created on a regular basis.
The method of creating a Publish Form template depends on the Publication Channel for which the Publish Form template is going to be used:
- For Drupal
- For Facebook or Twitter
Creating a Publish Form template for Drupal
Creating a Publish Form template for Drupal is done by creating a Drupal content type and importing it into Enterprise.
Step 1. Create a content type in Drupal 7 including the fields that should be used.
Note: The order in which the fields are placed is also the order in which these fields appear in the Publish Form template.
Step 2. Import the content types into Enterprise. See Importing content types from Drupal 7 or Drupal 8 into Enterprise Server 10.
Creating a Publish Form template for Facebook, Twitter, or WordPress
Publish Form templates for Facebook, Twitter, or WordPress cannot be created manually: the setup of the template is hard-coded in the Server plug-ins and can therefore not be changed.
Note: Technically you could manually modify the configuration files of the plug-ins, but this is not supported and should be done at your own risk.
- 25 February 2019: Added a statement about this feature being marked as deprecated for Enterprise Server 10.6.0 and higher.