Daniel Iser
Forum Replies Created
-
@stoffb, @nomades – I just worked on a similar bug described here, and with the info I got from his setup was able to fix it in a way that should be pretty reliable.
If your issue is related to that one, which I suspect it is, then the next release (v2.0.9) should hopefully resolve it for you.
I’m happy to have you test the fixes yourself if you get a chance to confirm its resolved for you too before I release, so if your inclined to make the code changes here they are.
I was able to properly render all loops with ACF fields during my tests just now.
Perfect looking into it now. I think one thing we can immediately look at doing is not not filtering
the_posts(query post filtering) until a specific hook, such asinit. Currently its set to always filter, but I’m thinking there are cases where plugins make custom queries very early, that we don’t need to be concerned about, such as querying custom field data types etc.Will debug a bit and let you know.
@pwosterbrock – Awesome, would it be possible to either have you export all the configs, or grant us temporary access (with ability to use the in dash plugin editor)? I think this is the same issue as reported here.
It would be useful to comment out sections of our code to see if the problem resolves, this would help narrow in on where the conflict is coming from and lead to a faster resolution.
If so we recommend sending the Trusted Login token from within our plugin (Content Control -> Support -> Grant Support Access), or Temporary Login without password plugins. You can submit the details securely via https://contentcontrolplugin.com/support/
I have all the plugins mentioned, but feel like a lot could be lost in the translation without detailed setup steps:
Elementor Loop Grid Widget, with a (Post Info Widget > Dynamic Tag > Custom > ACF Field) inside.
- This reply was modified 2 years, 9 months ago by Daniel Iser.
@lewisburgess79 – Curious, have you tried downgrading to v1.10 again? Not as a solution, but if it happens with that version too I’d have to assume it was in fact coming from theme or something else.
Honestly I can’t see how adding those 2 classes in the new version would change things, unless something in your theme also used those same classes before we did so. Otherwise if you also updated theme or other plugins recently that might be a good place to check as well.
That said, in your editor you wrap them with <p>, change that to a <div> and the html should be valid. Currently <div> can’t be inside a <p>, but our shortcode always used divs so I don’t think that was the only issue.In the short term simple fix might just be some CSS.
.some-custom-parent-class .content-control-accessible {
display: inline; // you could try inline-block as well.
}@stoffb, @nomades – Could either of you provide access to those test sites with v2 active and the ability to use the plugin editor? I mainly want to comment out sections of our code to see what action/filter is interfering here.
If so you can submit a login token or credentials securely via https://contentcontrolplugin.com/support/
Ok so just based on what I do see, this function is where the error occurs is here: https://developer.ww.wp.xz.cn/reference/functions/get_rest_url/
Specifically it means$wp_rewriteis null when this line is called:$wp_rewrite->using_index_permalinks()
I’m back tracking up through our usage of that function, but I believe this means something is forcing our plugins query filters to be run much earlier than they should.
In which case I need to find the source so I can figure out how to best address it on our end.
Those logs would be super helpful.@gerold1968 – Ahh, thats a different error than the previous one. Can you check if there are any others, I’d love to patch them all in one go, the more we solve & the earlier we solve it the better for any body else who might run into this.
Also that log is truncated (…), any chance of getting the full message or logs? I’m trying to figure out what is starting this process leading to an error, and the initial calls are buried in the …@noelawill – Just updated the form to accept zips, sorry about that.
@nomades JP\CC\Options’ is from v1. That code either means your plugin files are corrupt (half v1, half v2), or something is using our functions in your theme or custom code
I’m gonna set up acf along with elementor that I tested earlier tomorrow.
Some screenshots of what your describing would be helpful as well, specifically how ACF stuff appears, but normal content doesn’t. It leads me to think ACF isn’t using the global $post or $query when rendering things, not sure why they’d do that though.
@defender75 – Ok for the record I just tested this with Elementor Pro, created a loop grid with about 6 of 10 posts, each with different categories.
I was able to use the Hide/Filter controls successfully via the alternate query controls (NEW).If your post grid used the “Main Query”, then you would use the corresponding “Hide/Filter” controls for the Archive page just above.
Let me know, as its starting to seem more like a configuration issue with the restrictions possibly. Are you using any special Elementor addons I’m not accounting for?
Otherwise can you try to replicate the issue with one of our demo sites, your free to install whatever extra you want, when you duplicate the issue I’ll work to resolve it there hopefully.
https://app.instawp.io/launch?t=content-control-v2-sample-demo&d=v2
@noelawill – You can submit them via https://contentcontrolplugin.com/support/
Please include a link to this topic so I can keep track.
@rogererkens, @rabbit424 – Can you follow this guide and send us a token via the support form here. Leave a link to this ticket in the message so I can find it easily.
Will check things over and see if we can’t work out the kinks for you.
@dkurapati – Sorry for the delay, can you send me screens of the actual settings in your restriction, one of the last 2 tabs mainly (Protection & Content).
Further if its possible can you follow this guide and send us a login token via the support form here
@defender75 – Can you follow this guide and send us a token via the support form here
@joroabv – Not a problem, you can set up a test site based on our demo site: https://app.instawp.io/launch?t=content-control-v2-sample-demo&d=v2
@nobodee – I’m not sure if I’m misunderstanding or just unable to replicate the issue.
I’ve set up a test with a post with an excerpt, and a restriction that uses the Replace Content -> Custom Message + Show excerpts option.
This is working as intended, showing the excerpt above the restricted message.So maybe your settings need tweaking in v2, mainly because we added quite a few additional controls for things like how restricted posts behave in archives.
Let me know, happy to help.