Hi everyone,
I’m looking for some expert opinion on how to solve my latest SP problem. I’ve had a complaint from our accessibility group about the All Site Content page (viewlsts.aspx) in SP2010 and I need to make some HTML tweaks to the table that lists all the content. I’m debating between two solutions:
1. Using jQuery to modify the DOM on the fly and correct the inaccessible HTML.
2. Deploying a new, accessible viewlsts.aspx to the _layouts folder.
Now I know that customizing OOTB files is not allowed but I’m not sure the jQuery route is the best either. We have a custom master page with custom JS deployed already and I’m concerned about the jQuery interfering with that and with the performance of the jQuery.
With option 2 I could rename the original page to viewlsts.aspx.bak and deploy my viewlsts.aspx in it’s place. It’s pretty clean but not technically allowed and carries its own risks.
What should I do? Any best practices or recommendations I should know about?
Note that we have SP2010 on premise with 4 web front ends, about 4000 sites and about 25 000 users.
Thanks everyone, cheers!
1: as you have custom master page you can load jquery (or any other js code to modify the page) on-demand only on viewlsts.aspx. There are several approaches how to do it: custom URL based server control, vanila js-loader on master page with usage of SharePoint SOD to load your scripts on-demand on page url.
2: it is the simplies solution in case of customization capabilities, but if you replace standard viewlsts.aspx you
- will have to implement already implemented functionallity (UI, permission restrictions, custom actions support, etc.). And, if you want to, copy-pasting of existing page is the worst solution here because it will be unsupportable in the future.
- will have to double check if an next SharePoint service pack doesn`t replace this page back
Both ways are not optimal and don`t follow recommended practics,
but I think that js customization is the best of two evils.
