Hello M. Papin,

Thanks for your reply. This unexpected change, since Adsmanager 2.9.9, will not be noticed by most users of your component if they have several visits to the adverts on their website. Though, I’m not sure if this change was written in to your code or just happened by adding more code, by including another notification e-mail in Adsmanager 2.9.9. And why does this just happen with the expiration notice and expiration e-mails? What happens if the front end of a site with Adsmanager cannot be accessed for some reason? An advertiser, in theory, cannot be notified that their advert is due to expire or has expired! Also expired adverts remain on the website if they are not clicked on.

Your component was simply better when all e-mail notifications were sent automatically (up to and with Adsmanager 2.9.8.), whether a site is visited or not, which have Adsmanager adverts and/or categories that can be clicked on. There is no logic in changing this certain aspect of Adsmanager that worked normally and as it should (and I’ve been using Adsmanager since 2007) to the semi-functional state you have now allowed for expiration e-mail notifications.

I would hope and welcome that with your next Adsmanager update you would would have revised the code for e-mail notifications to what it was (up to and with Adsmnager 2.9.8.) so that users of your component and recipients of expiration e-mails are not confused.

Merci.

Nsm

Hello M. Papin,

Thanks for your reply. On the first page of this thread, my first submission to you (in paragraph 3) I clearly state that with the re-installation of Adsmanager 2.9.8. everything works fine. There is no need to visit my site and click on Adsmanager categories or ads, when Adsmanager 2.9.8. is installed, to enable the expiration notice e-mail or the expiration confirmation e-mail to be sent. The reason why I wrote to you to begin with, is because this is no longer the case. Believe me, with every upgrade of Adsmanger I test the creation, publishing and updating of adverts (with the e-mails that these functions generate) along with the sending of expiration e-mails. Everything worked fine up to and with Adsmanager 2.9.8. with my test site, which I explained works on a two day advert cycle from the time and advert is published to the time it expires. In this two day cycle I don’t visit my test site at all!

After the two days, when I visit the test site, the adverts have already disappeared (expired) from the front and back end and the test User has received the expiration notice e-mail and the expiration confirmation e-mail. All this happens WITHOUT visiting the test site! Also nothing has changed on my site between the Adsmanager update 2.9.8 to 2.9.9. Once I know everything is Ok, I then update my main site and this is how I know Adsmanager is working as it should. This test procedure that I use simply does not function as it should for the delivery of expiration e-mails as it normally did since Adsmanager 2.9.9! I feel (but cannot prove) that since Adsmanager 2.9.9, with the introduction of the additional e-mail notification for admin - “Admin - Email - ad queued for validation” has done something to affect the sending of expiration e-mails as you would have included additional code for e-mail notifications under the “Email” tab of “Adsmanager Options”.

M. Papin, you really need to test the differences between Adsmanager 2.9.8. and Adsmanager 2.9.9., where the expiration e-mails are concerned. I’m sure you have a test site on a server and if you try a two day advert cycle as I have explained you will see what I am saying is correct. Almost every time that you have a update of Adsmanager there is a bug fix is required for something that happened without you knowing when you have added to, improved or rewrote Adsmanager and you were probably informed about it by users of your component on this forum. I can only hope you consider what I’ve said and not write it off until you make a “real world” site test to bring this matter to a close.

Merci

Nsm