View entryprops for your own journal/administrated community
entries, self-service support
Staff and senior support have the at-need ability to view some of the troubleshooting information attached to entries; this information could be useful to the journal owner.
All entries have under-the-hood information called "entryprops" (short for "entry properties") attached to them. Staff/senior technical support can view these at need.
Usually there's no need to view this information, but sometimes there's a simple question (like: did all my icon information successfully make it over when I imported? Generally the importer gets this right, but it's usually more reassuring to see for yourself) that could be answered. (And doubtlessly if it were readily available, there would be more helpful uses for it floating around.) It also strikes me as information that would be useful to a community administrator, if it's available to journal owners.
How would it be viewable? (For all of the cases below, this would only be for the journal owner/community admin; if someone didn't have permission to see if they would get an error.) I have a few thoughts.
1) Create a page where you can enter the link to an entry in your own journal (or your community), and the properties are displayed. This is simple and pretty straightforward, does not require monkeying around with any existing pages, but not entirely friendly.
2) Create a URL argument (like the ?view=flat that you can add after the entry in the address bar) to display it on/from the entry. This would be reasonably friendly, but would probably take a lot more developer doing, and you'd have to look up how to do it if you didn't remember and needed to use it. (Depending on what was less of a pain to develop, I would see this as either adding information to the existing display, or going to a new location containing the information and a link back to the regular view of the entry.)
3) Have a little link/toggle near the rest of the entry information (depending on which was less of a pain to develop as described above), labeled "advanced entry information" or similar, to make it discoverable by people who don't already know to look it up.
Questions about the advisability:
1) Is there enough need for this information that someone couldn't just go ask Support? Senior support could tell people better than I could how often they get requests that require entryprops information.
2) Would this answer more questions than it would cause? It would not be fair to Support to release a feature that would cause a deluge of "What's a ____ and why do ____???!?!" questions. If this is implemented, someone grab me and I will write docs.
3) Would any information be revealed that a community administrator shouldn't have?
4) Would any information be revealed that is Dreamwidth-internal and a user shouldn't have? (I doubt it, but I ask for completeness; staff would have to answer this one.)
Development: This sounds like the sort of high-complexity, low-impact project that might sit for 10 years without being claimed.
Poll #12339 View entryprops for your own journal/administrated community
Open to: Registered Users, detailed results viewable to: All, participants: 38