Maro
-
Posts
38 -
Joined
-
Last visited
Posts posted by Maro
-
-
You need the Foliovision VAST Plugin and the Pro Version of the Foliovision Flowplayer.
I hat this but didn't managed to get it to work. First, i got CORS Errors and now my licenses are expired. I don't know if it has problems with the XML code Revive Adserver is delivering.
I'm exhausted on this problem... i'ts very sad.
-
It seems to be gone, at this time there is no CORS Error.
With foliovision VAST Tester, i got this next error:
FV VAST Ad error: AdError 1010: The ad response was not understood and cannot be parsed.
Maybe the player doesn't support this Version of VAST? I also tried to use = instead of %3D after "...pre-roll..."
-
Hello, i'm wondering which VAST Version is used. I didn't found any hint. Only a thread from 2014, it reads that back then revive adserver only supported 1.0.
Thank you
-
Anyone a clue? ??
-
I just switched to SPC because of the bad performance of asyncJS. The banners are not there instantly. I read about the fact, that async JS is as good as SPC without the disadvantages of asyncJS.
So what is the trick? Use only the <ins> line without the <script...> line for each banner?
-
On 7/6/2018 at 1:34 AM, andrewatfornax said:
Okay - did allowing the path fix the issue?
If not, then I suspect you haven't really allowed what's needed.
Try turning off all restrictions first - if that works, then you've got a starting point to figure it out from!
No it does not fix the issue. I already tried to say that. My english is not the best, sometimes it is hard to express myself correctly.
The issue isn't there at this time. I don't know why but i was disappeard before.
-
Hi, i already allowed the path
" is not within the allowed path(s): (/opt/plesk/php/7.1/share/pear/MDB2/Driver/Extended/:/var/www/vhosts/example.org/:/tmp/)"
-
Hi, the debug.log shows this line:
Jun 26 05:32:43 +0000 OX-5b31cffbdef91 [ warning] is_readable(): open_basedir restriction in effect. File(/opt/plesk/php/7.1/share/pear/MDB2/Driver/Extended/mysqli.php) is not within the allowed path(s): (/opt/plesk/php/7.1/share/pear/MDB2/Driver/Extended/:/var/www/vhosts/example.org/:/tmp/)
I have added the directory
/opt/plesk/php/7.1/share/pear/MDB2/Driver/Extended/
but the warning is still there, as shown above, now with the path as a allowed one.
What problems are possible with this issue?It's a Plesk Onyx Server, v17.8.11.
Maro
-
I am using this in Google WebDesigner
<script type="text/javascript" gwd-events="handlers">
window.gwd = window.gwd || {};
gwd.exit = function(event) {
clickTag = window.location.search.substring(1).split("clickTag=")[1];
window.open(clickTag);
};
</script> -
This is seen at the foliovision vast tester https://foliovision.com/player/vast/tester
FV VAST load (0,html5) https://servingdomain/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8
fv-player-vast.min.js?ver=6.6.2.1:1 FV VAST Ads init.
fv-player-vast.min.js?ver=6.6.2.1:1 FV VAST Ad error: AdError 1010: The ad response was not understood and cannot be parsed.After reload the CORS message is there again:
Failed to load https://servingdomain/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
-
Is there nobody who has the same issues? Really?
-
Did anyone know another good adserver software? I have not to be free.... It should just work.
-
i tried this:
https://developers.google.com/interactive-media-ads/docs/sdks/html5/cors
but itis already true, so:
"The value of the 'Access-Control-Allow-Credentials' header in the response is 'true, true which must be 'true' when the request's credentials mode is 'include'. Origin 'https://thevideowebsitethatshouldshowthevideo.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute."
-
Which credentials? What means include? Where to change it?
-
8 minutes ago, andrewatfornax said:
Well, the error you are seeing seems pretty clear:
The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access.
Seems like setting something other than the wildcard might help?
I use Plesk server administration software. I can add additional headers but then it shows the error, that there are more than one directives.
I dont know what this googleapi is, but if revive need this connection, than is the asterisk the right configuration, no?
-
Hi, thank you!
„This only applies to Flash-based video players. HTML5 video players do not require any crossdomain.xml policy file configuration.“
I already read this, but it seems to be only necessary for flash videos. I want to use only html5 videos.
-
The Revive Version is 4.1.4.
Please help :(
-
644 is ok for running server, but for installation and upgrading some folders should be set to 777, like mentioned in the documentation. The conf file can be 444, but for changes it must be writable to the owner.
Make sure the folders have the correct owner and group, like www-data for the owner. I'm using plesk, the owner is a user i named when creating the website subscription.
-
Hello everybody.
I want to serve video ads and i get this error:
Failed to load https://adserver.tld/www/delivery/fc.php?script=bannerTypeHtml:vastInlineBannerTypeHtml:vastInlineHtml&format=vast&nz=1&zones=pre-roll%3D8: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'https://imasdk.googleapis.com' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
It's similar to the html5 banner error from version 4.1.1, that was fixed through update.
I want to show the video ad in a wordpress website with foliovision's fv player plugin and their VAST plugin.
Is here anyone who know how to fix this?
Thank you in advance
Maro
-
Oh ok, thanks for clarifying this. So i will search for a click tracking solution.
The problem is not the repsonsivness of the banner, but the iframe around the banner, that revive is generating. sorry for beeing off topic.
-
Isn't a HTML5 Zip package automatically delivered via an iframe? The zone is using a asynchronus JS Tag and the ad is loading in an iframe. Is there any other solution?
It's hard to get HTML5 banners responsive.
"then the banner can not be delivered via an externally hosted iframe"
In my case, the zip package banner is in revive, not externally hosted.
-
Can somebody give me paid support? Anyone?
-
tagdiv has no clue, i don't know what to do now.
-
I use Newspaper theme of tagdiv. When switching to another theme, everything works well.
I try to find out why and where newspaper is setting a wildcard header.
Which VAST-Version
in Using Revive Adserver
Posted
Any information about 2.0, 3.0 or 4.0?