This is already registered as a feature request internally. Our product team will evaluate the impact of this issue compared to other open bugs and upcoming features, and assign a priority level to the bug report. Our developers take care of the highest-priority issues first, so we cannot provide a specific timeline for resolution at this time.
Thank you for understanding and have a nice day ahead!
@luciamarinescu so basically – since it is now becoming default on new installs, new stores won’t be able to use PPOM fields – I would see that as high priority – but that’s just me I guess.
*EDIT – Here is the image, that says you are not compatible btw.
I’d be super curious what issue is more important than the plugin not working at all on new sites. And if they aren’t too bothered about large successful sites who most need to use HPOS, then who their actual customer base is?
But either way, judging by this and the lack of response in other tickets, anyone wanting to use HPOS had better make alternative arrangements. Fast.
We want you to know that we’ve taken note of your suggestion. Our dedicated team is currently assessing the situation, considering its importance alongside other ongoing matters and upcoming enhancements. The priority of this matter will be determined, and our developers will tackle the most critical matters before anything else. Unfortunately, we are unable to give you a precise estimate for when this will be resolved, but rest assured, we are committed to addressing all the critical bugs within our products effectively.
We apologize for any inconvenience this may have caused and thank you for your patience.
Viewing 8 replies - 1 through 8 (of 8 total)
The topic ‘HPOS Compatible’ is closed to new replies.
