Diversi xhur ilu, waqt ix-xogħol fuq proġett ta 'klijent, I created a feature. Among other things, li karatteristika definit azzjoni custom (dawn jidhru taħt settings tas-sit). The only purpose for this custom action was to demonstrate to me that the feature activation was working as expected. Bażikament, I used it as a crude form of debugging.
Much to my embarrassment, this debugging artifact made its way from dev to UAT and to production before someone got around to asking, "what is this xyzzy link?"
By now, we’re in production and I really don’t want to uninstall the feature, fix elements.xml and then reinstall.
Todd Bleaker pointed out an easy way to handle it. In his words:
"CustomActions are not copied into the database, huma jinqara direttament mill-fajl Elements.xml u ikkopjata fil stat applikazzjoni fil runtime. Allura, inti m'għandekx bżonn li deattivat, uninstall, jerġa, u jattiva l-karatteristika li tneħħi l-CustomAction. Just tneħħiha mill-fajl Elements.xml u jirriċiklaw l-pool applikazzjoni(i) effettwata. Il-ħin li jmiss il-karatteristika hija fl-ambitu, inti mhux ser tara l-CustomAction aktar."
I segwita l-istruzzjonijiet tiegħu u, tal-kors, jaħdmu.
Fil-każ tiegħi, this is a department level installation with just a single WFE. If you find yourself with this problem in future and with multiple WFE’s, Nemmen li inti ser ikollhom jagħmlu l-bidla f'kull.
</aħħar>
