-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REQUEST: Enable for users as well #2
Comments
Hey @HQRaja , thanks for the suggestion. To understand better your requirement I have a couple of questions as I'm not sure exactly what user data you want to make available, and where to show it.
As the plugin is called "reveal post data", I think I'll try to keep the objective of it to reveal any raw data associated with a particular post - I think there might be scope to elaborate and show more info about the post author. Thanks |
Hi @rmorse, Apologies for not explaining it better earlier. What I meant to say was the way this plugin adds a button to see all relevant raw data when we're editing the post, can you please similarly add the ability to see all relevant raw data for a user when we're editing a user, and all relevant raw data for a taxonomy when we're editing a taxonomy. It could then be perhaps renamed to 'reveal raw data' or something similar. Or perhaps this one could be left as-is and forks created called 'reveal user data' and 'reveal taxonomy data' and modified accordingly to work for the purposes I mentioned above? |
@rmorse That said, what you mentioned regarding showing related author raw data in a separate tab when showing post raw data would also be a good addition to this plugin (in addition to what I requested). |
Great plugin! I'd want identical functionality for WordPress users as well, in order to reveal user data (including metadata) in raw format for debugging and development. Can you please add that feature? Come to think of it, this will be useful for all content types in WordPress, including taxonomies as well.
The text was updated successfully, but these errors were encountered: