History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: OX-3844
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Lukasz Wikierski
Reporter: Arlen Coupland
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
OpenX Ad Server

Backwards compatibility of 2.0 block features broken in 2.6.0

Created: 14/Aug/08 11:48 AM   Updated: 05/Nov/08 10:52 AM
Component/s: OXP: Delivery Engine
Affects Version/s: OpenX 2.6.0
Fix Version/s: Milestone 22, OpenX 2.6.1, OpenX 2.7.14-dev
Security Level: Public (All users can see these issues)

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: 0h
Time Spent - 1.67h
Time Spent: 1.67h
Time Spent - 1.67h

Passed QA Version/s: OpenX 2.6.1 and OpenX 2.7.27-beta

 Description  « Hide

Verified with 2.6.0

Using a zone JS invocation with block=1 in 2.6.0 will work. However using a 2.0-based invocation for the exact same zone & adserver will not result in blocked banners.

 All   Comments   Work Log   Change History   FishEye   Crucible   Builds      Sort Order: Ascending order - Click to sort in descending order
Arlen Coupland - 14/Aug/08 11:52 AM - edited
It seems that a correct/non-duplicate banner is selected by ajs.php however the incorrect banner is written to the user's screen

For example, using firebug I see that one invocation tag selects and outputs bannerID 99. Another invocation tag later on selects bannerID 33 but outputs bannerID 99

Lukasz Wikierski - 21/Aug/08 10:53 AM
Fixed in the same way as in 2.4 (added Backwards compatible block-banner JS and Backwards compatible block-campaign JS )

Lukasz Dybcio - 25/Aug/08 02:08 PM
Working good in 2.6.1-rc6.

Lukasz Dybcio - 22/Sep/08 01:41 PM - edited
QA: Can be tested after OX-4060 fix.

Sue Houghton - 05/Nov/08 10:51 AM
Passed in 2.7.27-beta-rc3