Richard Foley

Yes, it's a standard feature of the excellent Revive Adserver.

You need to look into CORS ( https://en.wikipedia.org/wiki/Cross-origin_resource_sharing ) and how this is implemented on your platform, using your web server and the programs which you are using.

No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://dev9.wesrch.com' is therefore not allowed access.

Security software (...) are notorious for reporting "false positives". You have to be careful how much serious notice you take of their often unfounded and hysterical alerts.

hi V, at the time of writing, the available plugins are: Signup and Uploads. These are actively used on live site/s, re-priced according to helpful feedback, and will be actively developed and maintained going forward. The earlier revenue and referral plugins have been abandoned as too-much-hassle-for-the-limited-interest. The local issue which was motivating the development was solved via other means. HTH.

That looks URL-encoded.

hi Erik, no, I don't underestimate the spam problem, and spam is crap to deal with, wherever it turns up. I had some success with using a simple "answer a silly question", during registration, which kept most of the spam out of my fairly busy SMN, and we have over 7000 members now. It's not massive, but we're not getting spam like this. Maybe it's an idea...? Good work from the admins that you do have. Keep it up! R.

This fellow is running at 382 million / month, perhaps this thread can help you? http://forum.revive-adserver.com/topic/3070-performance-questions/#comment-6556

Looking at your graphic, this is exactly what Revive does! Looking at your specification (100,000 websites), maybe you want to write a script which can set that up for you. If you do that, then Revive would also take care of all the stats tracking, which presumably you also want... If you don't care about which site showed which ad, then you should be able to use the same invocation code on every website, but your stats will (obviously) be screwed. Otherwise, as Andrew pointed out, perhaps you need to modify Revive, (or write a plugin?), to do exactly what you require.

You may want to read this link on base plugins here: http://forum.revive-adserver.com/topic/192-plugin-not-installed/#comment-6943

Revive Adserver Signup / Registration plugin released. Enables administrators to create Advertisers and Publisher accounts in one step. Also, if enabled, permits users to access the self-signup registration page/s. Includes optional default advertiser Campaign creation. Optionally auto-create paired publisher/user account with advertiser/user account. One-click installAdvertiser creation by admin and/or self-service.Publisher creation by admin and/or self-service.Optionally create default advertiser campaignOptionally auto-create matching publisher account on advertiser creationOpen sourceInstallation and bugfix supportand more...You can see the full list here: http://plugins.rfi.net/downloads/rfi-revive-adserver-signup-plugin/ ps. hope it's ok to post this here, at least it may make a change from the spam ;)

It might be useful to share the server error message...?

This may seem obvious, but have you tried connecting to the database from the commandline using the EXACT same arguments? You might also read up on connecting mysql remotely, permissions etc., perhaps there are some clues there: https://www.rackspace.com/knowledge_center/article/mysql-connect-to-your-database-remotely

well, first I slapped my forehead when I read your reply, then I went looking for other config options and the image tag looks highly promising! Thanks for the tip, Andrew :)

I have several WordPress sites which I self-host and they have no problems hosting Revive ads. However, I have a number of users who are running their WordPress sites on a wordpress.com *hosted* server. That is their WordPress install is hosted by wordpress.com directly. The reason the Revive calls do not function on these sites is that Wordpress explicitly disables ALL javascript on their own servers, for their own reasons. My sole solution to this so far, has been to recommend my users to move to a different hosting provider. Naturally this is not ideal, and most users balk at the idea. Does anyone have any helpful suggestions for a different, more user-friendly, work-around? Cheers.