willemb2

Thanks, @frankremmy. In the meantime I found out that I could download a .ics via de ‘Subscribe’ button on the front end. With another 3rd party plugin, WP Event Aggregator I could import that. Worked very well. It’s a bit like shooting down a bug with a canon, but it saved me a few hours of copy/paste.

Thanks, @gugaalves. I added my vote.

Thanks @adegans, I will study the weight system and discuss internally if we’ll get Pro versions for this and the 2 sister sites.

@rizaardiyanto In just half a year, this is the 4th update causing major issues. This plugin was a lot more stable in the days it was still called “Post Expirator” and it did just that, reliably.

Hello @battouly,

Thank you for pointing me to that article. But our button already has a very short labe line: ‘Lees verder’ (= read on). It also looks like MailPoet is already trying to address Outlooks’ rendering issues because there are <!–[if mso]> tags all over in the emails source code (see below). But in this case it doesn’t result in the desired effect. If I try to compensate as the article suggests I get a silly wide button in other clients.

I know Outlook is a lousy email renderer. But around 30% of our readers is using it.

<td class="mailpoet_button-container" style="border-collapse:collapse;text-align:right"><!--[if mso]>
                  <v:roundrect xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word"
                    
                    style="height:36px;
                           width:130px;
                           v-text-anchor:middle;"
                    arcsize="14%"
                    strokeweight="0px"
                    strokecolor="#0074a2"
                    fillcolor="#1b1498">
                  <w:anchorlock/>
                  <center style="color:#ffffff;
                    font-family:Verdana;
                    font-size:16px;
                    font-weight:bold;">Lees verder
                  </center>
                  </v:roundrect>
                  <![endif]-->
                  <!--[if !mso]><!-- -->
                  <a class="mailpoet_button"  style="color:#ffffff;text-decoration:none;display:inline-block;-webkit-text-size-adjust:none;mso-hide:all;text-align:center;background-color:#1b1498;border-color:#0074a2;border-width:0px;border-radius:5px;border-style:solid;width:130px;line-height:36px;font-family:Verdana, Geneva, sans-serif;font-size:16px;font-weight:normal"> Lees verder</a>
                  <!--<![endif]-->
                </td>

Thanks for your explanation, @lynnjat7 , I understand.

Perhaps your sponsor logos would work as a nice header or footer area, before the posts area?

We have 33 sponsors…

@barsha04 Should this have been fixed by now? I just updated my Dutch language site from 2.1.8 to 3.0.7 and my button text changed to “Read more”

@photoweblog well, glad to see you back online, MiKa! We were afraid you had left this planet.

Thanks, @danieliser that works. In a split-second we got:

User meta migrated
Upgrades complete with errors.

Same issue here. Using Content Control to make some menu items only visible to specific roles and that still works.

WP 6.3.1 , PHP 8.1.23 , 10.4.30-MariaDB-cll-lve.

• This reply was modified 1 year, 6 months ago by willemb2.

Thanks! I will install and try it out next weekend.

Amazing. While I was still gathering courage to try what @caseproof suggested above, Bing apparently decided to stop showing the contents from the og:description property in their search results. They still show the title, which can be found in other metadata as well, not only og:title. And they show the author, like Google does.

In the meantime I learned that og: comes from Open Graph, a protocol developed bij Facebook. I found a setting in our Avada theme to disable that. I don’t trust anything from Meta.

We’re currently looking at plugins that will add something like
meta name="robots" content="noindex,nofollow"
to restricted posts.

We do not want to stop the crawlers in general. We’ve used Yoast in the past to prevent crawling of individual pages, but that was unreliable.

When I access a restricted post when not logged in and look at the source I find the content that the Bing crawler is using in <meta property="og:title" and <meta property="og:description". Wouldn’t it be possible to suppress those tags for resctricted posts and pages?

We had the same error. After going to WP Dashboard > Events > Settings and clicking the green Save settings button at the bottom (without changing any setting) it went away.

Apparently this resets something. Version 3.0.0 on WP 6.2.2 PHP 7.4

No response from the developer and it has not been officially tested since WP 5.8.6 ?? But it still works for us on WP 6.1.1.