Skip to content
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

Add debugging #12

Open
CodeProKid opened this issue Nov 13, 2016 · 2 comments
Open

Add debugging #12

CodeProKid opened this issue Nov 13, 2016 · 2 comments
Milestone

Comments

@CodeProKid
Copy link
Collaborator

Should consider adding debugging throughout the codebase for when things go wrong. One option is to use the AI Debugger, but that will not be available to everyone using this plugin. Will have to think about how to approach this. Overall it would just be nice to know when / why something has gone wrong when updating a transient.

@CodeProKid
Copy link
Collaborator Author

Thinking about this some more, I think it might make the most sense to just add some hooks & filters into this codebase, and then create another plugin to do some debugging and logging.

@CodeProKid CodeProKid added this to the 1.3.0 milestone Oct 10, 2017
@jasonbahl
Copy link
Contributor

I agree. As some folks might want logging stored in WP and some may want the logging to be sent elsewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants