dmArchive "preview" shows current object

Description

After just trying to view a dmArchive of a dmHTML page, it kept reading the objectid & typename, and querying the database or cache for the view. Unfortunatley, specifying flushcache=1 did not accomplish anything.

The problem appears to be in the fourq.cfc (which is extended by types.cfc) in the getView function: there is a call to the objectbroker via: application.fc.lib.objectbroker.getWebskin() which takes only the objectid and typename from the passed stObj. This, in turn, checks for flushcache, and if it is equal to 1, checks the database on the objectid and typename of the archived object ... which returns the current object. Everywhere else, the object get's passed along as necessary.

While the workaround is easy (dump the archived object, save the body as a html page, view it), it would be nice if it worked. I'm not sure where the best place to change this is, since it includes a lot of objectbroker stuff.

Environment

None

Activity

Show:

Geoff Bowers September 26, 2010 at 9:43 AM

Can confirm this is definitely the case. We need to move this to views and methods on the dmArchive content type; ie. get rid of the hardcoded templates out of the webtop.

Fixed

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created March 30, 2010 at 2:28 AM
Updated December 22, 2010 at 12:32 AM
Resolved December 22, 2010 at 12:32 AM