Jump to content

Search the Community

Showing results for tags 'config'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Using and Managing Revive Adserver
    • Documentation
    • Using Revive Adserver
    • Managing Revive Adserver
    • Bugs
  • Advanced Topics
    • Performance, Scalability, and Reliability
    • For Developers
  • Revive Adserver Community
    • Revive Adserver Project News and Announcements
    • Feature Requests
    • Plugins
    • Requests for Consulting
    • Off Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL

Found 3 results

  1. Hi folks, I am using Revive as part of an RTB bidding platform. There are a ton of querystring variables that I want to pass through to the click and log URLs that are passed into the adjs call. When I add a new variable, so the URL is something like: http://localhost/revive/delivery/ajs.php?zoneid=1&cb=52153050782&foo=bar The resulting javascript, which initiates the click and log URL's, does not contain foo=bar. I set about creating a plugin to allow this. +1 for an example plugin for every available hook! +1 for additional documentation! (I realize the irony here that the plugin framework was built while I was intimately involved with this project, and the documentation and examples should have come from my team :) ) After building a plugin based on the 'addUrlParams' hook, so the following componentParams get passed: "foo" => "{foo}" I realized that the values get URL encoded, so I cannot pass in a variable {foo} to be translated because it gets URL encoded. Am I missing something here? If not, can I submit a pull request where new values can be added in the config file? Thanks! Love, Scott
  2. I have an insert which is failing in lib/pear/DB/DataObject.php here: $this->raiseError("insert:No table definition for {$this->__table}", DB_DATAOBJECT_ERROR_INVALIDCONFIG); return false; Never mind about the source of the error for now, I'm working on that (fixed). The issue is that I didn't see this error until I hunted it down by cut and destroy. The code in question returned false and continued otherwise silently. So, my question is whether my config is insufficient to call attention to this error, or is something else going on inside Revive which stops the error from being propagated out. In my php.ini I have, although nothing appears in the apache error logs, or in php_errors.log either: error_reporting = E_ALL display_errors = On log_errors = On error_log = php_errors.log In my Revive config I have, although nothing appears in the var/debug.log (and yes, it's writable). [log] enabled=1 type=file name="debug.log" Following dumping information manually to screen, I found the DB_DATAOBJECT_ERROR_INVALIDCONFIG call, however, without this: Nothing appears on screen, or in any logging/debug file. Excuse me for showing my ignorance, but perhaps there is a simple flag I'm missing, or someone has some helpful pointers here...?
  3. Hello. I'm trying to upgrade adserver from Openx 2.8 to Revive 3.0.2 On this page http://www.revive-adserver.com/support/upgrading/ I've read: But when I've untared (or unzip) revive-adserver-3.0.2.zip or revive-adserver-3.0.2.tar.gz - there are no dummy conf file. In Openx it was var/default.conf.php I found similar file etc/dist.conf.php Can I use it? Are documentation wrong?
×
×
  • Create New...