ambrosite

It is extremely unlikely that the plugin would stop working entirely, unless WordPress made substantial changes to the database schema that would break thousands of plugins. It doesn’t really need to be updated, however I probably will issue a minor update at some point just to make a few small tweaks and get it relisted in the plugin directory.

The plugin display posts in reverse chronological order when sorting on date, and ascending alphanumeric order for everything else. If you want to reverse that, you can negate the conditional on line 283. In other words, change this:

if ( ($previous && $r['order_by'] != 'post_date') || (!$previous && $r['order_by'] == 'post_date') )

to this:

if ( ! (($previous && $r['order_by'] != 'post_date') || (!$previous && $r['order_by'] == 'post_date')) )

• This reply was modified 8 years, 6 months ago by ambrosite.

Of course nothing happened. The installation instructions clearly state that you must edit your template files in order to complete the setup. If you need help editing the templates, you should either ask the developer of whatever theme you are using, or try posting your question on the “Themes and Templates” section of the www.ads-software.com support forum.

https://www.ads-software.com/support/forum/themes-and-templates

A good suggestion. For years there has never been any technical reason to update the plugin, however that may change if core ever gets around to refactoring the taxonomy tables like they have been talking about in the dev blog. If I do release an updated version I will implement your fix.

I can confirm that barnez’s code does work. Thank you, this plugin is getting more and more annoying all the time.

Or you could just swap the two functions; that is, use next_post_link_plus in place of previous_post_link_plus, and vice versa.

Thanks for sharing your solution. That is certainly an interesting usage of the plugin; I’ve never seen it used quite that way before, but I figured people would be able to do all sorts of cool stuff with the ‘return’ parameter.

This was their reply:

“If they have already been working with our Tech Ops team, it would be best to let them continue through that route. It would not be wise to continue adding contacts for them to speak with as all requests of this nature would go to our Tech Ops team anyway.

“Realistically, we could determine that the plugin is fine to use again at a later point. But at this current point in time, Tech Ops has already blacklisted the plugin. We are not able to do anything about this for you.”

Thanks for the reply. We are paying for a dedicated server, so we should be able to get some kind of response from them. I’ll tell them what you said and let you know.

Your code should work; you were only missing a closing parenthesis. But I think you figured that out already.

Brady,

Thank you, I’ll give that a try. In the meantime you might want to check out this plugin:

https://www.ads-software.com/plugins/b09-link-to-existing-content/

It does something similar to yours, except that they are deregistering wplink.js and replacing it with their own modified version. I realize it is a radical solution to replace an entire core file just to fix one line, but if they aren’t going to put your patch into the core it might be the only solution. I really need to get this working so I may end up doing it myself.

If that patch were to be added to the core (and let’s hope that it is), what would need to be added/changed in your plugin code in order to make it work with the new event?

That’s a good fix. I might add it to the next version of the plugin, if I ever get around to releasing it.

There is a better way to patch WPML now; please read this post:

https://www.ads-software.com/support/topic/plugin-ambrosite-nextprevious-post-link-plus-wpml-patch?replies=22#post-4632708

You’re using the Virtue theme, right? I see what the problem is — the theme author copied the entire code of my plugin and pasted it into one of his theme files. He really shouldn’t have done it that way, but the bottom line is, you don’t need to install my plugin at all, since it is already baked into your theme. You can just use the functions as explained in my documentation.