hommealone

Thanks Henning! You wrote:

An ad?… that is directly assigned to a widget would not have an edit button.

That explains it! We place our ads using a widget.

And since we don’t need it, adding the constant you referenced

define( 'ADVANCED_ADS_DISABLE_EDIT_BAR', true );

did indeed remove the code block, as you suggested. Thanks!

For everyone else (who does want to have the edit bar/icon), stripping the added code down to a partly minified version would be nice. Something like:

<style>div.advads-edit-bar{position:absolute;height:0;display:none;z-index:10000;animation:advads-edit-appear 2s linear 1;} @keyframes advads-edit-appear { 0% {opacity: 0.0;pointer-events: none;} 66% {opacity: 0.0;} 100% {opacity: 1.0;} } a.advads-edit-button{position:absolute;top:0;left:0;text-decoration:none!important;box-shadow:none;border-bottom:none;color:#0074a2;margin-top:-5px;} a.advads-edit-button span{top:10px;line-height:25px;margin-left:-5px;width:26px;height:26px;border-radius:13px;border:solid 1px #0074a2;background:#fff} div[class^="asbpe-"]:hover > div.advads-edit-bar {display: inline-block; vertical-align: top;}</style>

Just thought you might want to consider that for a future update.

Nice touch, on your part, for already adding that code at the end of the head!

Thanks again for your help and great plugin!!

@henningaa – While I did manage to get rid of the Ad Health item in the admin bar (thanks for the instructions!), there is still a block of CSS code in the head which I am curious about:

<style>
				div.advads-edit-bar{position:absolute;height:0;display:none;z-index:10000;animation:advads-edit-appear 2s linear 1;}
				@keyframes advads-edit-appear {
					0% {opacity: 0.0;pointer-events: none;}
					66% {opacity: 0.0;}
					100% {opacity: 1.0;}
				}
				a.advads-edit-button{position:absolute;top:0;left:0;text-decoration:none !important;box-shadow:none;border-bottom:none;color:#0074a2;margin-top:-5px;}
				a.advads-edit-button span{top:10px;line-height:25px;margin-left:-5px;width:26px;height:26px;border-radius:13px;border:solid 1px #0074a2;background:#fff}
				div[class^="asbpe-"]:hover > div.advads-edit-bar {display: inline-block; vertical-align: top;}				</style>

What does this do, and is it always necessary?

I’ve searched the pages, even after javascript execution, for div.advads-edit-bar but I can’t find it. Is it always there, and I’m just missing it? If we do not have that div, or any of the other items referenced in the CSS, why do we need to have that code there at all?

If it is really not needed in our site, then I’d like to know how to remove it. If it really is necessary, is there any chance it could be minified?

Thanks again for this plugin, and your responses. I’m a little obsessive about keeping my code as clean and simple as I can, so your reply will be helpful!

@spacetime – My apologies. I was getting the two plugins (Advanced Ads and Ad Inserter) mixed up. Thanks for jumping into this thread (about Advanced Ads; I think that’s what threw me off!) with that info on Ad Inserter. I have it sorted out now.

I’m really sorry, but… I went to the plugin settings page, and I can’t find a gear icon anywhere:

Good to know, thanks. Where do I find the screen for that setting? What’s the URL of the screen, or route from the admin menu? Sorry… but I can’t find it.

I am not using Ad Inserter Pro, just the free version. There is no “Debugging” tab in the settings.

That works – thanks so much. A nice improvement, in my opinion.

Nice use of the “wp_add_inline_style” function. I did not know that this function existed before now.

Thanks so much for your willingness to address this. Much appreciated!

Hi @henningaa – thanks for your reply.

I had already used that setting to remove the Ad Health item from the admin bar.

I’m looking for a way to remove the “Ad Inserter” item from the admin bar, and the related CSS code in the head. Is that possible? I could not find a setting to do that. Perhaps some kind of function hook?

Thanks for your quick reply (and for making this great plugin available!) OK, I see why you would want to include the styles as inline in the head of the document.

Here is my thinking: I hate seeing that block of code as the almost-first thing in the head. No offense meant to you of course, but there are much more important things which need to come first.

As a suggestion (and I’m sure you may have other considerations that I’m not aware of!) I’d suggest that you do two things: first, use PHP in the class-sassy-social-share-public.php file to minify the code before it is added into the head. There are several good and small php minify-css functions available to do that. ( Just search “how to minify css code using php” ) Second, insert that css last in the head, instead of first.

With those suggestions in place, I would not need to do anything myself. But until then…

My plan was to remove that code; minify it; and add it to another stylesheet that loads later. The styles (settings in the plugin options) will not change often on this site, if at all. If I ever do need to change them, I can disable my code to remove the code from the head, see the new styles and copy them, and then re-remove them.

I’d be very happy to not do that if your code was minified and came at the end of the head. If not, I’d like to know how to remove it myself.

Thanks again!

Duplicator is a great and reliable plugin, offered for free for a very long time. (Thank you, Duplicator team!) It is understandable that they would like to have more communication with their users, especially the free users.

But I totally agree: the weekly emails should be an “opt-in” feature, not the default for everyone.

Yes, some people use it for daily backup and create packages on a schedule. They would definitely benefit from the emails. But lots (millions?) of users like me probably make backups only infrequently. Why tell those users that nothing has happened (every week!)

If you don’t make backups on a schedule; if you manually create all packages, then summary emails are of no use, right? Perhaps the plugin could be smart enough to email you only if it was used. Otherwise, then definitely my vote is also to the make the emails opt-in.

• This reply was modified 1 year, 1 month ago by hommealone. Reason: typo

WPEngine customers can get Turnstile keys by signing up for a free Cloudflare account. Once you are signed up, do not add your domain to the account; WPEngine will continue to use its Advanced Network (Cloudflare) as the CDN without conflict that way. Rather, in the account dashboard menu, find Turnstile and follow the steps. You will need to enter your domain into that, which is OK. Just don’t add it under “Websites”.

(You can, if you want use both your own Cloudflare account plus the WPEngine Advanced Network, but that’s a bit complicated to set up. See the WPEngine documentation on that.)

Thanks for the reply and the link to the Cloudflare forum. I’ve suggested the idea there:

https://community.cloudflare.com/t/turnstile-and-wpengine/544855

Well, I’ve come up with a better combination. I found the Disable User Login plugin and am using that instead. It plays nicely with WPS Hide Login, and seems to be more actively updated and supported at this point than the Lock User Account plugin.

https://www.ads-software.com/plugins/disable-user-login/

Answered my own question: yes, they are compatible, and work together nicely.

Thanks for making this very nice plugin available in the WP repository. Works great.

The author of WPS Hide Login wrote:

If [the Lock User Account plugin] redirects to wp-login.php especially, it won’t be compatible with WPS Hide Login. Try to contact [the Lock User Account plugin] support to fix that or to transmit a filter to us to make WPS Hide Login compatible.

https://www.ads-software.com/support/topic/compatibility-with-lock-user-account-plugin

I’m afraid I don’t understand exactly what they are asking for. I’ve asked for clarification and will let you know if they say more.