Hi Jens,

As mentioned in the other tickets, we’ve had some issues with this ticketing system and are in the process of transitioning to a new one. I’ll respond here as well as in the new chat system so we can stay connected on both ends if needed.

Regarding this issue:

• I’ve found the original ticket: https://tmsplugins.ticksy.com/ticket/3423278/.

Thank you for the reminder! I’ll follow up with our developers and do my best to advocate for prioritization.

When we initially confirmed this as a bug, we also mentioned that we couldn’t provide an ETA for a fix. Unfortunately, some issues take longer than expected, as priority decisions are managed by our development team based on overall impact.

In this case, the issue appears to be more of a compatibility conflict rather than a direct bug, though I understand that from your perspective, it’s still an important problem. Rest assured, our developers are aware of it and are working on a resolution.

We are just still not able to provide any kind of an ETA for this specific fix, I'm afraid, but you can keep following our ChangeLog and as soon as it's fixed, we will add a patch note about it there.

2. In regards to this question, to make the PopUp a modal :
Our Master Details PopUp is already a modal, so I am not sure what you meant by that part.
Could you please elaborate on it?

Thank you.

Hi Jens,

Oh, I see what you mean now—thank you for the clarification.

Yes, by default, our Master-Details popup modal has a gray, faded background that covers the rest of the page. When it loads, it focuses solely on the Master-Details section, and the user needs to close it before interacting with anything else on the page.

If I understood correctly, you’re suggesting an improvement—perhaps an option to modify how the popup behaves when clicked, or the ability to move it by clicking, holding, and dragging it to a different position on the screen?

That’s an interesting idea! You’re welcome to submit a detailed development suggestion, and of course, feel free to correct me if I misunderstood your request.

As you know, we can’t provide an ETA or guarantee that it will be implemented, but we’ll certainly consider it for future updates.

Hello again, Jens,

I wanted to follow up on the Theme conflict we discussed in the original ticket, where one of our developers provided a custom JS fix to resolve the issue with your theme.

After consulting with our management and QA team, I regret to inform you that we will not be treating this as a bug. The issue stems from a specific conflict with the GeneratePress theme, and the custom JS we provided has resolved it.

As you know, the custom JS will not be overwritten by our plugin updates, so there’s no need to repeat any steps on your end.

Our primary focus is on integrating our plugin with the major page builders and themes that most of our users rely on, such as WPBakery, Elementor, DIVI, Avada, Gutenberg. These are the themes and builders that receive priority for native integration and conflict fixes.

Another important factor is that whenever we release a fix for a specific theme, it must go through extensive testing by our QA team to ensure it doesn’t negatively affect other themes that our users may be using. This makes fixes like the one you’re asking for in this case complex and potentially risky, which is why we’re unable to implement a permanent solution for this conflict at this time.

I hope this clarifies our position. 
Thank you once again for your patience and understanding, as always.