especht

Thank you Stephan for the reply. We're using a hosted version of Revive, so we can't install the patch ourselves. Is there any estimate on when the next version with this change will be released?

An SEO expert has asked us to implement rel="sponsored" for all ad links. Is there a way to do this for all ads in Revive? If not natively, is there a plugin that could help? Thanks for the help.

If anyone has any idea how to find what version of the Banner Types plugin I should be using with Revive Version 4.1.1, please let me know. I am trying to figure out if having only version 1.1.0 might be the reason that the asynchronous ad tags aren't appearing in my zones.

I'm wondering if the issue is the version of the Banner Types plugin being used. For Revive Server Version 4.1.1, I see that we're using version 1.1.0 of the Banner Types plugin. I'm having a hard time finding what is the version I should be using with 4.1.1. Any idea where I can find what is the version I should be using?

We're using Revive 4.1.1 and when we look at the invocation code for a banner type ad, we're not seeing the asynchronous one - only javascript, iframe, and local mode. Any idea why we wouldn't be seeing the asynchronous type?

If anyone has any suggestions, I'd love to hear it. We're currently using the standard "Javascript Tag" type - where the script code is placed into our design at the point where it should display. I've read some articles about asyncronous javascript tags, but I'm not seeing that as an option - perhaps that is a custom module we need to purchase? Another thought I had is waiting until the page is loaded and then using jquery to insert the script tags into the proper positions after page load. If anyone has had any success getting revive to load the ads after page load, I'm very interested in hearing about it. Thanks in advance.

We use revive on a few sites and have been getting bad scores by google for slow page load. We believe part of the problem is the way we have the ad tags put into the page. We are using the standard javascript script tags wherever we want the ad to display, but that means that portions of the page won't load until the ads have returned. Is there another type of ad tag that we can use so that the content of the page can load first and then the ads can be appended later?

Thank you for the quick assistance. I found that it is 3.0.2. I'll contact our host to get a more current dump. Thank you for the help.

I don't believe so. I can check, but I'm pretty sure what was provided was the database and content that was current. The upgrade occurred a long time ago.

I am trying to move an install of Revive Ad Server (v 4.11 - upgraded from OpenX) to a new server. Our host has provided me with a backup of the mysql database and an archive of the files (php, etc.). I've created the database and restored the backup and copied the files into place and modified the config file to use the new database. When I log into Revive, I receive the following error: Unknown column 'user_id' in 'field list' The command it's trying to execute is an update on the ox_session table and it's referring to a column called 'user_id'. However, the user_id column doesn't exist in the table. Here's the create statement I see in the mysql backup I restored: CREATE TABLE `ox_session` ( `sessionid` varchar(32) NOT NULL DEFAULT '', `sessiondata` text NOT NULL, `lastused` datetime DEFAULT NULL, PRIMARY KEY (`sessionid`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; Here is the desc of the table in the restored database: +-------------+-------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+-------------+------+-----+---------+-------+ | sessionid | varchar(32) | NO | PRI | | | | sessiondata | text | NO | | NULL | | | lastused | datetime | YES | | NULL | | +-------------+-------------+------+-----+---------+-------+ Any ideas why Revive is looking for the user_id column that doesn't exist? I'm trying to respond to a reply from Ian - but I don't see his reply in the post. He asked: >> So did you did an upgrade, and then restored a backup of your MySQL database which was made before you upgraded? Any upgrading occurred before the backup of files and database was provided to me. So I'm just trying to run the exact same version as was running on the previous server. I thought all I needed to do was copy the files, create the database, restore the backup of the database, and update the config file to use the appropriate database. But that's when I ran into this error.