aBlogSlot & aBlogSingleSlot - Serial Slot IDs scoped to Area or Singleton

[johnnybenson]

This is continuously a problem and it affects XHTML validation tremendously, not to mention that it also can impact things like slideshows from functioning properly.

When there are multiple blog slots on a single page, pulling in posts can potentially pull in the same post.

The posts pulled in do not come with unique IDs to the given Area that they belong to.

This causes validation errors to fire where posts have the same ID.

If in AREA/SLOT scenarios, a slot name is appended to the id's this problem would be solved.

This is obviously not a problem for viewing posts in the engine

[johnnyoffline]

I fixed this some time ago in 1.5.

To do this, I created a new option for slideshow called 'idSuffix'

If the option is set, the string gets appended to the ID of the slideshow.

In the case of the same blog post showing up in two separate blog slots, the idSuffix option is set in the normalView of the slot by using the unique id's for the individual blog slots

Slideshow

$id = ($options['idSuffix']) ? $id.'-'.$options['idSuffix']:$id;

Blog Slot

<?php $options['slideshowOptions']['idSuffix'] = 'aBlogSingleSlot-'.$permid.'-'.$slot.'-'.$aBlogItem->getId(); ?>