Pretty interesting BobRay. But is the location of the snippet in the post tpl going to work right? That's supposed to fire on posting, which means that little tpl, filled in with all the relevant info of content, time, and so on, *happens*, right? So the snippet only fires on creation, not every time someone opens the page? I am not sure it will fire at all, and also not sure it won't fire every time
Could we have a limiter in the snippet so it fires say if createdon date is not set, or other aspect of the post itself? Or is there another way to think about how to approach it.
I suppose the real place to go to do this isn't the tpls at all, of which there are a million, but rather to the code that we edited to change the subscription behavior with Jay...I barely remember that code but we know what it does. Or even right in the manifest.
Hey, thinking in an even different way, why couldn't we just make a snippet to send an email notice for each new value in the db. Maybe my idea isn't clear, in the db there will be logging of each individual post as a unique number, let's call it ID_number. Wouldn't it be relatively simple to tell the snippet, each time that ID_number in the db gets a new value, email is sent?
So falk, what do you think about these ideas? Changing the extra from error log to discuss log is pretty smart thinking, but can you find a discuss log to use? Also is converting the extra to focus on a different log a hard job? It sounds simple in theory and sensible.
I tried to go another way, I am not a dev so I always look for the simple way with less coding