Right now, we're not differentiating between different instances of the same password, so the content of each unlocked instance gets dumped into the block of all instances.
This only happens when unlocking with ajax. On refreshing the page, the correct content is inserted into the password-protected blocks. So, a simple fix is to disable ajax with the ajax='false' attribute.
I am tracking each shortcode instance in the default template, but need to make the Ajax JavaScript smart enough to use them.
Screenshot: Locked state with two instances of same password.
Screenshot: Both content blocks inserted into both password blocks when using ajax. Creates duplicate insertions in the wrong locations
Screenshot: After refresh, we see the expected behavior. Each content block is inserted into the correct password location.
Also note that when you re-lock on a page where the sections were duplicated erroneously, the locked content block is correspondingly duplicated for each content block.
Right now, we're not differentiating between different instances of the same password, so the content of each unlocked instance gets dumped into the block of all instances.
This only happens when unlocking with ajax. On refreshing the page, the correct content is inserted into the password-protected blocks. So, a simple fix is to disable ajax with the ajax='false' attribute.
I am tracking each shortcode instance in the default template, but need to make the Ajax JavaScript smart enough to use them.
Screenshot: Locked state with two instances of same password.
Screenshot: Both content blocks inserted into both password blocks when using ajax. Creates duplicate insertions in the wrong locations
Screenshot: After refresh, we see the expected behavior. Each content block is inserted into the correct password location.