-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Compile error with v1.0.3 #171
Comments
@E-VANCE Thanks! I'm glad to hear SatisPress has been helpful for you. How are you installing SatisPress (Composer or the release zip?). It looks like an older version of |
I used the release zip since the installation that serves SatisPress is not handled via Composer... Just checked the Not sure how to proceed...? |
Do you have another active plugin that's loading an older version of |
Good question... I'll go ahead and deactivate all other plugins, upgrade to |
Gotcha... iThemes Security Pro in version The error message given isn't very helpful to this regard π I'll keep the security plugin deactivated for now, they'll probably update their dependencies at some point (and should, the last plugin update is from August 2021). Or do you see a sensible way of checking for already included packages...? Anyhow, let's get back to work on more important stuff π Thanks for your hint and keep it up! |
Oof, this is real. And I can't really disable iThemes Security Pro. woocommerce/woocommerce#27384 recently went through similar, and there are tools that let you auto-rename certain namespaces. From woocommerce/woocommerce#27384 (comment) https://github.com/humbug/php-scoper |
This kind of the bummer with relying on dependencies in WordPress. SatisPress or iThemes could prefix the dependencies, but things like If I lock the versions used in SatisPress, then we'd run into the same issue next time versions became mismatched in any plugin. I have used Mozart in the past. While it'd be a breaking change and bypass the benefits of using global interfaces like Strauss is another option that looks to be an updated version of Mozart. |
If bandwidth, check how Action Scheduler currently handles getting loaded from multiple packages across WooCommerce ecosystem (and now other things use it for background jobs, too). But that's a WP-specific package, and generic PHP libraries may not feasible to patch for such. All discussions I've seen about this very problem have concluded "global interface used across dependencies" just doesn't work out for time being, not until I think doing namespace juggling is the only sane way forward. |
https://github.com/silexphp/Pimple/blob/main/README.rst states
Solid Security (ex-iThemes) |
Hi there,
first of all: Awesome plugin, solved so many headaches for me. Many thanks for developing and maintaining π.
I ran into an issue when SatisPress (supposedly) updated to
1.0.3
β at least I could resolve it by downgrading to1.0.2
and the error is re-producible in my environment.This is the error output:
Running PHP
7.4.26
on Apache2.4.51
with WordPress5.8.3
. Let me know if you need more specific debugging information.Do you have an idea what could be causing this issue...?
Thanks & regards,
Henning
The text was updated successfully, but these errors were encountered: