-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
|
@xurizaemon This is proving pretty useful. For example, I discovered 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. |
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 🔎 |
The way civi processes forms I think means each submit results in a 302 to
the results - this might make it look like a hook ran twice? But I still
wouldn't expect postProcess to run twice unless there were two form submits.
|
No description provided.
The text was updated successfully, but these errors were encountered: