I try to explain it a last time. Please try it yourself out with your own MG installation.
Xenforo works fine without the MG plugin. MG works fine in combination with XF as long as you do not use all ACP-settings offered within the MG-ACP settings. Only under a specific condition, depending on whether you enable a specific MG setting, MG does not work anymore.
If you offer an MG plugin with ACP-options within the ACP for MG, the coder has to make sure, that the settings of that MG plugin (no matter which option-combination you use in ACP) do not interfere with the rest of Xenforo in a negative way and vice versa.
Can we agree on this?
Because if not, the whole discussion is pointless. We would have a different definition of a "bug" and then we just differ in opinions and can not agree on anything anymore. There would be no basis to form a discussion on it.
The reason why I started this thread as a bug report is, that a specific MG setting within the MG ACP does not work anymore, as soon as you enable a specific option within MG. As proven with my screenshots and as proven with the hack of Kirby, who fixed that bug.
Again: Only under a specific condition, depending on whether you enable specific MG settings, MG does not work anymore as it was intended according to the settings you make in the MG-ACP.
These are not settings of XF. These are settings of MG. Bear this in mind. There is a reason why we have settings for MG separated from settings for XF.
If the developers would have intended to have it the way it works without the bugfix, they would have made in the description either a warning, that if you use it this way, it will bust the quota limits within MG (both, "mirroring categories" and quota settings are within MG_ACP, not within XF!!!) or they would have simply added a checkbox within MG ACP that if you turn on mirroring of XF categories, then the MG calculation of the MG quota will always include these mirrored attachments unless you check that box.
The reason why none of both suggested "hints" are shown in ACP is because the developers were not aware of that problem at all. Simple as that and the only logical conclusion.
They obviously did not test that combination of settings before releasing it. This is NOT something bad per se. Please do not misunderstand me.
Noone will complain that a bug was overseen. BUT what drives me crazy is how some people try to gloss over this bug without reading the detailed descriptions, without looking at the screenshots and without testing it themselves first before commenting on it.
A bug is a bug. Nothing earth shaking. Bugs will happen all the time and bugs are there to be fixed, not to be glossed over them or ignored by the developers if you publish them.
I reported a bug. I am only the messenger. I proved it and explained it many times, but some people throw stones at me like I would have injected a virus in the XF code or how do I dare to criticize something?
Is this a good way to deal with bug reportings?
If others are reading this, will they be motivated to report a bug in the future? What is the benefit of this community then?
