whats best practise to deal with several extensions which maybe modify same class or at least subclasses.
Let me give you an example to explain it a little bit better.
Lets say i have created an extension which adds a field to UserRequests, call it EX1. Then i have another Extension which adds several fields to incidents, call it EX2. Now some time later i need to modify the base class ticket and create a new field there, EX3.
Creating a new field is not the problem thats pretty straight forward, but is it really necessary to also update the <presentation> tags from EX1 and EX2 so that the new field from the ticket class (EX3) is visible?
Is there a better way or a best practice to archive this so that i dont have to update every other extension as well?
If i really need to update every extension is it enough to just redefine the <item id="user-content-fieldset:Ticket:baseinfo"> ?</item></presentation>
thanks for you advise on this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
whats best practise to deal with several extensions which maybe modify same class or at least subclasses.
Let me give you an example to explain it a little bit better.
Lets say i have created an extension which adds a field to UserRequests, call it EX1. Then i have another Extension which adds several fields to incidents, call it EX2. Now some time later i need to modify the base class ticket and create a new field there, EX3.
Creating a new field is not the problem thats pretty straight forward, but is it really necessary to also update the <presentation> tags from EX1 and EX2 so that the new field from the ticket class (EX3) is visible?
Is there a better way or a best practice to archive this so that i dont have to update every other extension as well?
If i really need to update every extension is it enough to just redefine the <item id="user-content-fieldset:Ticket:baseinfo"> ?</item></presentation>
thanks for you advise on this.