Jump to content

andrewatfornax

Administrators
  • Content Count

    2,007
  • Joined

  • Last visited

Posts posted by andrewatfornax


  1. I notice, but that doesn't always unfortunately equate to having time to do anything about it. Detailed bug reports highlighting a step through with an IDE that provides us the parts of the code that are failing, and a PR to fix the issue, are always welcomed 🙂

    Otherwise, I am hoping to be able to resume more active work on the project from next week. 

    @manuel, you still have an environment that doesn't upgrade, and willing to share your install code base and DB backup?

     


  2. 1. The plugin files in the install package are in Revive Adserver's etc/plugins directory, and get copied over as part of the install/upgrade process, so an empty plugins directory in the downloaded package is correct.

    2. You can look at the base plugins in the downloaded package's etc/plugins directory, and each plugin zip file will have details inside it relating to the exact version, if you want to manually compare the versions there with what you have.

    https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded may assist with this.


  3. I hope that it will be at some point - however, I'm not aware of any plans at the moment by any of the core team members to actively work on the issue at the moment.

    I've been caught up with other projects for the last 6+ months, but hope to be able to devote more time to Revive Adserver again soon...


  4. Hi @Oneup,

    Sure, I understand what you are saying, but a 500 error is an internal error from the webserver. I get that you are only seeing the error when accessing Revive Adserver, but nevertheless, the issue is coming from the webserver, not the Revive Adserver code.

    You need to look at your webserver logs, and see what it's saying there, and debug this using your webserver documentation.


  5. Hi @yashmeena,

    1. I don't believe that we have any documentation regarding the technical details of how the Asynchronous JS Tag works in the terms of how a browser interprets the script... What is it that you are trying to do that would need this information? 
    2. The way that Revive Adserver decides which banner to display is already documented here: https://documentation.revive-adserver.com/display/DOCS/Banner+Selection+Mechanism
    3. There is no way to "override" which banner is selected - but there are lots of things you can do to make sure that it picks the banner(s) you want! The documentation about how Revive Adserver decides which banner to display should help you to understand this.
    4. Complete documentation is an ongoing project! We work on it as and when we can. If you'd like to support us in this effort, then please do consider signing up for a small monthly amount, rather than a once off large amount! We need the support of the community to help us spend more time working on changes, rather than promises of riches after the changes are done 🙂

    I hope this helps!

     


  6. I don't think that message is the cause of your issue (whatever it is), because that's a warning, rather than an error - but I could be wrong.

    I suppose it depends on what the issue actually is - but you don't actually tell us anything about what's wrong.

    Maybe start with https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken and if that doesn't help, come back with some specific details?

×
×
  • Create New...