Timeline for CiviEvent registration & IATS payment processing fails to blank page
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2016 at 4:22 | comment | added | BruceW | You are probably right. I do have an extension for SimpleDonate form that was not initially notated as Drupal only. It is just showing an "Install" link and no other. What is the process for deleting an extension then? The documentation just says there will be an "Uninstall" link. Thx. | |
| Sep 21, 2016 at 12:03 | history | edited | KarinG - Semper IT | CC BY-SA 3.0 |
added 46 characters in body
|
| Sep 21, 2016 at 12:02 | comment | added | KarinG - Semper IT | You should never manually rm -r extensions - that will cause issues - everytime you disable an extension it will trigger CiviCRM to do all sorts of other things re: ManagedEntities - it is quite possible that another extension is missing/throws a fatal error; not being able to disable the iATS extension tells us there are some serious underlying issues in your CiviCRM instance; | |
| Sep 21, 2016 at 10:32 | comment | added | BruceW | With patched extension finally installed and working from master branch the page still timeouts for event registration and never finishes the process even though the payment gets processed perfectly at iATS. Also, for some reason when I disable the extension it crashes Civi. I then have to reinstall the codebase, log out, delete browser cache (b/c I think so) and log back in with a new session in order to restore Civi. Can I just remove all the old extension folders in custom_ext and just have 1.5.3patched there alone? | |
| Sep 21, 2016 at 10:08 | comment | added | BruceW | For some reason when I disable the extension it crashes Civi. I then have to reinstall the codebase, log out, delete browser cache (b/c I think so) and log back in with a new session in order to restore Civi. | |
| Sep 20, 2016 at 23:31 | history | answered | KarinG - Semper IT | CC BY-SA 3.0 |