-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with 5.61+? #335
Comments
Yeah - looks like that deprecation was in 2020 so it would definitely be good to stop calling if from this extension - it seems this extension calls a few core furnction that are not supported for non-core use |
Note I don't think the presence of deprecation warnings makes it incompatible - live sites should not be displaying deprecation warnings (but staging & dev should so they they do get fixed) |
@eileenmcnaughton Correct me if I'm wrong but |
@jofranz ah right - I was looking at the deprecated one - that one must have been through it's deprecation & been removed Easiest is for the extension to take a copy of the function into the extension, although a better approach would be to replace the custom search (which we are winding down support for) with a search kit display. Presumably the extension works other than that search & just the search could be removed/ disabled? |
@jofranz while I don't want to overtake this discussion, just wanted to say that I was hitting the same issue and I've spotted on your initial post that you've been using a bash script that you're calling to detect removed code from extension(s): |
@eileenmcnaughton
Touches #330
The text was updated successfully, but these errors were encountered: