andrewatfornax
-
Posts
2007 -
Joined
-
Last visited
Posts posted by andrewatfornax
-
-
"Targeting Channels" are now called "Delivery Rule Sets".
https://documentation.revive-adserver.com/display/DOCS/Change+History
-
Hi @scott001,
No news, but I'll ask the same question of you as I asked above - are you willing to share your installed code base and a DB backup, so that I can take a look?
-
Hi @JLW,
From https://www.revive-adserver.com/support/requirements/
- For Revive Adserver v4.2 and above: PHP 7.0.8 or higher
We also don't recommend using anything other than our official releases - we really can't support the software if it's managed via a 3rd party auto-installation service.
-
Please see our troubleshooting guide.
HTTP 500 errors are an issue with your webserver, before execution of Revive Adserver code. You will need to diagnose and resolve the issue with the webserver.
-
Some of the terminology you are using doesn't really make sense, but I think the answer is yes.
You can run Revive Adserver on myadserver.com, and you can then get it to display ads/banners on mymainwebsite.com - or indeed, on ANY site.
-
Hi @JLW,
Is this a new installation or one that you have been running for a while?
Have you ever been able to delete an Advertiser before?
Has MySQL been recently updated or changed?
-
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?
-
No immediate plans for an upgrade, sorry.
-
-
I'd get rid of it, and install it from the official package!
-
-
No changes related to this thread in 5.0.3:
https://github.com/revive-adserver/revive-adserver/blob/v5.0.3/RELEASE_NOTES.txt
-
-
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.
-
Take a look in the log files generated during the upgrade process. This may help provide more information about the actual error.
-
-
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...
-
Apologies, I lost track of the issue here. So what's the issue? I can see that @manuel, it looks like you reported that you can upgrade, and it completes, but the DB version isn't updated. Is that the only outstanding issue? Is there a GitHub ticket for that?
-
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.
-
Hi @yashmeena,
- 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?
- The way that Revive Adserver decides which banner to display is already documented here: https://documentation.revive-adserver.com/display/DOCS/Banner+Selection+Mechanism
- 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.
- 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!
-
https://pear.php.net/package/Date/docs/latest/Date/Date.html#methodformatLikeStrftime
I think you want a format string of:
%m-%d-%Y
-
Hi @Oneup,
Yes, there sire is a specific place where you can start the process of looking for 500 errors, which the documentation I provided mentions!
This is a webserver issue, so you need to start with your webserver documentation.
-
Hey @420
In the GitHub ticket (linked above), you'll find a comment from me on 21 August, which links to the exact line of code where the date is being formatted for sending in emails.
Feel free to make the minor code change you need there to fix it yourself, if that's what you're looking to do!
-
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?
403 Error on Adding a new banner
in Using Revive Adserver
Posted
You may also need to consult your web server documentation re: what it logs, where it logs it, etc.
As you say, there's no 403 error in the log information above, so, it's either being logged elsewhere, or is at a different time from what you have - or logging of it is not enabled. There could be lots of reasons.