Jump to content

stapel_eliz

Approved members
  • Content Count

    31
  • Joined

  • Last visited

About stapel_eliz

  • Rank
    Newbie

Recent Profile Visitors

1,535 profile views
  1. The problem turned out to be that my server host hadn't actually updated PHP from version 5-point-somthing, despite my request that they do so (and assurances that they had). When Revive did the update (via cPanel's Softaculous), it asked if it could update the version of PHP but, though I'd said "yes", the update didn't apparently go through. The solution was to do the update myself. Thank you! Eliz.
  2. When I log into my Revive dashboard, I can check the various advertiser accounts that have been set up. When I do so, I am able to view the linked zones and any delivery limitations. Today, I logged into a new advertiser account (on v4.2.1), and realized that the advertiser does not have access to this information. Is this how the client accounts are supposed to be, or have I messed something up? Thank you! Eliz.
  3. Since updating my installation recently, I've been seeing error messages. According to the current installation (while in "Admin" mode): You are currently using Revive Adserver v4.2.1 running on Apache 2.4.39, PHP 7.0.33 and MySQL 5.6.44-. When I open an "inventory" account (in "manager" mode), I see the following message: MESSAGE: Declaration of OA_Admin_UI_Rule_Min::validate($value, $min) should be compatible with HTML_QuickForm_Rule::validate($value) TYPE: Warning FILE: /home/purple04/public_html/mathads/lib/OA/Admin/UI/component/rule/Min.php LINE: 41 DEBUG INFO: 36 function getValidationScript($options = null) 37 { 38 return array('', ""); //return nothing, we use JQuery validate anyway 39 } 40 41 } 42 ?> 43 44 45 46 According to the debug log (with the domain's server account being anonymized as "domain"): RV-5d4db179922a2 [ warning] Declaration of OA_Admin_UI_Rule_Min::validate($value, $min) should be compatible with HTML_QuickForm_Rule::validate($value) on line 113 of "/home/domain/public_html/adserver/lib/max/ErrorHandler.php" on line 125 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm/RuleRegistry.php" on line 125 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm/RuleRegistry.php" on line 174 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm/RuleRegistry.php" on line 1797 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm.php" on line 194 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm/Renderer/Array.php" on line 40 of "/home/domain/public_html/adserver/lib/OA/Admin/UI/component/ArrayRenderer.php" on line 1675 of "/home/domain/public_html/adserver/lib/pear/HTML/QuickForm.php" on line 300 of "/home/domain/public_html/adserver/lib/OA/Admin/UI/component/Form.php" on line 307 of "/home/domain/public_html/adserver/lib/OA/Admin/UI/component/Form.php" on line 245 of "/home/domain/public_html/adserver/www/admin/advertiser-edit.php" on line 88 of "/home/domain/public_html/adserver/www/admin/advertiser-edit.php" The lines in the "warning" are always the same, but they're not occurring continuously, so not every ad impression is generating errors... I think... Any ideas? I don't know if it matters, but I did the update via cPanel's "Softaculous" utility. And ads are indeed being served and logged. Thank you! Eliz. Edit: In poking around GitHub, I see that many files were updated "14 days ago". Does this mean there is a newer version of Revive? https://github.com/revive-adserver/revive-adserver
  4. Okay. Interesting. How would uploading (and thus overwriting) only the updated files cause all the statistics to disappear, and no new statistics to be collected? Thank you! Eliz.
  5. I know that the proper process for updating a Revive Adserver installation is NOT merely to upload whatever are the files with more-recent "save" dates. But why will this not work? (I understand that this is probably a painfully stupid question, but I'm... well... not always terribly bright.) Thank you! Eliz.
  6. I may have found a fix, and it involves editing the "async.js" file. I am NOT a coder, so USE AT YOUR OWN RISK! In the "development" folder at the github page for Revive, the "www/delivery_dev/async.js" file contains the following: 74 /** 75 * The start event handler. Delivery can be prevented by setting e.detail.start = false. 76 * 77 * @param {CustomEvent} e 78 */ 79 start: function (e) 80 { 81 if (e.detail && e.detail.hasOwnProperty('start') && !e.detail.start) { 82 return; 83 } 84 85 rv.removeEventListener('start', rv.start); 86 87 rv.dispatchEvent('refresh'); 88 }, I took the comment to heart, and decided to copy my Javascript (which was functioning correctly in reading the GDPR cookie value) into the "async.js" file. Note: In the actual "async.js" file, everything is in one line, rather than nicely broken up so as to be easily read. For testing, I first inserted my coding without stripping all of the empty spaces, line returns, etc. So my new "start: function (e)" looks like this: start:function(g){ // Begin my custom coding for reading the cookie value var CB_value, CB_consent, cb2ox; if (document.cookie.split(';').filter(function(item){return item.indexOf('CookieConsent=') >= 0}).length){ function getCBval(cname) { var name = cname + "="; var decodedCookie = decodeURIComponent(document.cookie); var ca = decodedCookie.split(';'); for(var i = 0; i <ca.length; i++) { var c = ca; while (c.charAt(0) == ' ') { c = c.substring(1); } if (c.indexOf(name) == 0) { return c.substring(name.length, c.length); } } } var CBval = getCBval("CookieConsent"); if (CBval == '0'){ CB_value = 0; CB_consent = false; } else{ CB_split = CBval.split(","); CB_array = new Array(); for(i=0;i<=5;i++){ CB_array = CB_split; } CB_value = CB_array[4]; if (CB_value == "marketing:true"){ CB_consent = true; } else{ CB_consent = false; } } } else{ CB_consent = false; } cb2ox = CB_consent.toString(); // End of my custom coding for reading the cookie value // Added "or cb2ox = 'false'" to "if" statement // "if" was "(g.detail&&g.detail.hasOwnProperty("start")&&!g.detail.start)" // I added an extra set of parentheses around the "if" condition // Then I added "||(cb2ox=="false")" inside the "if" condition, after the original condition if((g.detail&&g.detail.hasOwnProperty("start")&&!g.detail.start)||(cb2ox=="false")){ return } f.removeEventListener("start",f.start); f.dispatchEvent("refresh") }, In the above, I've included comments delineating my cookie coding, and also the addition in the "if" statement. I have tested the above script in each of Firefox and Internet Explorer, and it appears to work. My cookie script determines if the current website visitor has selected "true" or "false" for accepting "marketing" cookies (this information being available in the "CookieConsent" cookie). If the user has elected NOT to accept marketing cookies (so ads should not display, and the "cb2ox" variable reads "false") or if the user is seeing the GDPR screen for the first time (so GDPR regs require that no cookies be set - yet), then nothing is displayed for any of my Revive "zones". Phew! Eliz.
  7. I realize that your post is nearly a year old, but would you be able to clarify what you did? For instance, my "db_schema.ini" file looks pretty vanilla, with the "zones" section containing this: [zones] zoneid = 129 affiliateid = 1 zonename = 130 description = 130 delivery = 129 zonetype = 129 category = 162 width = 129 height = 129 ad_selection = 162 chain = 162 prepend = 162 append = 162 appendtype = 129 forceappend = 2 inventory_forecast_type = 129 comments = 34 cost = 1 cost_type = 1 cost_variable_id = 2 technology_cost = 1 technology_cost_type = 1 updated = 142 block = 129 capping = 129 session_capping = 129 what = 162 rate = 1 pricing = 130 oac_category_id = 1 ext_adselection = 2 show_capped_no_cookie = 129 I see nothing that might be particular to my installation, and I have no idea what is the "meaning" of "newZoneField = 2", and would appreciate clarification, as it may assist in an issue I'm facing. Thank you! Eliz.
  8. andrewatfornax: Is there any ETA on this documentation yet? Thank you!
  9. andrewatfornax: Would you be able to provide an example of what "passing a variable into Revive Adserver in the invocation code" might look like? Thank you! Eliz.
  10. My upgrade was trouble-free, and I can confirm that the Revive cookie is anonymised. Eliz.
  11. I am trying to coordinate between a GDPR cookie-setting script and Revive. The cookie-setting script starts out as "false" (so no cookies are supposed to be set) and asks the user to pick the user's "level" of cookies ("necessary", "preferences", "statistics", and "marketing"). The script then sets a cookie as either a "0" (meaning "opts out of everything non-necessary") or else as a more standard type cookie (containing something along the lines of "necessary:true,preferences:[value],statistics:[value],marketing:[value]", where [value] is "true" or "false"). For the purposes of discussion, let's call the cookie "CB". I have figured out how to have a Javascript check CB, and return either "true" for marketing, or else "false", writing this value (as a string) into a global variable "cb2ox" (for "converting CB's "marketing" value to an OpenX tag value"). I have figured out how to have another Javascript add "data-revive-cb2ox=[value of cb2ox]" to the "ins" tag in the HTML of a given webpage. (That is, if you view the DOM for the page, the new name-value pair is displayed within the "ins" tag.) I've done this scripting set-up on a page that I'm using for testing. I have set a Delivery Rule (that is, "Only display this banner when:") as: "(Site-PageURL DoesNotContain [testing page's URL]) OR (Site-Variable cb2ox Contains true)" If I'm understanding the Rule correctly, this means that ads will be displayed in the customary way on all pages other than [testing page's URL]. However, when the URL is [testing page's URL], the other rule should be checked; that is, the value of "data-revive-cb2ox" should be checked and, if NOT "true", then no ads should display. However, ads are still displaying. So clearly I'm doing something wrong. There is no documentation for "Site - Variable", so the error may lie there. Or maybe I've got the Delivery Rule set up wrong. Either way, I'd appreciate advice, instruction, links,... commiseration, sympathy,... whatever.... Thank you! Eliz.
  12. Within the /www/delivery/ directory, I note the following files: core.13871 248,520,704 12/13/2015 -rw------- core.17991 247,996,416 12/24/2015 -rw------- core.2044 248,246,272 11/12/2015 -rw------- core.24385 249,286,656 01/09/2016 -rw------- core.27415 248,008,704 07/18/2015 -rw------- core.31189 247,980,032 08/10/2015 -rw-------What are these? More to the point, do I need them? If so, do I need all of them, or only the most recent one? If not, may I delete them? Thank you. Eliz.
  13. Is there any plugin that would allow end users on my site to click a "report this ad" link, so I would get an e-mail telling me exactly which ad was problemmatic? (Or, if this is a separate scripting thing, or a third-party service, does anybody have a URL they could recommend?) Thank you! Eliz.
  14. I have been advised to change the password on my SQL database, in hopes of securing it (in case the hacker managed to snag that information). However, I can't seem to get the password to update. I've gone into phpMyAdmin inside my cPanel, and tried setting a new password. Then I changed the password in the config.php file. But I can't log in with the new password; however, the old password continues to work. I've tried setting up a new user with a new password, while removing the old user. After updating the config file, I couldn't log in with the new info, but I could still log in with the old info. I tried deleting the old user completely. After updating the config file, I still couldn't log in with the new info, but I could still log in with the old info. I tried importing the old database into a new database (with a new name), and creating a new user with a new password for the new database. After updating the config file, I couldn't log in with the new info, but I could still log in with the old info. What the frick am I doing wrong? Thank you. Eliz.
×
×
  • Create New...