Answered Notify404 not sending emails

I have installed notify404 on two different sites on two different servers - but it's not hiding any emails when a 404 occurs. The email addresses are all set up.
Any ideas of things to check?

I don't know how notify404 works, but an alternative is the LogPageNotFound extra, which will create a log of the 404s and show you them in a grid (which you can clear periodically).

Quote from: BobRay at May 15, 2017, 05:36 PM

I don't know how notify404 works, but an alternative is the LogPageNotFound extra, which will create a log of the 404s and show you them in a grid (which you can clear periodically).

Thanks for this Bob - it looks good. I can't seem to clear the log though - when I click the 'clear log' button, it takes me to:

http://www.domain.com/page-not-found-log-report/page-not-found-log-report/ (and ironically gives me a 404 error).

I have tried it one both sites, which are on two different servers, both running Rev 2.5.7 and the same happens.

Any ideas?

Thanks again.
Andy

Quote from: BobRay at May 16, 2017, 02:29 PM

Be sure you have this code (with the exclamation point) in the head section of all templates (especially the one used by the log report page):

<base href="[[!++site_url]]"">

Worst case, you can clear the log just by deleting the file. IIRC, it's in core/logs/.

Thanks. The page was created by the plugin without a template. I didn't think to check. As soon as I applied my base template all worked! Thanks !

Sorry, that would be my fault (unless your default template is empty). I assumed it would get the default template.

Is your default template empty? If not, I'll try to put in a fix.

Quote from: BobRay at May 16, 2017, 04:28 PM

Sorry, that would be my fault (unless your default template is empty). I assumed it would get the default template.

Is your default template empty? If not, I'll try to put in a fix.

No worries. Was simple once you pointed it out.
It didn't assign any template at all.
My default template isn't empty.

I just released a new version to fix this. It now assigns the BaseTemplate if it can find it, and the default template if not.

It turns out that in older versions of MODX, it works fine with an empty template, but no longer.

I can't imagine why. Thanks for the heads up.

Ah great - no problem - glad I can help someone else for a change!!