|
Karen
|
December 11, 2018 at 2:55 pm
In both the Admin and User Registration pages the link to view an invoice is getting redirected back to the home page, as if the front end controller does not know what to do with the key value pairs. Here is an example URL from the Admin side…
https://www.mysite.com/?ee=msg_url_trigger&snd_msgr=html&gen_msgr=html&message_type=invoice&context=purchaser&token=1-34fe6cb00692ec3e835b01b3283cc9dc&GRP_ID=7&id=2310
|
|
Josh
|
December 11, 2018 at 3:45 pm
Hi Karen,
May I ask are there any security-related plugins installed on the site, or does the host have mod_security enabled?
|
|
Karen
|
December 12, 2018 at 12:59 am
No and No. The main plugins are Gravity Forms, Woocommerce, PODS and, of course, Event Espresso. I was hoping there was an obvious problem. I will start shutting things down to eliminate the possibility of plugin conflicts.
|
|
Karen
|
December 12, 2018 at 1:32 am
Turned off all plugins except Event Espresso plus add ons, problem persisted. Turned off EE add ons, problem persisted. Turned off EE and then turned it back on, problem persisted. I am confident it is not a plugin conflict.
Tested in IE, Chrome and Opera, problem persisted. Made sure Chrome and IE did not have any pop up blockers so I am somewhat confident it is not a browser issue.
Next?
|
|
Tony
|
December 12, 2018 at 2:32 am
Hi Karen,
Can you go to Event Espresso -> Messages -> Settings.
Under the HTML view, can you see the invoice messenger listed as active? – http://take.ms/d6O0W
If so, drag it to the inactive section, wait a few seconds and drag it back.
Now retest the link for the invoice, does it work then?
It could also be that the request is triggering a mod_sec rule your host has in place, you would need to contact your host and have them confirm if that is the case.
|
|
Karen
|
December 12, 2018 at 7:57 am
Tried disabling and activating the invoice messenger again, problem persists.
Checked with the host and they have not implemented any changes to the mod_sec rules since the feature was last suspected working, however after checking the messenger log I am seeing successful messages for only email and all the html messages appear to have failed and this error message is supplied…
“Message was not executed successfully.
Messenger and Message Type were valid and active, but the messenger send method failed.”
I checked the receipt option and it has the same issue.
What can I do to debug this?
|
|
Josh
|
December 12, 2018 at 8:53 am
Checked with the host and they have not implemented any changes to the mod_sec rules since the feature was last suspected working
Can they check the mod_sec logs to see if any rules are getting triggered when they try the above link to an invoice?
Then, if you can check the site’s PHP error logs for any fatal errors logged at the time the receipt URL was redirected to the home page, that will help with debugging this. If you don’t have a PHP error log to check you can activate wp-debug mode by making an edit to the site’s wp-config.php file.
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
after you’ve activated wp-debug mode, you can check the debug.log file located in the site’s /wp-content/ directory.
|
|
Karen
|
December 14, 2018 at 5:18 am
The host, which is a very popular host, indicates that they will release no information on mod_sec or the logs other than to say that their security will not interfere with wordpress or properly written wordpress plugins.
Thanks for your assistance, however at this point we have decided not to spend any more time on this issue and have disabled invoices. We will keep an eye out to see if it happens to show up as a bug fix in future patches.
|
|
Josh
|
December 14, 2018 at 7:15 am
OK,
I wouldn’t advise to keey an eye out for a bug fix, because we’re unable to replicate this issue anywhere else.
Your host would not need to release any information, but if you were to get a helpful support tech they could take a look at the logs and make any needed adjustments. Other hosts have done this and it’s resulted in fixing the same issue.
Also, if you have a few minutes to check the PHP error log and/or the debug.log, you might find a PHP error from when the invoice was attempted, in which case we’ll have something actionable to help you with.
|
