Jump to content

andrewatfornax

Administrators
  • Content Count

    1,893
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Not sure what the -q option for PHP is there - might be affecting things? https://documentation.revive-adserver.com/display/DOCS/Running+Maintenance
  2. Without more specific information, I cannot help any further. What did you adjust, how did you adjust it - exactly what did you specifically do, and do you still see the same specific error in your log files as before? If not, do you have any other error(s) in your log files?
  3. Hi @Bono, Can you please check if your PHP installation supports the zip extension? Although this was needed in previous versions, we did not correctly test to ensure it was installed - the feature to test to ensure that the zip extension is installed during upgrade/install was added in 4.2.0.
  4. I've created https://github.com/revive-adserver/revive-adserver/issues/1054 to capture this issue.
  5. No, sorry, I cannot - I have never actually used the API myself! Hopefully someone else in the community may be able to assist though.
  6. I would imagine that when you have an error telling you that the software can't write to a given directory, the solution is to assign the appropriate permissions to the directory to give the software the ability to write to that directory, yes? 🙂
  7. I think that you could potentially use one of the https://documentation.revive-adserver.com/display/DOCS/Site+Delivery+Rules options - say Site - Variable - but unfortunately, you'd need to have something custom in place to pass in all of the relevant content that you wanted to check for the presence of the forbidden word(s) as the variable to Revive Adserver - and that would probably limit how much content you could pass in...
  8. Bingo! Sounds like you have at least one error you can now fix, and see if that helps!
  9. Hi @NjScoot, Yes, there is an (as yet undocumented) XML-RPC API, that allows for the management of (most) of the things you can do via the UI, and there is also at least one 3rd party REST API plugin for Revive Adserver as well that I'm aware of, if XML-RPC isn't your thing... HTH.
  10. No, at this stage, I cannot. When you say "it does not go to the next step", what does it do? What does it show? Can you take a screenshot and show us?
  11. Hi @chrisA, No worries, thanks for confirming. In that case, I would ask that you please double-check the upgrade instructions - it looks to me like you were maybe performing a clean install, but trying to do that into an existing database, instead of taking the required steps to get Revive Adserver to recognise that it's an upgrade, rather than a clean install. HTH!
  12. You say, trying to install the update... Just to clarify, are you trying to perform a clean install, or are you trying to upgrade an existing installation?
  13. https://documentation.revive-adserver.com/display/DOCS/Unable+to+Link+Banner+and+Zone
  14. If you'd like some assistance (and it sounds like you do), you will need to provide some more details information other than a brief text description. Screenshots, exact steps taken, full details of your setup, what the results of each troubleshooting step were etc. would all be useful.
  15. While the community would, I am sure, like to be able to help, your posts do not, unfortunately, provide much information. This is why you are probably not getting much help. However, I am glad to see that you appear to have things working now.
  16. Async tags should automatically detect the protocol of the page they are being delivered on, and use the same. In your test example above, the test page is loaded over HTTP, so that's what you are seeing used for the banner content....
  17. Hi @EERA, Unfortunately, there would not be a single file you could edit to change how impressions are "calculated" (although I'm not really sure what you mean by that). The entire Revive Adserver system utilizes a common understanding of how statistics work throughout the application - changing the understanding of this would be something that requires everything that interacts with the idea of impressions to (potentially) be changed.
  18. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken
  19. Hi @EERA, Sorry, no, there's no demo version (although you can sign up to the Hosted Edition quite cheaply!). I've also updated our docs to answer your main question: https://documentation.revive-adserver.com/display/DOCS/FAQs
  20. Hi @bartv, Revive Adserver supports the logging and reporting of requests, in addition to impressions. https://documentation.revive-adserver.com/display/DOCS/Banner+Logging+Settings
  21. Agreed, we should remove the option for anything other than 60 minutes. Also, @PicNic, chances are maintenance is not finishing within 5 minutes, which may be another reason you have lock messages, as maintenance is still running when the next one tries to start.
  22. Hi @bostongio, Best place might be the Chrome Developer Tools, which should let you log the details of what's coming back to the browser - that may shed some light on the situation.
  23. Hi @scott001, Sure, a bug is always a possibility! If you can reproduce, can you please set up a bug report in GitHub with the steps for us to reproduce? Thanks.
  24. Ah, thanks @Matteo Beccati! I had this on my follow up list, but I can see you have answered. I was thinking about looking into the code re: the database level lock, but I completely missed the fact that this is auto maintenance! @PicNic, if you use auto maintenance, this is expected behaviour, as multiple banner deliveries are likely to trigger maintenance in parallel - but only one maintenance process is allowed to run at a time. If you move to scheduled maintenance, you should get a much clearer view that maintenance is running correctly, without the other information cluttering the logs.
  25. Possibly this is coming from your PHP configuration? https://documentation.revive-adserver.com/display/DOCS/Email
×
×
  • Create New...