Hi @paul2,
I’m afraid it is not a plugin issue. We’re not able to replicate the bugs as in your app, because this implies a certain implementation of this plugin with state/actions/events which we are not aware of, unfortunately. It is something only your developer knows so far.
However, we have managed to almost replicate what you’re trying to accomplish with this plugin, and we had some success on our side. I can showcase it with a couple of screenshots.
Editor
A single ZQRTE element and a RG group:
The RG is pulling some testing data from database:
It contains items with simple text elements that retrieve the HTML (not that important as it’s set just for testing purposes):
Although we do not know how exactly your developer has set the Content field, so it’s just blank (but it should be based on the Parent’s group data where the plugin element is placed):
However, when the RG item is being clicked, it is using the following workflow:
Where you set the HTML of the current item that was clicked. The next step is setting a state of type text, but its value would be based on that current item’s HTML:
And the actual event that triggers when Content text is being changed:
Preview
First item clicked (ignore the actual HTML tags for the RG elements, as previously mentioned it’s just for testing purposes):
Changed text for the first item:
Second item clicked:
Changed text for second item as well:
Now, back to first one:
And back to second one as well:
As you can see, it keeps the appropriate cell data, meaning it should be an implementation issue rather than plugin related.
Without knowing more about how it’s done on your side, whether sharing access to your app or building a separate testing page, I’m afraid there is nothing more we can help with.
Thank you for understanding.