ladler

Thank you

Any update on this? It would be great to have this editable w/o having to mess with the core files. I’m sure it’s not that difficult of a thing to implement.

I see, thanks. The update notifications are confusing because it brings you to an updates section of the plugin but you can’t really update the plugin and it’s not clear at all that you have to manually update the core plugin.

I modified one of my templates to use the following:

<a class="wpdm-download-link" href="[download_url]" target="_blank">Download</a> and I guess that is what broke it. Can you see any reason why that wouldn’t work properly?

IF i just use [download_link] then it works but I wanted to do it the above way for more finite control.

I don’t think that answered my question. You linked me to a newsletter plugin when I was inquiring about an Active Campaign integration.

Definitely would be useful to either add a hook OR allow us to change the copy with new settings for email lock. Thanks.

I’ll try to give access asap, thank you.

Understandable, but maybe other people haven’t mentioned it. There’s a first time for everything. And as per my original comment, I’m using 2 different themes, 2 different installs and experiencing the same issue, so maybe there is a plugin conflicting with yours that is installed on both, however a simple fix would simply be to adjust the modal properties to use explicit CSS rules.

You are right. I figured it out by embedding the appropriate tag, thank you.

Honestly if the plugin was coded with the proper use of ID’s for the CSS then there wouldn’t be any conflict what-so-ever. I’m a developer so I should know. I’m not trying to be rude, but it’s slightly ridiculous to imply that every single customer has to update their css file or give them fixes for their particular situations when the issue clearly lies in the plugin architecture itself. A simple edit to your css declarations would solve this issue on the plugin end. Trying to hunt down conflicts with my other plugins and then attempting to implement one-off fixes is a lesson in futility.

Regardless of if it will not cause functional issues, I paid for this plugin and no other plugins of the hundreds of I’ve owned operate like this. Your plugins should use specific overrides or better naming conventions to ensure that the CSS does not conflict with it. How would I get you temporary writes? I don’t want to put it publicly, obviously.