PaulIsLoud

I’d of been happy to but I just logged in to Algolia again to grab my API keys for some tests with the node client, and noticed that the _tmp on the index has done away, and now only the primary wp_searchable_posts index exists.

On a side note, we want to give certain post types priority in our ranking, and unfortunately it doesn’t happen to be the case that alphabetical ranking (either asc or desc) would be the sort order we want, so we have to look for alternatives to this approach.

We’re thinking of using the node client to basically:

* pull the records in the index
* add an attribute to each record (i.e. post_type_priority)
* establish a priority for each post type (i.e. ‘photos’ would be priority 1, ‘videos’ priority 2)
* add this attribute as an attributeToIndex, and to customRanking, sorting either asc or desc

It’s a lot of reading and writing, and we’d have to rerun the whole thing every time we publish a post, to get the additional meta data added to the new posts’ index record in algolia.

Seems to me a better option would be a type of sort like so

customRanking: [
{ ‘literal(post_type)’: [‘photos’, ‘videos’]}
]

or something similar – I think you get the idea. Basically, give me more than just asc and desc, so I can provide a defined sort order for a non-numerical field.

Would be super helpful, and save me a lot of code and your servers a lot of reading / writing.

Hi Ray,

I’ve been getting this as well. We are not using any WordPress caching plugin, though are doing basic nginx fastcgi cache. Cleared that cache, still getting this.

Any luck tracking it down?

Hi @reedyseth,

I’m having the same issue, subscribe_reloaded_show() is still not an available function.

Any progress / ETA on this?

Anyone have a thought on this? We’re getting complaints from users on not being able to subscribe to comments on our posts.

Things are working perfectly! Yep, it was the rewrite: false issue.

Michael thanks so much –?I tried your suggestion and it worked perfectly, finally resolving the issues that were keeping us from being able to upgrade.

May be helpful to add this suggestion to your list here: https://www.ads-software.com/support/topic/ugraded-version-10x-checklist

Thanks again!

Correct, “gone” means still in the database / admin, but not available on the front end.

Sure, reinstalling 0.9.5 is easy enough, but so is a restore. May end up doing that as push comes to shove. Anywho…

Re: access, this is a client site, and so would need to request permission to let you in, and would prefer avoiding if possible.

Given the above, any thoughts on what might be going on?

This is exatly the experience I had. Enabled plugin, comments gone. Disabled, comments back.

yep, checked there, but unfortunately the screen options only control the ‘body’ of the admin interface, and not the left nav. thanks for your input though.

Just got a notice from WordPress Firewall regarding activation of the plugin. There appears to be a conflict. If you disable the WordPress Firewall, enable this plugin, and reenable the Slick Social plugin, all is well with the world.