Jump to content

andrewatfornax

Administrators
  • Content Count

    1,898
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. I think the short answer is that I am not aware of any option to change this. Can you please raise a GitHub case (with PR if you are so inclined)?
  2. So, just to clarify, though - if you put the legacy city geo targeting data file in place, Revive Adserver provides an option to allow targeting by city, which isn't available if the data file isn't present?
  3. Yes, that is indeed the case - if you use a *x* zone, then any banner of any size will be able to be displayed. Unfortunately, that's just the way it is - if you want to be able to fall back from a zone of one size to another size, well, the assumption is that any size is okay... The only way around this would be to use *x* zones, but separate out your banners by sizes into different campaigns, or use other Delivery Rule options to control where banners are displayed. There are some API options that can be used to obtain information about what zones have banners linked or not, but this is for management, rather than delivery. In the delivery service, no, there is no current option to "ping" the zone to find out if it would deliver a banner or not.
  4. I don't think there's any upper limit to the weight, other than what the database field will support - unless the UI prevents certain values?
  5. Ah, I think maybe you don't need the PDO version of the MySQL library; instead, you can use the mysqli version, which Revive should support natively.
  6. What does your phpinfo(); page look like?
  7. Hi @dalouke, Capping depends on the ability to set a cookie in the user's browser, so, the very first impression they see is not a capped banner, if there is no cookie already set from Revive Adserver. This is to ensure that we don't deliver a capped banner over and over and over again to someone who won't accept the cookie.
  8. https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering
  9. Update your PHP installation to have the MySQL extension!
  10. https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded and https://documentation.revive-adserver.com/display/DOCS/Plugins+Missing+or+Disabled ?
  11. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken ?
  12. No, best option is the use of Delivery Rule Sets for consistent application.
  13. Yes, this can be done - in the UI, there are options for different URLs for the admin UI, delivery, etc etc. If you set these up, and configure your web server serve the host names used appropriately (e.g. the UI root path needs to be www/admin) then this can be done.
  14. This sounds like you are either not correctly specifying the location of your old installation during the upgrade, or, if you are, the webserver does not have permission to access the old installation directory and files. (During the upgrade, access to the old installation is needed to bring across various files/settings.)
  15. Duplicate post of https://forum.revive-adserver.com/topic/5384-upgrading-from-414-to-421/
  16. I would recommend starting a new thread, with some details of your error, what you were doing at the time you got the error, etc.
  17. Hey @diego, I'd love to continue to help, but you are really not helping me (or the community) to help you. A link to a 13MB log file, with the expectation that I (or anyone else) has time to look through the log file for you, is pretty ungracious of you. If you'd like additional help, please try trimming the log file down to something relevant that we can work with - ideally, just the part of the log file that is produced at the time you see the issue. This is what you should be investigating yourself anyway!
  18. If you have the same problem (namely, that you see mod security in your logs denying access), then you have not disabled mod security. If you have disabled mod security, then you will not have the same problem - you will have a different problem, which will need details on what the problem actually is, from the logs, if you would like help.
  19. Sure, it's open source, so you are free to modify the software in anyway that you want!
  20. That sort of looks like a timeout issue, that you started the upgrade under PHP 5.6, and then took a while to install PHP 7, and then came back to the upgrade. Did you try the upgrade from the beginning after installing PHP 7?
  21. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  22. No, there is no solution for Revive Adserver to allow for a distributed solution which periodically synchronises statistics back to a central service.
×
×
  • Create New...