22 Jan 2007
30 Nov 2009
Link to this post
Ok, so this is "by design" after all. I thought, from the first reply, that the ID would be accessible in 3.7SP1, no matter if the page had previously been published or not.
The fact that the desired behavior is working with previously published pages is better. I also understand the dilemmas that may may have developing Sitefinity's workflow and stuff related. Still, you are really close to have a rather perfect self-contained workflow that even non-tech personnel can relate safely to.
Here's an example scenario to illustrate my point:
The CMS is online and we have a number of new pages to be created and published simultaneously, say announcing a new product. The new pages should not be visible in the web's navigation after our desired moment of publication, and not before. Further, these pages have a number of hyperlinks referencing each other, and it would be great to be able to reference by ID (browse) once and for all. Taking the database offline is not an option.
We are of course not stuck her. We can either set property "Show in navigation" to No for all pages part of a common publishing, publish once, edit links, and keep a list of pages meant to be visible in navigation, and finally set property "Show in navigation" to Yes for those pages. Or just keep a list of pages/links to be re-established, publish, edit, and publish.
The workaround is ok except that it interferes with and complicates the workflow. That is, making special instructions for the editors and publishers would be tedious, for all parts.
So far, this is actually the only spot where Sitefinity has turned out for us to be less than user friendly. But I guess that is not bad, compared to the strenghts of the system. Can live with it!