Community
Bugs and feature requests go on GitHub, release news on Facebook, and anything about your own store goes in a private ticket. Pick the channel that fits your question.
Where to Ask
GitHub for bugs, Facebook for release news, and private tickets for anything touching your own store.
“What’s new?” Release notes, announcements and the occasional store worth a look. Follow it to get the news right in your feed.
“This is a bug.” Reproducible defects, feature requests and pull requests, filed on the public repository.
“This is my store, and it is private.” Anything touching your own orders, credentials or customer data belongs in a ticket, never a public thread.
Source
The public repository carries every issue, milestone and pull request, from first filed report to merged fix.
Issues, milestones and pull requests are all public, and the roadmap shows what is planned, in progress and released.
Contribute
Six ways to help: bug reports, translations, documentation fixes, patches, release testing, and showing off your own store.
A reproducible bug report leads straight to the right fix. Say what you did and what you saw, because your steps are what make the fix possible.
J2Commerce 6 includes 22 languages. If a phrase could read better in yours, a one-line correction improves every store running that language.
Your note on an unclear page makes it clearer for everyone who reads it next. Say which page and what was missing, and it gets rewritten.
Branch it, keep it to one concern, and say in the description what a reviewer should check. Small, focused pull requests get reviewed first.
Run it against a copy of your own store, the one configuration only you have. “This works on mine” is real data.
A working storefront shows other owners what J2Commerce can do. Ask to be added to the showcase, and bring whoever built it with you.
Ground Rules
One conduct rule for every channel, plus a private route for security reports instead of a public issue.
One rule, applied everywhere: debate the work and respect the person. Nobody is expected to already know how all of this fits together, and every question is worth answering.
Report it privately rather than in a public issue, so the fix reaches every store before the details are public. The advisories page has the reporting address, what happens after you send it, and every published advisory with the versions it affects.
Opens the J2Commerce repository on GitHub, where anyone can file an issue.
