Where and how to report a Mage2.PRO extension's issue?

(Dmitry Fedyuk) #1

The preferred place to report an issue in a Mage2.PRO extension is the corresponding forum branch.
It allows to share the knowledge about an extension in a single, publicly available place.
For this reason, do not report the issues by emails or private messages.
Use email or private messages only for an additional sensitive information (e.g. credentials).

If you have a low-level issue (e.g. a PHP error/exception with a backtrace on the screen), then please report it in an extension’s issue tracker on GitHub: https://github.com/mage2pro

Reporting rules

  1. A report should always contain a screenshot.
  2. If your screenshot contains a diagnostic message or another meaningful text, then always duplicate it in the textual form.
  3. Place an exact diagnostic message to an issue’s title. Do not use generic titles.
  4. Use separate topics for separate issues. Do not post multiple issues in a single topic.

There is a Mage2.PRO issue tracker located?
Checkout issues
Where and how to report a Mage2.PRO extension's issue? (duplicate 2)
Should I duplicate my post in multiple places?
«Uncaught ReferenceError: Unable to process binding "text: function (){return getCartParam('summary_count') }"»
Where and how to report a Mage2.PRO extension's issue? (duplicate)
Integrated stripe on staging server does not reflect in front end
Should I duplicate my questions in public and private messages simultaneously?
How to report a Mage2.PRO extension's issue? (duplicate)
Should I follow the reporting rules, or I can ignore them?
Where should I upload images?
The last 4 digits in the order confirmation email sent to our customers are showing incorrectly
(Dmitry Fedyuk) split this topic #3

2 posts were split to a new topic: «Phpunit_framework_testcase’ not found in app/vendor/mage2pro/2checkout/…»


I am hoping that there is a way to configure this extension to not effect my tax calculation