- NTLM authenticationNTLM authentication
- BlogBlog
- BluemindBluemind
- BPMBPM
- CalendarCalendar
- CaptchEtatCaptchEtat
- CartCart
- Classified AdsClassified Ads
- Content IOContent IO
- ContentTypes EditorContentTypes Editor
- DashboardDashboard
- Data fillerData filler
- Datasources ExplorerDatasources Explorer
- Deploy starterDeploy starter
- ExchangeExchange
- External DataExternal Data
- ExtractionExtraction
- Extra User ManagementExtra User Management
- FAQFAQ
- FlipbookFlipbook
- FormsForms
- Front EditionFront Edition
- Front NotificationFront Notification
- GadgetsGadgets
- GlossaryGlossary
- GLPIGLPI
- Google CalendarGoogle Calendar
- HyperplanningHyperplanning
- InlinemediaInlinemedia
- Job OfferJob Offer
- Link directoryLink directory
- MapsMaps
- Microsoft 365Microsoft 365
- MobileAppMobileApp
- MultimediaMultimedia
- MyFavoritesMyFavorites
- NewsNews
- NewsletterNewsletter
- NextcloudNextcloud
- Personal pagesPersonal pages
- Subscription pageSubscription page
- Proxied ContentProxied Content
- Queries DirectoryQueries Directory
- Server DirectoryServer Directory
- Skin editorSkin editor
- Skin factorySkin factory
- SMSSMS
- Social networkingSocial networking
- SurveySurvey
- SyndicationSyndication
- TagcloudTagcloud
- TarteAuCitronTarteAuCitron
- Translation flaggingTranslation flagging
- UGCUGC
- User directoryUser directory
- Web analyticsWeb analytics
- Web Deploy starterWeb Deploy starter
- ZimbraZimbra
Vertical organization chart
- Home
- Plugins
- User directory
- v2
- Update manual
- Migration from 2.13 to 2.14
- Vertical organization chart
Last published:24/09/2024
LaurenceAumeunierThis page should only be used if script asks you to manually migrate skin.20240924.UD.RGAA-OrgaChart
For reasons of accessibility, and in particular for navigating the organization chart using assistive technologies, the HTML "entity card" has been revised.
If you have overloaded the template <xsl:template match="orgUnit"> file services/user-directory/pages/services/organization-chart/organization-chart_4.5.xslHTML of a card no longer has to correspond to the structure expected by javascript.
Review your overload by starting again from the template in the plugin user-directory.
See if it's possible to apply your overload other than by overloading the "orgUnit" template. As the structure HTML of a map (div sequence, aria attributes, button placement, ....) is closely linked to JS, it's very risky to overload it.
In addition, this component has undergone several modifications to make it RGAA-compliant, so any overloading of the project may invalidate the corrective measures, so be careful!
Back to top