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

WordPress support #1

Closed
xurizaemon opened this issue Mar 25, 2017 · 4 comments
Closed

WordPress support #1

xurizaemon opened this issue Mar 25, 2017 · 4 comments

Comments

@xurizaemon
Copy link

No description provided.

@xurizaemon
Copy link
Author

xurizaemon commented Mar 25, 2017

xurizaemon pushed a commit that referenced this issue Mar 25, 2017
@christianwach
Copy link
Collaborator

@xurizaemon This is proving pretty useful. For example, I discovered that hook_civicrm_postProcess fires twice when submitting the "Online Registration" section of an Event form. I'm pretty sure it shouldn't be doing that!

Which got me to wondering... could this be refined such that it audits the hooks that CiviCRM fires? Or are the rules for this too complex to code?

Just a thought.

@xurizaemon
Copy link
Author

xurizaemon commented Mar 31, 2017

I'm open to any additions people want to propose - initially it was called "civideveloper" but I didn't want to claim that namespace until it did more than just show hooks.

So: yes, and also check out some of the other issues like #3 #6 #7 #8 - maybe you could open a new one for auditing and outline the sort of audit checks you'd envision? (Maybe "these hooks should fire once per page, these are ok to fire twice?")

Are the rules complex? IDK! But if we start making a list - "hook_civicrm_config should only fire once per run" - then we can find out 🔎

@xurizaemon
Copy link
Author

xurizaemon commented Mar 31, 2017 via email

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

No branches or pull requests

2 participants