Scott DeLuzio

I’m seeing the ads come through with no problem on my end. See this screenshot of this post.

I have noticed that sometimes the AdSense ads do not show for a few minutes after they were created. You may also need to clear your browser cache if you are still not seeing them.

Can you post a link to a post where the ad is hidden?

This plugin only looks at the products in the customer’s cart to determine whether or not a field should be displayed. There might be a way to do that, but it goes beyond the scope of this plugin.

This plugin is designed to collect input from the customer, so I don’t think it would be possible to do what you are looking for through this plugin at this time.

There is a pro version of this plugin that will allow you to use multiple product IDs as you are describing. You can get it by visiting: https://surpriseazwebservices.com/plugins/conditional-woo-checkout-field-pro/

Please visit the support forum for the pro version of this plugin.

Please visit the support forum for the pro version of this plugin.

Please visit the support forum for the pro version of this plugin.

Please visit the support forum for the pro version of this plugin.

Marking this as resolved, as this is a duplicate of this post: https://www.ads-software.com/support/topic/how-can-i-get-the-ads-to-align-left-or-right-with-text-wrap?replies=7

There are a number of reasons you might get a 403 Forbidden Error. That error occurs when your browser makes a request to the server, but the server refuses to display the page you requested. This could mean that you do not have permission to view the requested page, which may indicate that there is a configuration that needs to be changed on your site’s server.

Here are a few troubleshooting steps:

Before making any changes to your site’s files I would recommend making a backup so you at least have a point you can fall back to if something goes wrong.

Update All Plugins, Themes, and WordPress
Make sure you are running the latest versions of all plugins, themes, and WordPress core files. If you need help updating, take a look at this article.

Rule Out Other Plugins and Themes
Deactivate all other plugins, and revert to the default (TwentyFifteen) theme, then try again. If you don’t get the 403 error, try re-activating plugins and themes one by one and re-trying the steps you used to get the error in the first place until the error comes back. The last plugin you reactivated may have been the cause of the problem.

Replace Core WordPress Files
Follow the steps here to replace the existing WordPress files on your server. Your site may have a problem with one of the core files. Deleting the wp-admin, wp-includes directories, and any other loose files and replacing them with a fresh copy will eliminate any problems with the files on your site if there is one.

Check File Permissions
Directories, and files can have different permissions. If they are configured improperly you may end up not having access to the page you are attempting to view. Check the WordPress Codex for Changing File Permissions to use as a guide. Your host may also have modified permissions for some directories or files, so you may need to check with them for help.If you are unfamiliar with changing file permissions, you can use this guide for help. Your host may have other methods for accessing files other than cPanel, so check with them if these steps don’t help.

Check Your Site’s .htaccess File
There might be a rule in there that is causing you to receive this error. A basic .htaccess file would have code like what is found on this page, although some plugins add their own rules to this file so yours may look different. You can start by replacing what yours has with what was found on that page to see if it helps.

Ask Your Host
Your hosting account may have rules set up such as mod_security, which could cause this error.

The <!-- and --> code is the start and end of an HTML comment – anything in between those will not display to the visitor, but will show up in the code. It’s commonly used to insert some reminders such as the 336×280 Large Rectangle in your ad code.

As for the display:inline-block, I wasn’t sure what wasn’t displaying correctly for you – whether the ad wasn’t aligning correctly, or at all. Since the ad code specifies a different display, I thought I’d point that out, but it doesn’t seem like that was the problem anyway, so it probably doesn’t matter.

Glad you have it working now.

Could you explain what has stopped working? Are the ads not displaying at all? Is the ad not aligning correctly? Could you provide a link to your site where it isn’t working correctly, and explain what part isn’t correct?

The code you provided, is that a direct copy from one of your posts? If so, the <!-- and --> are probably causing the ad to stop displaying.

My original suggestion, which should still work, was to put the <div> with the styles around the ad code on the plugin’s setting screen. That way you could still just use [AdSense-A] (or B or C) in your post without having to worry about formats.

For example, in Settings > AdSense In-Post, you could put your ad code in one of the boxes like this:

<div style="float: left; margin:10px;">
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<ins class="adsbygoogle"
     style="display:inline-block;width:336px;height:280px"
     data-ad-client="ca-pub-1234567812345678"
     data-ad-slot="1234567890"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
</div>

In your blog posts you would just use the shortcode without the need for adding a <div> around it each time. If you ever need to edit the <div> style, you would only have to make the change once in the plugin’s settings.

You might also want to pay attention to any styles provided by the ad itself. See in the example above the style line in the ad code includes display:inline-block;. In your example it looks like you are trying to use display:block;. There may be a conflict with the styles used there as well.

I had the same problem. The donate box is on top of the delete button so you can’t see it. Try right clicking the donate box and inspect element in your browser.
Add the following style to the page:
.spacker-donate { display: none; }
This should hide the yellow donate box temporarily so you can see the delete buttons. Remove whatever you need to before reloading the page, which will bring the donate box back in view.

I know this isn’t a great fix, but hopefully the developer can move the donate box to either the top or bottom of the page so it doesn’t interfere with the operation of the plugin.

Under the Current Features section in the plugin description it says recurring payments is supported with the Pro version https://gravityplus.pro/gravity-forms-stripe