-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This plugin appears to break [redmine_multiprojects_issue] #9
Comments
|
we use alias_method here, because this is compatible with redmineup helpdesk plugin. Problem is, a plugin can use alias_method or super - you have to decide to. redmine_multiprojects_issue uses super, which is the modern, preferred way. The problem is, we cannot drop redmineup helpdesk support at the moment. I suppose there is no solution at the moment to use redmine_multiprojects_issue and additional_tags together. |
Very much appreciate the swift response, and I completely understand the requirement to maintain compatibility with other plugins. I do like the reasons given under the "why another tag plugin" section, the promise of a stable/maintained product is everything we hope for these days, in the future perhaps you guys will find a way to adopt the "modern, preferred way" without breaking compatibility elsewhere. In the meantime keep up the good work! |
...perhaps something similar to the |
Hi @chrislockwood And, you (the user, which wants to install the plugin) has to create a configuration file for it. This makes the installation more difficult. The change in column_content (the method, which both plugins tries to overwrite with different approaches) is required for tags. A solution would be to find a possibility without to use column_content.: Another solution would be that Redmine provides a better solutions to customize for methods, which are popular for plugin developers (e.g. there are very often query helpers as column_value or column_content). I created a patch as proposal on redmine.org for that: https://www.redmine.org/issues/34743. With this patch, the problem would be solvable by plugin developers. |
Appreciate your feedback on this, along with the patch submission, we can only hope that it is integrated in a timely fashion. In the meantime perhaps another workaround can be found, though presumably only in the form of plugin developers working together. It would be good to have one tag plugin which has universal compatibility, because really this should be a core Redmine feature. |
sure, this would great. You can try do convince RedmineUp to use prepend instead of alias. This would be a great step, because RedmineUp plugins are used in many installations. |
I am unclear on the exact issue, presumably something method overload related, also not sure which maintainer is best placed to investigate/workaround the problem.
nanego/redmine_multiprojects_issue#48 (comment)
In my case the multiproject_issue plugin solves a significant project architectural headache, but I would very much like to use tagging in conjunction, both offer superb functionality.
The text was updated successfully, but these errors were encountered: