Mark Huot

So I found out where things are going wrong for me. The issue is that `count($data)` here, https://github.com/nystudio107/craft-seomatic/blob/f00efb180f743ed81a425bf6a8c2d0403ba7321d/src/models/MetaTag.php#L155 is only, ```php ["property" => "og:image"] ``` That's causing the render to...

Ah, you had it… and I didn't understand what you were asking, sorry. There _is_ an SEO Settings field enabled for this content type. In that field I see the...

Yup, I'm following. I see the light switches per-field and (to start) they are all disabled, meaning they're pulling from the per-channel settings, I believe. I did some more testing...

Yup! That seems to help. And with that set in the content settings I can successfully ignore the per-entry override field because it works in either situation. Phew, that's an...

I believe the issue is, 1. Set the "SEO Image Source" to "Custom URL" and enter Twig code like `{entry.imageField.url}` for example. 2. Notice on the "General Settings" there is...

So that some user groups could access more often and others less often? Hrm… right now rate limiting isn't exposed to the UI, would you be okay with this per-group...

Yup, this makes perfect sense. FYI, on `dev-master` there's a feature that hasn't made it in to the docs yet that allows you to limit queries by depth and by...

I'm working on adding this in to the Token "Settings" page. I have query depth and complexity in there relatively easily. I'm struggling with query rate limiting though because right...

> In my case, It's really the quantity that is the problem, so I'm not sure if depth/complexity would help…but I wouldn't want to bog down everything just to support...

Yea, I may just bite the bullet and enable logging per token. There are a bunch of cool side effects of that decision too, like being able to show a...