andrewatfornax

Thanks for the update @420 - sorry to hear the issue persists. I think there have been some updates on the GitHub ticket, so I will take a look at those ASAP.

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

Those don't like like file paths any more - suspect you entered a URL rather than a file path during the upgrade?

Review your webserver logs, then read the webserver documentation! ?

I meant more that the permissions to access the OLD installation were incorrect - the error is stating that it cannot locate the old installation's plugin files, which it needs to do to copy them over to your NEW install (as you may have 3rd party plugins installed). If you've specified the correct path, and that is the path to where the OLD installation plugins are, and the files really are there -- then it has to be a permission issue, the new installation's web server configuration is not allowing access to this path.

That's a permission error from the web server itself, not from Revive Adserver. Check your web server logs.

Hi @Kat, With an HTML banner, you can put as many links into a banner as you like. However, that's probably not actually what you want. If the customer wants to track impressions, then their banner needs to load a tracking asset which calls back to their system to record the impression. If they customer wants to track clicks, then the hyperlink to their site needs to actually be a link to their click tracking system, which records the click and re-directs the user to their site. These, however, are not thing that you should have to worry about. If the client wants these things, they should include them in their banner - normally, you would just deliver their banner as they have created it.

Erm, update it using your favourite editor?

Permissions?

This is not something that is part of the built in functionality of Revive Adserver, sorry.

The GitHub ticket above has been closed now; you could try again with the changes from the ticket manually merged into the 5.0.0 release?

I can't, no.

Hi @rogeriolira, If your question is specifically about Aquaplatform, you could get in touch with them directly, as this is a community forum for Revive Adserver. However, in general, you need to place your zone invocation tag in your HTML code where you want the banners to appear - so if that's in the footer of your site, that's where you put the zone tag.

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

https://documentation.revive-adserver.com/display/DOCS/Managing+Configuration+Files

Related? https://github.com/revive-adserver/revive-adserver/issues/1103

Related? https://github.com/revive-adserver/revive-adserver/issues/1103

Related? https://github.com/revive-adserver/revive-adserver/issues/1103

Hi there, There's a link to sign in on the Revive Adserver Hosted Edition website: https://www.revive-adserver.net/

Probably the only way I (or the community) can help is if you can post a clear and complete picture of what you have set up, in detail, and where we can then see the banner(s). The approach of giving us a small amount of information at a time (and not responding to questions that are asked) doesn't help me (or the community) to help you.

Just link additional banners to the zone(s) as required. Revive adserver will display different banners, based on what is linked and the priorities/delivery options, etc.

Not sure what that is, but can you log in? If you can, then you can recover from this and manually install the default plugins - see our troubleshooting guide for info on this!

No worries, step through the troubleshooting guide then and that should sort it out for you.

Follow the debugging guide for banners not displaying for further ideas, but my immediate guess would be that your web server isn't configured for the new domain, and therefore isn't passing the request through to Revive Adserver?

Actually, I take that back. I set up a new development environment recently, and ran into the issue with MySQL 8. I spent some time looking into the issues, and there is no simple solution, so I am afraid that for now, we have updated the requirements to note that MySQL 8 is not currently supported.