May 26, 2021 at 8:43 am #7689
I am looking for suggestions/ideas on how I could easily inject and maintain custom scripts I am creating for out OST instance.
I don’t know if what I have in my head is possible but, what I am thinking of is to create/add a file for all my scripts that would automatically be loaded (ideally I could specify on which pages, but not a must-do). This way I wouldn’t have to modify any of the core files which would make my life easier whenever I’d upgrade and go over any of the modifications I have made… 🙂
What do you guys think?
June 8, 2021 at 4:50 am #7716
hey little update…
We’re looking to have some sort of conditional fields in our forms. For example: if item B is selected in dropdown, then hide the next 3 fields.
I read some ideas about removing the bit in the code that rules the random generations, but I am not too keen to edit the core code.
So I am wondering if anyone has done this another way or has suggestions ?
May 8, 2022 at 4:52 pm #10241AcartmegaParticipant
You should try Motherload. https://www.cartmega.com/software/osticket/motherload-for-osticket.html
Our Superlists plugin for osTicket Motherload is implementing something similar to what you suggest on the new Ticket page (client side).
Basically it identifies and hides various custom fields on the form and replaces them with dropdown lists.
I am positive that you could achieve your goal.
Hope this helps.
July 19, 2022 at 1:09 am #11059
You must be logged in to reply to this topic.