andrewatfornax

Yeah, me too. I'll see what we can do. Thanks.

Although I haven't completed this yet, I've just checked by upgrading myself to 5.0.5, and I can confirm that the plugin (once updated) does have a field for the license key. If you log in as your admin user, and go to the Plugins tab, what version of the MaxMind GeoIP2 plugin do you see?

Okay, thanks for letting me know. I will try and spend some time doing some updated documentation around GeoIP ASAP.

The only option for email-based reporting is at the Advertiser level, I'm afraid.

Just to round out the thread and confirm, when you upgrade, the upgrade wizard will ask you where the old installation is located, so that it can find the previous installation's plugin files, and copy them over (so that any 3rd party plugins are retained) and upgrade them (if they are core Revive Adserver plugins and need to be updated).

Hi @Ryan G, What version of PHP did you upgrade from? Was it a version before PHP 7? I think that PHP 7+ needs to use the mysqli extension, so you'd have to ensure that's in place in PHP, and then update your Revive Adserver configuration to use mysqli, rather than mysqli.

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

Which I understand is incredibly frustrating for you @scott001, but I am not sure how any of us can help with this. We don't have access to your server and how it's configured, or access to any of the logs - and even if we did, because we're talking about .htaccess rules and Apache, it's kind of beyond what we can support anyway. Have you had any luck with an Apache support group, who may be better able to advise why the rules are not working as expected?

Hi @2ge, Is that a persistent error, or did it come good? The server that provides the remote service needed for this feature appears to be working at the moment for me, so it may have been a transient networking or service issue between your Revive Adserver installation, and our server...

The way that I would approach this is to use a delivery rule, to specify that the banner can only be displayed on the specific page that you want it to be on.

That does seem odd from a superficial point of view looking at the code in isolation, but what delivery rules use that code, and in what real-world setup examples is it causing an issue? Code in isolation is one thing, but the context is important!

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

What version of PHP?

The maintenance process does have locking in place, to ensure that only once instance is triggered at a time, but personally, whenever I was managing a setup like that, I would put the Revive Adserver code on the central DB server too (even though it would not serve ads from there), and then run maintenance on that machine, so that there's no need for network traffic off-server to run maintenance. Every millisecond counts, right? ?

Hi @AngryWarrior, Instructions for manually upgrading your plugins, if they didn't get upgraded automatically, are here: https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded

Nope, I still don't have any means of reproducing this, unfortunately.

Ah, okay. Strange. What version of Revive Adserver please?

Press save?

In the configuration file of your Revive Adserver installation.

I guess that will depend on how your web server is configured re: how .htaccess files are detected and processed!

Hi @Zak, In short, Hosted Edition only supports what the download edition supports - so I think the answer is "no" to all of your questions. https://www.revive-adserver.net/faq/

https://documentation.revive-adserver.com/display/DOCS/Unable+to+Link+Banner+and+Zone

Hi @scott001, Okay, thanks - have you enabled debug logging in Apache and traced the logs to confirm that the rules you are putting in are being triggered, and why they are not working as expected?

Hi @proa, You mentioned "aqua ad server". Do you mean https://www.aquaplatform.com/ ?

The only mention I can find of SVG files in HTML5 banners is https://github.com/revive-adserver/revive-adserver/issues/924 which was an issue fixed in 4.1.2, so this should work in 4.1.4 (although I would still strongly recommend upgrading, as there have been security issues fixed since 4.1.4). Do you have more details on what's happening or how to replicate?