bigspud
Forum Replies Created
-
Hi
Thanks for your reply. I have found a sort-of workaround for now.
If you embed the ###POSTLINK-ONLY### field immediately followed by the tracking code most email programs will see it as a single link.
The downsides are not all email programs behave the same and leave it out of the link, and obviously your content cannot be dynamic but it’ll have to do for now.
Thanks
Gary
Forum: Plugins
In reply to: [WP Ultimate Recipe] Standalone recipesHi Brecht
Apologies for the slow reply, I’ve been working through the options with posts old and new. Thanks for the advice, that worked just fine. It was a little confusing on the FAQ page which is why I didn’t follow it initially (it said to do the action, but not why).
paulalexandru, thanks for your feedback. It’s always useful to hear from other people’s experiences of a plugin that isn’t involved with the development. I appreciate your comments, however my related posts plugin works just fine as it supports custom posts (https://ww.wp.xz.cn/plugins/yet-another-related-posts-plugin/). I had been using it before WP Ultimate Recipe and continue to do so. So no issues from me here on that front.
Gary
Forum: Plugins
In reply to: [WP Ultimate Recipe] Standalone recipesHi
Thanks for the speedy answer. I did read that last night but I’m concerned about /recipe/ slug in the URL. Either I have to change 600+ posts or create a 301 redirect for every post.
I converted one post to a recipe using the method described:
http://bigspud.co.uk/recipes/curried-lamb-breast-with-onions/
Which I can also access via
http://bigspud.co.uk/curried-lamb-breast-with-onions/
But the canonical points to the /recipe/ version (I haven’t actually put all the recipe details into the right format yet).
What’s the next step from here? Should I set up 301s? Should I leave it alone? I have a lot of historic link equity I’d like to preserve.
Gary