Yes, I'm getting the same problem. I've done a quick search on Google and MSN and there are lots of other sites that have the same problem. Interestingly, none of them show up with cache dates older than the 26 November. So it looks like something happened then. Had been working smoothly for weeks, then all of a sudden I get the 'This is to let you know that during a revalidation process of your site, co-op ad network ads were not found' email. On checking the ads I just see the message 'Error retrieving ads'. Checked the xml file permissions and everything are OK. The contents are shown at the end of this post. Is it a change at DP that has caused this? ------- <?xml version="1.0" encoding="utf-8"?> <Settings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <LogStats>false</LogStats> <SupportedAgents /> <MaxAdCount>0</MaxAdCount> <QuickRewnewTime>0</QuickRewnewTime> <RenewTime>0</RenewTime> <Ads /> <LastFetch>2005-11-29T04:56:02.7916972-05:00</LastFetch> </Settings> PHP:
Ads appear to be functioning correctly on my site with the ASP.NET control. Although bizarrely, with 5 ads on the page, one ad appears to be duplicated...
Hey guys, As far as the multiple ads, the only time that should happen is if you have less than 5 ads in your xml cache. Although I will investigate this further to ensure no multiple ads are served when ad count > 5. In reference to the "Error retrieving ads" error, I can take a look at that issue tomorrow evening. Alternatively, if you'd like an answer sooner, the source code to the control is available here: http://www.web-controls.net/download.aspx?f=CoopAdNetworkSource.zip Cheers, Bobby
In another post I gave Shawn my server IP address, after which Shawn informed me that my server's IP address was automatically blocked by the system for not caching ads -- ?? In my case as well, I'd been using this component for months without a hitch. Not sure where the error or problem lies, but hopefully if this is something that others are experiencing then a solution can be reached. Perhaps there's something in the way the component caches ads that the coop system decided to recently take offense to?? Hard to guess at what it could be without being on the "nuts and bolts" end at DP or knowing all the code from the component.
I think the problem may have been that the files, at some point, were not writable but ads were still being fetched, but not stored due to not being able to write. I've released a new version (1.0.0.2) that fixes this issue. If a file is not writable, no ads will be fetched. Hopefully this solves your problem. I also fixed the bug that was causing occassional multiple instances of the same ad to be loaded. All ads will now be unique always. I will incorporate a feature into the next build that will allow the developer to store the cache in memory, rather than a physical file. This should eliminate all the read/write issues. ETA is prolly a week or so on this. New files can be downloaded here: http://www.web-controls.net/blog/update__patched_co_op_ad_network_server_control_1_0_0_2.aspx Hopefully this solves the issues we've discussed. If you're still having problems, we can investigate further. Cheers Bobby D
What a legend - now that's service for something that's free! Downloaded and installed, source code squirreled for future reference Cheers, Jamie