Labels

accessibility (2) ADF (1) archiver (3) cmu (1) contributor (13) cookie (1) DAM (3) date (3) download (3) dynamic list (4) ephox (5) fatwire (1) fck (1) filters (1) folders (4) headers (2) IBR (3) ImageAlchemy (3) java (4) javascript (2) layout/template (4) link (6) locale (2) multilingual (1) rendition (3) replicator (4) rules (1) schema (1) search (11) sites (1) sitestudio (24) ssp/sspu (5) SSUrlFieldName (2) stellent (4) timezone (1) urm (1) weblogic (1) workflow (2)

Friday 10 September 2010

Not so ready-to-replicate

One of the fab new features introduced in SiteStudio 10gR4 was the "Ready to Replicate" flag (let's call it R2R.) As discussed in some of my other posts, sections that are not marked as R2R are ignored by Archiver during the "Manage Site Replication" process - which finally makes site management a breeze. However an oddity has crept into subsequent versions of the SiteStudio component that I'd like to mention.

One of the initial things I noticed about the R2R flag was that the SiteStudio Replicator application would ignore it. Personally this made sense to me because the application requires you to choose specific sections. If I chose it, I want it replicated!

But since upgrading to component build 546, the R2R flag is now being enforced by the replicator application. This might make logical sense to the Oracle development team but from a practical sense it is terrible. The sections I have carefully chosen to replicate are not turning up at the destination! There is no visual clue in the application to tell you if the section is R2R. The only way to know is to right-click each and every section and view the Properties. Sections that are not ready are listed as "Ready To Replicate = false" (but the sections that are ready do not provide any R2R info.)

I haven't tried it in 11g but I assume it's the same... if any Oracle guys are reading this, please consider amending the replicator application to either ignore the R2R flag or to provide some indicator or warning about sections that won't be replicated. :)

* UPDATE
There's a solution to this problem, I posted it here.

No comments:

Post a Comment