Open lkraav opened 4 years ago
hey @lkraav could I have a bit more context here, please? Thanks
Could I have a bit more context here.
Oops, I could've indeed mentioned this triggers simply by loading front (or any) page.
hmm I narrowed it down to the Frontend class; if I exclude everything other than that looks ok - seems an interaction with wc_memberships_get_members_area_endpoint()
but I'm not sure yet exactly where/how and why
I am unfamiliar with this plugin here. From semver looks like it's still not an official 1.0 and I guess code is going to change until/if it makes it to core. Is there a reason why should it be considered a bug in Memberships or should we prioritize this on our end?
If there's anything we can change in Memberships please open an issue or PR in the repo.
Thanks
At what WordPress action does wc_memberships_get_members_area_endpoint()
happen at?
Where is the codebase for this plugin?
@westonruter
WooCommerce Memberships is a commercial WooCommerce plugin and the repository at https://github.com/skyverge/woocommerce-memberships has private access (@lkraav and I have access; there's a mirror on the Automattic/WooCommerce org: https://github.com/woocommerce/woocommerce-memberships).
wc_memberships_get_members_area_endpoint()
is used in different parts of the plugin to return a query variable to extend the WooCommerce My Account page with a new endpoint. This function is sometimes used to filter query_vars
. At init
it is also used to call add_rewrite_endpoint()
.
We did not have reports similar to the one in OP related to other plugins.
Load front or any other page, get this PHP Notice.
Traceback:
Should we somehow be smarter about when to get involved in
parse_query
or... :thinking:cc @unfulvio