Unexpected behavior with BEE, BAT, and Commerce integration

Hi @dudeweb,

Just a fellow community member here — not a maintainer of BEE, BAT or Commerce.

I understand the frustration of losing days to an integration that didn't work the way you expected, I really do. But please remember that these modules are built and maintained by volunteers who are giving their time to the Drupal community. Coming into their issue queue to call their work "the worst module in Drupal" is genuinely demoralizing, and it's the kind of comment that makes maintainers burn out and abandon projects — which ultimately hurts all of us who rely on them.

If there's a real bug, please describe it properly (versions, steps to reproduce, expected vs. actual behavior) so it can be fixed. If the modules simply don't fit your use case, that's also valuable feedback — but it can be said without the hostility.

Hi!

I understand you're frustrated about the lost days.
I've faced the same frustration with these modules myself. But I didn't give up, mainly because of the great value these modules give.

I've gone ahead and updated the issue title to be more descriptive so other users can find it if they have the same problem. The original title "DO NOT USE THOSEMODULES!! Lost days! Thanks a lot!" was changed because it is not constructive for the issue queue — it doesn't describe the technical problem, it can't be searched by others with the same issue, and it violates Drupal.org's issue etiquette.

While I understand the venting, the original title isn't very helpful for getting technical issues solved on Drupal.org.

To try and make things right: share the bug here in the issue queue. Post the specific errors you're hitting with BEE, BAT, and Commerce, along with the steps to reproduce.

I didn't give up on them, and maybe you don't have to either.

Thanks.