I think the problem is that the TermsPartHandler triggers the TermCountProcessor as a Task async and the TermCountProcessor used the ContentTypeId as a parameter.
If a ContentItem gets deleted, the TermCountProcessor cannot access it anymore and the Terms won't getting reprocessed which results in a wrong count.
I altered the ITermCountProcessor interface to accept TermPartRecordId's instead of the ContentTypeId and use this id's directly.
I also had to add a call for the ITermCountProcessor in the TermService UpdateTerm method. This is because when you re-publish a ContentItem only the new Terms are available in the PublishedEvent - but also terms from the previous version needed to be processed.
- Implemented HTML filters for Html, Text and Paragraph elements
- Tokens are only processed on the front-end, not in the editor page itself. This also prevents an exception when the {Shape.Execute} token is used with a theme specific shape.
Work Item: 21304
This fixes an issue where "complex" form field names aren't properly mapped to key value pairs, such as "Parts%5B0%5D.Bindings%5B0%5D.Name" instead of "Parts[0].Bindings[0].Name"
The issue is that the media item element renders the selected media items with the Thumbnail display type.
The Media shape templates for that display type do not include necessary styling themselves; instead the media library picker UI includes the necessary stylesheet.
The cache keys of action method parameters are now prefixed with "PARAM:" to avoid collisions with built-in keys such as "theme". Similar to the "HEADER:" prefixing done for headers.
Work Item: 21277
Modified admin-taxonomy-tags.js to fix js problem related to tagit.
The calls to data() jquery selector in the autocomplete initialization code where not matching on the provided keys. The keys have been modified to resolve the issue.
Work Item: 21238
Instead of using a custom writer for the Response.Output property, the OutputCacheFilter now uses a specialized Stream class for the Response.Filter property, which captures anything written to it. This seems to work with any type of result, including FileContentResult.
Work Item: 20881
Sébastien Ros