wprocks34

Thanks again!

Excellent!

In the meantime, is that space before the close quote after rel=”noopener” a problem in any way?

Thanks!

Fine plugin. Two comments:
1. On the frontend, I see a space before the close quote after rel=”noopener”, ie, target=”_blank” rel=”noopener “>. What could cause that?
2. How can this work on pages as well as posts?

I am using a different plugin that allows the setup and functionality I want. The downside is that it has not been updated in two years. So we’ll see what the future brings. Thanks for responding!

The widget that is sticky is shown only on posts. See my previous email for details.

You can look at the sidebar of any post on https://bebrainfit.com. However, while trying to resolve this issue, I have moved the Amazon up the sidebar. Instead of being at the bottom of the sidebar, it is now in the middle (third widget from the top).

The widget that is sticky is still the one at the bottom but it is served by a third-party ad network. In this case, the widget is sticky but displays differently than when I have a banner ad in the widget that is served by my server. The ad is not seen until after you have scrolled completely past the widget above, then it pops in. After that, the ad/widget sticks as you scroll to the bottom of the page.

When serving my own ad in this widget, you could see the ad come into view as you scrolled, then it would stick as you continued to scroll down the page.

Thanks for responding and let me know if I can help.

Maybe, but I’ve already tried all the usual cache-clearing things.

I am using 3.1.3. Sorry, I had rebuilt the index using only posts to prevent problems.

I have done some more testing and it’s funny, the only time I can produce an error now is with one search term – “truth about abs” – which is a product. Searching on this term shows results that include a number of newsletter issues that are excluded pages. I’ve tried other product names, generic keywords, even the term “newsletter”, and excluded pages do not show.

I have rebuilt the index a few times since my original comment. Perhaps that helped. Otherwise, I don’t understand this aberration with the one search term. I’m not too concerned, but if you have any ideas on what might cause the issue, I’d like to know. Thanks.