You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using Elastislider for my product pages and it works beautifully. However, as soon as I attempt to use Elastislider on a "listing page", something goes odd. When trying to use more than one instance of it on a page, Elastislide appears to be generating extra XHTML markup. As compared to how it behaves on a single page instance, Elastislide creates many nested divs when I use it multiple times.
Note that, in my case, I am trying to integrate Elastislide into Wordpress. This may or may not be the source of the problem or the cause of why Elastislide is nesting in this manner. So, just in case, I have already issued a question on WP forums:
Apologies for the external link but I could not figure out how to parse the code (seen in the wordpress forum link) here on Github. There is also a duplicate thread about this seen here, but it was more than 8 months old: #5)
The text was updated successfully, but these errors were encountered:
I have been using Elastislider for my product pages and it works beautifully. However, as soon as I attempt to use Elastislider on a "listing page", something goes odd. When trying to use more than one instance of it on a page, Elastislide appears to be generating extra XHTML markup. As compared to how it behaves on a single page instance, Elastislide creates many nested divs when I use it multiple times.
Note that, in my case, I am trying to integrate Elastislide into Wordpress. This may or may not be the source of the problem or the cause of why Elastislide is nesting in this manner. So, just in case, I have already issued a question on WP forums:
http://wordpress.org/support/topic/archive-listing-nested-duplicate-divs-elastislider
Apologies for the external link but I could not figure out how to parse the code (seen in the wordpress forum link) here on Github. There is also a duplicate thread about this seen here, but it was more than 8 months old: #5)
The text was updated successfully, but these errors were encountered: