mpmchugh

I don’t see that anywhere as a permission in Members. It seems it might not be accessible in a Multisite install. Is there anyway around this? I’m just trying to let an SEO person edit Headers and Footer scripts some how without making them a full admin.

At the very least it’d be nice if a user could create/submit scripts but maybe not activate them.

• This reply was modified 3 years, 2 months ago by mpmchugh.

Actually, I discovered that it’s an incompatibility with the Login with Google plugin which we were using for access to certain pages. It was forcing users to the Admin dashboard after login. I let them know about it, but they also have a function to handle a single redirect, which is all we needed for the time being on this.

I managed to get this to work by placing this button and script as part of the confirmation message itself.

<a class="close et_pb_contact_submit et_pb_button" href="javascript:void(0);">CLOSE</a>

<script>
jQuery(document).on('click', '.popup a.close', function() {
DiviArea.hide();
return true;
});
</script>

The script would not work from the head of the page, oddly.

Sorry, but what do you mean by “make a PR with solution”? Not clear with “PR” refers to here.

Hi Kevin,
Thanks for the reply. I’ll certainly reach out to Elegant Themes, the Divi developers, but it seems Lazy Load for Videos is doing something very low level that would be difficult for them to work around. And then it would have to be dealt with individually by all the the other page builders as well—Elementor, WP Bakery, etc.

I suggested the “by enclosing class” possibility, as there are other similar plugins that have such an option. Lazy Load for Videos seems to be the best at what it does, so I was just making the suggestion to improve it’s compatibility for more users.

It also might be worth considering making your plugin optionally use its own shortcode-—e.g. [lazy-video src=””] or something like that—-to only lazy load videos using the Lazy Load for Videos shortcode.

This would allow much wider compatibility, as it optionally wouldn’t be globally applied, and the user could use it as needed. i.e. people using page builders could just use the shortcode on their blog posts and none builder-built pages, for instance.

Another option to consider is a per page/post control that enables or disables Lazy Load for Videos for that page or post. A lot of caching plugins have options to disable their features on a per-page/post basis.

Either of these would make Lazy Load for Videos a lot more compatible with people’s specific site setups, themes and other plugins.

Thanks,
Michael