thesinglegourmet

Hi Shea, thanks for your answer!

OK, so if I have the Pro version, it is more efficient and pages load faster if I use CSS Snippets (as opposed to a PHP snippet with CSS inside of it).

If there are say, 100 lines of CSS, can you estimate what the performance hit/improvement is of one method versus the other?

The two plugins with which this is happening with me are

• Post Snippets (free) https://postsnippets.com (also available in the WordPress plugin repository)
• Code Snippets Pro https://codesnippets.pro (it also happens with the free version, available in the WordPress plugin repository)

These URLs were trivially easy to look up.

Steps to reproduce (this should take you no more than 10 minutes):

1. Set up website with Astra theme, and the following plugins: Spectra and Post Snippets (or Code Snippets).
2. Create an HTML snippet that uses <p> or <br> tags. Make a note of the shortcode.
3. Create FAQ using the FAQ block provided by Spectra.
4. In one of the “answers”, enter this text: lorem ipsum [shortcode] dolor sit amet.
5. View page with FAQ

Hi @karlemilnikka, thanks for your suggestion. The same thought occurred to me, and I tried it using <br> tags, with similar results.

@beautyofcode

Thanks for your response. However…

According to the page you linked, if the “Enable the legacy REST API” box is checked, then the new extension is needed.

According to @babylon1999 in this very post: “If you don’t have any API keys generated in WooCommerce → Settings → Features → Legacy API, then no, you’re not using the Legacy API”

So if the “Enable the legacy REST API” box is checked (and the Legacy REST API is enabled), but there are no API keys (and the Legacy REST API is not being used)… is the new extension necessary?

If you don’t have any API keys generated in WooCommerce → Settings → Features → Legacy API, then no, you’re not using the Legacy API

@babylon1999

I couldn’t find a “Features” tab on the Woocommerce settings page; I think you meant WooCommerce → Settings → Advanced → Legacy API.

Second, while it is a logical conclusion that if one sees a key there, then the website is using the Legacy REST API, it is not obvious to a non-programmer that the absence of any keys means that the Legacy REST API is not in use.

Currently, this page: https://developer.woo.com/2023/10/03/the-legacy-rest-api-will-move-to-a-dedicated-extension-in-woocommerce-9-0/ plainly states

If any of these [conditions above] applies to you, your site will need to have the new extension installed.

and condition number 1 is

You have the Legacy REST API enabled in your WooCommerce install. … The “Enable the legacy REST API” box below being checked means that the Legacy REST API is enabled.”

without mentioning anything about API keys.

I think you can see how a non-programmer would interpret that page to mean “If the Enable the Legacy REST API box is checked, then you need the new extension.”

It would be much clearer (and more accurate) if that page included a statement that is something like “If you do not see any API keys generated in WooCommerce → Settings → Advanced → Legacy API, then you are not using the Legacy API, and when you upgrade to Woocommerce 9.0, you will not have to install the new extension.”

• This reply was modified 11 months, 3 weeks ago by thesinglegourmet. Reason: typos
• This reply was modified 11 months, 3 weeks ago by thesinglegourmet.

After further testing, I have found that this happens to me only when the Mailer Type is set to PHPMailer, which I had to do because of a conflict with Code Snippets Pro 3.6.1, which has been resolved with v 3.6.2.

So I no longer have this problem, but people who set the Mailer Type is set to PHPMailer might still.

The developers of Code Snippets Pro have released v 3.6.2 which fixes this issue.

More information on this bug: it happens to me only when Mailer Type is set to PHPMailer, and it happens even if I go to Settings > Advanced and check the “Broken Email Fix” box.

Clearing the cache in my browser solved the problem. Thanks!

Hi, sorry I forgot to mention that I already did that.

I solved this problem by deleting the /wp-content/plugins/post-smtp/ folder and reinstalling from WordPress “add plugins” screen

This was solved when I deleted the /wp-content/plugins/post-smtp/ folder and reinstalled v 2.7.3 from WordPress “add plugins” screen

Marking as resolved

• This reply was modified 1 year ago by thesinglegourmet.

This banner still appears when I go to /wp-admin/admin.php?page=postman, even after dismissing it several times.

Not as annoying as when it was appearing everywhere in the admin pages, but still not ideal.

• This reply was modified 1 year ago by thesinglegourmet.

Hello, I have this same problem. The banner appears at the top of every page that starts with thesinglegourmet.net/wp-admin/ and it is very annoying.

I downloaded the zip file referenced by @furqanfazal, and that turned out to be version 2.7.1 of the plugin, which still had the problem, and caused WordPress to tell me that the plugin needed to be updated. I used the “update now” link and it updated to 2.7.2, and I am still getting the banner.

I have also closed the notice from the Post SMTP dashboard and the notice still appears on every page.

I hope to have a fix for this soon.

Thanks.

• This reply was modified 1 year ago by thesinglegourmet.
• This reply was modified 1 year ago by thesinglegourmet.

This code achieved my goal:

.tribe-block.tribe-block__events-link {
justify-content: center;
padding-top: 0!important;
}

.single-tribe_events .tribe-events-c-subscribe-dropdown {
margin-top: 0!important;
}

Both the margin and the padding have to be set to zero.