Support

August 3, 2012 at 2:38 pm

I have a client I’m developing for who wants to -hide- many EE capabilities at a very detailed level. For instance, when creating a new event we hide the ability to create a post. And we hide certain individual line-item capabilities on repeating events. We do this using CSS in a style sheet that we load when in the WP dashboard (that’s a long story, but it is doable and works fine) that makes -specific ID=””s invisible- on the EE admin pages.

However, not all EE capabilities in the interface(s) have unique IDs. For example, on the “Event Overview” when creating a new event, there is a panel “Event Options” and the “Attendee Limit:” and many other capabilities there are just LI (list items) or P (paragraphed) code with no unique ID.

I would like to ask if the EE development team, in the future, could please assign a unique ID=”” to each individual section of the interface that a developer might like to suppress through CSS hiding? Again, for example, in the “Event Options” this would be 1) Attendee Limit; 2) Allow Group Registrations; 3) Max Group Registrants:”; … and so forth. Ideally this would be done throughout all interfaces for all add-ons. I know that’s a big deal, but it would be a great help.

I know this will initially take a bit of effort, but it will make the interface vastly more customizable by developers, and might even be useful for the EE team as well. I know that hiding things is a kludge, but it’s been a “go or no-go” matter for me with a recent client, and we’re now doing this by hand within the EE code where we need it.

(Obviously we can doctor up the EE code ourselves to do this, but then whenever EE updates come out, we have to do code comparisons and alter dozens of lines in your new code. This is error-prone, even though usually we do things perfectly.)