Brian Becker

Thanks methnen. I appreciate the follow up. I’ve had to go a different direction but I hope that 2.5.1 will help the next user!
Brian

I added cloudsearch to the main/default site and it worked on the main site but not the secondary site:

In a staging-server-area there are just 2 in the environment.
https://jerper.staging.wpengine.com
https://search-jerusalemperspective-com.jerper.staging.wpengine.com/

I deactivated ALL plugins except AWS globally and CloudSearch individually. No change.

On the default site, I added CloudSearch, configured and clicked “Sync All Indexed Documents” and it processed 497. Searched from the main screen and got results, but highlighting wasn’t working properly in that it just showed the excerpt or opening 50 words to each found article.

Went back to 2nd MS site (search-jerusalemperspective-com.jerper.staging.wpengine.com/) and still the search results were all “Hello World”

• This reply was modified 6 years ago by Brian Becker.
• This reply was modified 6 years ago by Brian Becker.
• This reply was modified 6 years ago by Brian Becker.
• This reply was modified 6 years ago by Brian Becker.

There are 2 “Network Activated” plugins:
Amazon Web Service
User Syncronization – to keep users synced across the multisite

And then the only plugin that is active in the site is CloudSearch

Does that mean a plugin in another sites is not properly behaving and being more aggressive than it should?

Brian

• This reply was modified 6 years ago by Brian Becker.

I would prefer having them under the same event so my calendar doesn’t have twice as many games listed.

Problem solved – sticky posts… you have to actually set the following to keep sticky from overriding your request…which I think is crazy that it overrides posts_per_page setting…

But now that I know, I won’t get caught by this bug again.

“ignore_sticky_posts” => true

Same result using => $count … I’ve also tried
‘posts_per_page’ => 3

And no difference in results…7 posts shown rather than 3.

So strange.

Is there a reason why this bug has not been addressed? It’s been a week.