Follow

Upgrading Express 1.0 to 1.1

Version 1.1 of Pugpig Express includes a major change to the Contents Page and app Table of Contents options provided in an article and as a result it will require some content to be reset.

Pre 1.1

Previously an article page had the following group of entry field options:

 

 

This combined some settings that applied to the editions Contents Page (HTML) as well as some settings that applied exclusively to the native apps Table of Content appearance for an edition which we felt was confusing.

The Settings included:

  • Appearance on Contents Page with options; Standard, Hero and Hidden
  • Custom Contents Page image; an override for the main image used as default
  • Table of contents tile image; an override for the main image used as default 

Post 1.1

The update to version 1.1. release introduces these into two separate groups of options to the Article content type along with some extra config too:

1. Table of Contents Settings now has its own group of fields:

  • Table of contents tile or icon image
  • *New* Hide from Table of contents option

2. Contents Page Settings now has its own group of fields:

  • Appearance on Contents Page with options; Standard, Hero and Hidden
  • Custom Contents Page image; an override for the main image used as default
  • *New*Custom contents page headline
  • *New* Custom contents page standfirst

As a result some of the previous Settings need to be reset, please read the important changes to make to your content highlighted below:

IMPORTANT CHANGES TO MAKE

For Contents Page; if an article was set to be 'Hidden' or 'Hero' on the contents page, it will need to be reset again for yet to be published editions.

For Table of Contents the optional tile image override will also need to be reset however it will default to use the articles main image (if one is set) so this isn't essential.

Please note for this release we have kept the old Pre 1.1. Content Settings group in for visibility so you can see the previous options you used and copy these across into the new fields. However, these old fields will no longer work so avoid using them moving forward and we will switch them off in the next release in a couple of weeks time.

We apologise for any inconvenience caused with this change however there are a number of improvements that come with this release. We will always aim to mitigate content changes required in future releases and provide a better way for editorial teams to manage this moving forward.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk