WARNING!!!
When you unpublish files they do not get removed from the Sitemap and Search modules. They will still be visible from the frontend. Dynamicweb know of this for over 7 months case: CAS-72131-PWL9KQ. We have received legal action already due to lawyers removing pages by a Pharmaceutical company used the unpublish button like it states in the manuals and the external lawyers still found the text in the sitemap!
Not sure if getting the existing functions to work is as interesting as creating new ones!
Developer forum
E-mail notifications
CRITICAL ERROR IN 7.2
Posted on 20/01/2011 16:17:14
Replies
Nicolai Høeg Pedersen
Posted on 20/01/2011 17:42:09
The feature of published and unpublished is described in the manual here - and it has always worked that way:
http://manual.dynamicweb-cms.com/Dynamicweb-On-line-Manual/Pages/Page-properties.aspx
The case you are referring to have bug number 4310 which have been fixed:
http://engage.dynamicweb-cms.com/Releases-177.aspx#item4310
In newer versions of Dynamicweb, from the paragraph list you can choose from "Published", "Hide in navigation" and "Unpublished". In that case Unpublished means you can only view the page if you are logged into the administration.
http://manual.dynamicweb-cms.com/Dynamicweb-On-line-Manual/Pages/Page-properties.aspx
The case you are referring to have bug number 4310 which have been fixed:
http://engage.dynamicweb-cms.com/Releases-177.aspx#item4310
In newer versions of Dynamicweb, from the paragraph list you can choose from "Published", "Hide in navigation" and "Unpublished". In that case Unpublished means you can only view the page if you are logged into the administration.
Posted on 21/01/2011 09:45:04
Thanks for the response. Unfortunately this was not the case as the core BUG has not been solved in the newest version, In the latest 7.2 version the pages are still visible in the Site map and Search module even if you are not logged in.
Have opened a new case and and the core BUG has a new number The bug number is: 5945 formally none as 4310
Have opened a new case and and the core BUG has a new number The bug number is: 5945 formally none as 4310
Nicolai Høeg Pedersen
Posted on 21/01/2011 09:47:08
I've asked our QA to take another look at this.
Will get back when the issue has been investigated again.
Will get back when the issue has been investigated again.