spinksys

Just found this: https://github.com/cabrerahector/wordpress-popular-posts/wiki/8.-REST-API-Endpoints#v2viewspost_id-post

“Note that to send a POST request to this endpoint you must provide a valid nonce called '_wpnonce' either via the _wpnonce parameter or the X-WP-Nonce request header, otherwise the REST API will return an HTTP 401 Forbidden response.”

I’m probably not doing that, so that’s probably the problem.

Edit: Yes, that appears to be the problem. Now to figure out why.

• This reply was modified 11 months, 1 week ago by spinksys.

Thanks for the quick reply @hcabrera !

Did anything change with the API between /v1 and /v2 that might cause this? Or, let me explain. So we do have a firewall that blocks traffic, and our engineering team has created a mechanism for specific urls to get through (which they did for the /v1 API). When I notified them that the URL changed from /v1 to /v2, they updated this mechanism and the error changed from a blank error (I can’t recall specifically what it was) to the 401. When I reached back to them that it’s still not getting through they said the error is coming from the plugin itself, so I should reach out to you. But I have suspicions.

In theory do you think updating our firewall rules from /v1 to /v2 should be enough? I’ll reach out to our host next, but I thought I’d double-check with you first.

Thanks!

Thanks for looking at these – I agree that often the advice isn’t as black and white and the bot suggests.

Agreed, most are easily fixable. Thanks for taking a look!

I’ll see what I can do in my off time – hopefully you can take a look as well.

Thanks.

Hi Hector – thanks for the reply! Our hosting is through WordPress VIP, and these fixes are required for updating. Is the code open source? I’ve been making the fixes for the past few updates, I can easily make most of them and submit to you for review if you’d like.

Yes, I think so.

First of all, I don’t have a great (or good!) understanding of how the excerpts are generated. They are being pulled dynamically, right? When I search, autocomplete is changing the text in the excerpt. My assumption is that as I search for a term the excerpt is automagically created with the search term in it (to give the excerpt context).

While it would be super easy to use js/php to cut down the numbers of words displayed, I am concerned that I would lose that context. That’s why I assumed there was some easy way to programatically changed the default excerpt size.

And so, back to your answer. It seems like customizing the excerpt length before index seems like the best solution, but I’m not sure how to do that. Any thoughts on where I might look?

Thanks for all your help!

Sorry for the confusion!

For example, right now my search results look like this (this is a different site btw):

How to Quickly Customize Unsplash Pictures
… marketing hipsters, Shutterstock to every kind of marketer, designer, creator. It would be interesting to survey Unsplash users about the reasons why they use it: I expect most would just …

Posting Trends on Four Different Facebook Pages
… to get more in touch with their customers online. Therefore they often create prize competitions, surveys and DIY ideas. Beside that, IKEA occasionally provides you with background information about the …

Collect Analytics and user feedback with Hotjar
… Each survey is also reachable via a direct URL which you could link to. The survey component is maybe not as powerful as surveymonkey or typeform. But it’s powerful …

Startups at Uprise Festival 2015: Learn platforms, Tents out of cardboard, Spotify of Gaming and Tinder of Job search
… appointments, sending newsletters, a newsfeed, you can post files, chat with other group members, create surveys etc. The platform is targeting professional training institutes offering in-person trainings looking for …

So it goes linked title, then long excerpt for each returned post/page. I want the excerpt to be roughly half as big. Say, 30 words instead of 55 words. But I can’t figure out how to get that to work with WP Search with Algolia.