In eCM you could secure a piece of content but it would still show up for users who weren't logged in, as well as for logged in users who didn't have access.
It seems that with WCM if you don't have access to content, you don't see it (unless the link is hardcoded).
Is there a setting that anyone has found that switches this on/off?
Our content producer is still testing WCM and while trying to figure out when left-side navigation showed up (and whether that was something we could control, outside of putting every piece of content in a navigation item) he ran into the following:
We are testing WCM and I turned off Cookies with Firefox and received the following message:
Cookies are not enabled.
Unfortunately, it looks like your browser doesn't accept cookies. This site requires the use of cookies.
Please change your browser settings to allow cookies from this site, and try again.
For those individuals already using WCM and iMIS, what backup (and system maintenance) practices have you put into place?
We feel pretty confident about our SQL backup strategy, but the only items we're finding in the official docs are for SQL at http://docs.imis.com/15.1/index.asp?topic=/15.1/34128.htm and nothing regarding iMIS itself and the WCM sites.
After trying a 2 server installation in a test environment, and running into some major performance issues, we're attempting to run a 3 server install, which is a little closer to how we intend to end up; that's an iMIS app server, a database server, and a Web server.
The database server and iMIS app server seem to be setup just fine.
The WCM/Web server is something of a mess.
Since we've still got to investigate this a bit more, it sits here before posting as a bug ...
If you have a content folder that has tags associated with it, when you create a new record the inherited tags won't display.
I assume it's the same reason the Publish Location is incorrect (although it shouldn't even display if it's not correct, IMO, since some users I've worked with will copy the incorrect address, assuming it's correct).
Since we've still got to investigate this a bit more, it sits here before posting as a bug ...
Our content guy ran into an error while attempting to create a new piece of content.
Interestingly, he created the content record, saved it, then went back in and added HTML content to the document.
When attempting to save the record he got a message like
