OpenDNA

@rencosch Try putting the URL of a post into the search field of your Mastodon client. (They show up for me.) You can then Boost them.

Not what you’re looking for, but it’ll put them in your local’s timeline.

@rencosch Webfinger is fine and I see 3 followers (I believe I’m one of them). Try publishing something. IIRC that helped.

Well, that seems reasonable.

Turns out it wasn’t the only extension I forgot to update. ??

The author of that post is mistaken: the plugin is irrelevant.

He’s using the WP-default “embed” method for Blocks. The reason it looks okay is that he’s filled the hard-coded height with an image (the window would be the same height without the image.) Also see: My write-up of the WordPress x Mastodon embed issue.

Enable the plugin and WebFinger (user)@(domain).(tld)

The user is the WP author username which resolves https://(domain).(tld)/Authors/(user)

@gridman @simonwood Check your blogs’ followers now. I’ve followed both (or so my Mastodon says). If you cancel your follow requests and try again, it may work now.

Sorry. @pfefferle, I’m sure that’s not helpful to squashing the glitch.

I think it’s a caching issue with Mastodon, CloudFlare, or etc. I suggest this because:

1. I get different results when using the same Mastodon account to follow different WordPress authors (in the same time period).
2. I get different results when following the same WordPress author using two different Mastodon servers (in the same time period).
3. The problem resolves itself if I leave it alone (t>2hrs?).
4. When it resolves on Mastodon (follow approved), it resolves on WordPress at the same time (follower listed in Admin).

I see that accounts which followed before a post was propagated see it, even it is unpublished, but accounts which followed after do not. I don’t know if that’s diagnostic (CloudFlare?) or not.

• This reply was modified 2 years ago by OpenDNA.

Here’s the stack trace for this error on YOAST SEO v.15.3.

PHP Fatal error: Uncaught Error: Call to a member function og_tag() on null in ${PATH}/wp-content/plugins/wp-multilang/includes/integrations/class-wpm-yoast-seo.php:311
Stack trace:
#0 ${PATH}/wp-includes/class-wp-hook.php(287): WPM\\Includes\\Integrations\\WPM_Yoast_Seo->add_alternate_opengraph_locale()
#1 ${PATH}/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
#2 ${PATH}/wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#3 ${PATH}/wp-includes/plugin.php(660): do_action_ref_array(‘wpseo_opengraph’, Array)
#4 ${PATH}/wp-content/plugins/wordpress-seo/src/integrations/front-end/backwards-compatibility.php(61): do_action_deprecated(‘wpseo_opengraph’, Array, ‘14.0’, ‘wpseo_frontend_…’)
#5 ${PATH}/wp-includes/class-wp-hook.php(287): Yoast\\WP\\SEO\\Integrations\\Front_End\\Backwards_Compatibility->call_wpseo_opengraph(”)\n#6 ${PATH}/wp-includes/ in ${PATH}/wp-content/plugins/wp-multilang/includes/integrations/class-wpm-yoast-seo.php on line 311

I think the CopperMine plugin got fugged with the 1.5 upgrade. Any time I tried it it broked WP. (the geo plugin did the same thing with the upgrade)

Your CSS doesn’t contain a definition for how to treat comment paragraphs. You have


.entrybody p { margin-top:0.8em; margin-bottom:1.6em; }

and

.commenttext { clear: both; padding-top: 0px; margin-top: 0px; margin-bottom: 3em; border-top: 1px solid #ebebeb; line-height:1.2em; color: #5b5b5b; }

but no .commenttext p {. Try this:

.commenttext p { margin-top:0.8em; margin-bottom:1.6em; }


rwatkins: You da man. Thank you.

I don’t want to use br but that’s what WordPress is using for line breaks within entries. Until I can change this, margins do me no good because they can only be used on paragraphs.

The question is: How do I get WP to use paragraphs instead of line breaks in .entries? Would changing to another editor plugin help? Suggestions?

Ok, rookie mistake: the problem wasn’t shieldhost.com, it was the installation of an unconfigured plugin. (coppermine)

Are you using shieldhost.com? The same thing has happened to me twice now. I re-installed and it came back. Today: *poof!* It’s broke again. =^(

Davestinner: yep. Something like digg.com would work fine.

Scoop (e.g. dailykos.com and kuro5hin.org) has a “promote from diaries” function but I don’t need it to be within a multiblog: Just “promote from category”.

Root: I’m still out of the loop.