Lyndon Roeller

Thanks @joel. This is kind of an edge case but I appreciate the willingness to update your docs.

Ooooook…. I guess the app was already installed and that’s why it didn’t show up in the list.

Leaving this up in case it helps someone else.

@thundersnow Very much appreciate the authoritative answer.

I have two replies…

1. [This one’s more for the sales team] If Yext is going to sell me on the fact your platform can embed menus on websites, and you offer the option to reorder those menus in your dashboard ummm… please make it work. What’s one more call to the DB to grab the menu order I set in your dashboard? (or, for god sakes, at least document this obvious gap in functionality in your help pages).

2. Yes, I can probably wrestle these menus in the correct order on the front end, but then what? I turn this over to the Culinary Director’s team to manage and say, well, you can’t actually add or remove menus because the ordering is hard coded. Yeesh. They edit menu items (and yes, even the names of their menus) frequently.

Once again tho, I very much appreciate the Yext WordPress Plugin team’s willingness to dig into the details. Ultimately I got the same answer I received from my support ticket but at least you offered some technical detail, which I guess is what I was looking for.

Thanks,

Lyndon

@thundersnow. Well done! You very much just helped seal the deal on a sale. I’ll be sure to let our account rep know.

Hopefully this helps someone else in the future as well.

Lyndon

@thundersnow Thank you so much for the quick reply!

Do you have the ability to test with a dev copy of Multisite now? I’d love to get a definitive answer before purchase instead of being in a situation where we spend $2k+ and be testing it for you ??.

My big red flags would be…

– That there are no initial install problems on multisite

– That the plugin can pull a menu from at least two separate locations in Yext into at least two separate WordPress child sites.

– That there are no console errors on the front end.

Sorry, making you work for this one but trust me, the client will be worth it.

Lyndon

Will do. Thanks!

Ahh… forgot to mark this one resolved.

Hi there,
Still having some issues selecting which custom post types we would like the share buttons to appear on.

We have a Team archive and Team single pages. I only see “Teams” listed in the Placement option however…

https://prnt.sc/ph33bf

I’d like to be able to deselect the Team archive and select the team single.

Perhaps it’s the way we are implementing our custom post types? We’re using ACF Pro.

Any help is greatly appreciated! Thanks!

Indeed it does. Just tested on a local install. Great work and thank you.

Cool. Thank you again for the info. So basically, yes compression is happening both by WordPress and then by TinyPNG (for JPEG). WordPress sets JPEG compression to 82 and you guys up that slightly to 85.

Great, thanks for the quick answer!

To clarify, the plugin sets WordPress’ quality from 82 to 100? So WordPress’ compression is not in the mix at all, correct?

Sorry, I’m sure it’s not that simple but I would like to know more.

Lyndon

Thanks @dgwyer for the point in the right direction.

I’ll hang tight with the free version since it looks like this has been fixed in 4.7 (which should be released Dec. 6).

Links for others looking for more info on this…
https://www.ads-software.com/support/topic/uploads-changed-to-lower-case/

And the WordPress bug track ticket…
https://core.trac.www.ads-software.com/ticket/37989

Well thanks for the lengthy and detailed reply.

Perhaps the hosting environment (WP Engine) is contributing to these issues. Or, if it’s large image size, I’ll need to know more about the practical limits your service can handle.

Expect a support email soon. I’d like to get to the bottom of this and share that info here to help others who might be having similar issue.

Lyndon

ps – despite the reliability issues… your compression is great! That’s why we deal with so many errors. I do really hope we can continue to use your plugin.

Hi Mikko,
So I’ve had this filter in my functions.php for a week now and I can’t tell if it’s working. Searches for > 80 characters can still take place in WordPress, but does your filter simply prevents them from being passed to Relevanssi?

If that’s what the filter does, then it could be working. If it’s suppose to stop a long query from being performed at all, then it doesn’t seem like it’s working.

Sorry for the confusion but I’ve never worked with filters in a plugin before.

Thanks!