Matteo Beccati

Hi @scott001, I'm sorry - we must have missed this. We've had similar reports, but until now no one was able to provide any useful information on how the malware or compromised plugin files were injected in the first place. Do you have any older logs that could help?

@Snaggy yes, absolutely. An/or you can find a pristine file in etc/plugins/openXBannerTypes.zip. The zipfile can be used together with the "Import" button in the plugin screen to overwrite the existing files.

@tvvpmi Yes, please clean up your plugins/bannerTypeText/oxText/genericText.delivery.php file, which has most likely been compromised at some point. Unfortunately the logs sent by @sunech didn't cover the time when that happened.

Thanks for your help. Would any of you allow me to have a closer look, in order to see if I can spot anything else that's unusual and possibly gather more information?

data-revive-id is a hash calculated using the delivery and deliverySSL config values. @Adi The old one had "www" in the path while the new one doesn't, that's why you're getting a different id.

It's a known incompatibility with the utf8mb4 charset: https://github.com/revive-adserver/revive-adserver/issues/740

@olabre See my original reply. Testing upgrades from 2.0.11-pr1 is now part of the release process. Tags should also be compatible, as long as you are not using functionalities that have been removed.

@OMG I believe you just need to make sure that This banner can be safely displayed inside an iframe (e.g. is not expandable) is checked in the banner-edit screen.

As I said earlier, only "clickTag" is supported. Revive AdServer only supports a single destination URL.

Revive only supports the main clickTag. They should also be using the JS variable thereafter, not an <a href

I'm sorry, magic macros aren't supported in HTML5 banners. You should stick to the default, which is using clickTAGs. You should kindly ask your client to comply.

Hi @tkat https://support.google.com/dcm/partner/answer/3145300?hl=en Look for Simple ClickTag insertion.

@andrewatfornax maybe the plugin requires the revive-id field used in the async tags? @melamoccicata If so, just generate an asynchronous invocation code and copy the revive-id html attiribute value.

The setting is in the webserver hosting Revive Adserver.

@Maro Sorry, I can't possibly know how your servers are configured. Wordpress is not involved in that though.