majelbstoat

In fact, if you turn off the cross-linking option, future cross-posted posts will not have the “Also published on Medium” link. In this case, because this is a reciprocal link, the link to the original post (“Originally published on original.com”) will not be added to the bottom of the Medium post.

The cross-link option can be set by default on your user profile page, and on a post by post basis on the editor screen.

There is currently no great way to do this, sorry. You can directly modify the “medium_post” post meta associated with your wordpress post, but there is currently no UI to do that. We will see about supporting this in a future version. Sorry for the hassle, and thanks for the report.

This is unexpected, and we’ll work on fixing it, thanks!

Jamie.

Hey wrgmag,

In the meantime, if you’d like to disable the also published on Medium link, you can comment out the call to the “the_content” filter on line 19 of lib/medium-site.php.

Jamie.

Hey, thanks very much for the feedback. The import on site, and import through API are somewhat different – the import on site parses the entire HTML at the URL as rendered by WordPress, whereas as the plugin just acts on post content. This leads to the differences you’re seeing.

Shortlink parsing is a bug. I’ll probably have to adjust the priority of the filter to make sure they’re included. (Though, I’m currently a bit confused why they’re not. Anyway, can be fixed, and thanks for the open issue on Github.)

Cross-link is intended to be “both” or “neither”. It being set to link to Medium but not the reverse is unintended, and a bug (which I can’t currently repro, but will keep trying). We set rel canonical back to your blog regardless of cross-linking, so Google will always know your site is the master.

It might be sufficiently complex to handle all the possible cases for all the possible themes that feature image insertion isn’t a good tradeoff, but I’ll do some research here too.

If you find anything else, please continue to raise them here: https://github.com/Medium/medium-wordpress-plugin/issues

Cheers,

Jamie.

Hi,

I’m the author of Gengo. If you can come to the forums on my site, I’ll try and help you get the problem sorted.

https://jamietalbot.com/wp-hacks/forum/

Cheers,

Jamie.

You could try X-Valid which corrects poorly marked up XHTML in posts and comments.

Just released version 0.91. It’s a minor revision, fixing a mistake in the allowed attributes of an INS tag (thanks to James from no2.org) as well as a bug that incorrectly wrapped whitespace in a UL or OL list.
You can find it along with installation instructions at
https://www.jamietalbot.com/wp-hacks/#P_xvalid
Cheers,
Jamie.

No probs Ben!
If anyone has any more problems, please let me know and I’ll do my best to get them fixed ASAP. If I don’t know, I can’t fix them!
Jamie.

Hi!
I just uploaded version 0.85 which includes automatic correction for comments posted to the site. If any problems cannot be fixed, the post author is emailed with a list of the problems and a link to edit the comment manually.
The email itself is rudimentary and will be cleaned up in future versions, but for now should suffice.
If there are any problems please let me know. Thanks.
You can find the updated plugin at:
https://www.jamietalbot.com/wp-hacks/
Cheers!
Jamie.

That’s the next aim ?? Hope to release a version that will do this soon. Shouldn’t be too much trouble I don’t think, just adding a hook to the right place. Will try and get it out soon. Thanks for checking it out!
Jamie.
PS: Incidentally, one user reports some problems with href attributes, though hasn’t provided any details yet. Has anyone seen what they think is a problem with this? Thanks in advance…

No probs, glad you found it useful! Let me know any problems if you find them…
J.

Damn, I mean the < !– more — > tag (no spaces) Can never post code here properly! ??

Have you tried using the <xmp><!–more–> tag? Putting that in your article should display only the text up to that point, along with a link to display the entire text if I remember rightly (don’t use them myself)
HTH,
Jamie.

I probably should have mentioned explicitly that you should disable WP’s own balancing, if it is currently active…