nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Generated pages locked to other users

mikemalm

HTML files that are generated by templates cannot be opened or edited by anyone but the originator. Unlocking does not work (even at the Master role level), and when the originator tries to unlock the file it still remains locked to other users. The attached message appears when trying to open/edit the file. Pressing the "OK" button does nothing.

Submit locking is in place (by default) in The TeamSite branch.

Find more posts tagged with

Comments

Adam Stoller

On Windows 2000, using TeamSite / TeamSite Templating 5.5.2 SP1, I had a generated page locked by another user in another workarea. I was logged in as Admin.

I unlocked the generated file, selected it and clicked Edit, edited the DCR associated with the generated page, did a Save & Close, was prompted to regenerate the page, selected OK, was told that the page already existed and did I want to overwrite it, I said yes, and it updated it.

In other words, based on the parameters you specified and the environment I have to work in - I was unable to reproduce your problem.

Perhaps your environment is different? If so, please try to document the exact environment and the steps you go through to reproduce the problem.

--fish
(Interwoven Senior Technical Consultant)

mikemalm

We are currently using TeamSite/TeamSite Templating 5.0.1, build #5463. Workstations are pretty much 50/50 with Win2000 and Windows NT. Submit locking is the default used for locking files.

Here's what we do: User A will create a new data record, open the DCT, save a DCR and generate an HTML page. Once this is done, User A can still open and edit the page in the DCT, update the DCR and regenerate with no problem.

If User B attempts to open and edit the HTML page however, the error message occurs (screen shot of message attached in my first message). Clicking on "OK" in the window just makes the message reappear, so "Cancel" is the only option.

If User B logs in as Administrator or Master & tries to unlock the file, it seems to work OK (the lock disappears). But then if User B tries to open/edit the file again, the same message appears. Even if User A unlocks the HTML file, User B still cannot open/edit it as if the file has remained locked.

Adam Stoller

When user B tries to edit the generated file - is there still a lock on the DCR being held by user A?

Are they attempting to edit the same DCR in the same workarea or different workareas?

What role is user B logged in as?

--fish
(Interwoven Senior Technical Consultant)

mikemalm

They are attempting to edit the same DCR in the same workarea.

I did notice that the DCR file remained locked. Unlocking the DCR files resolved the problem (so anyone can open/edit the HTML page through a DCT).

But since the DCR typically is not submitted to staging (which unlocks the file), how can we keep the DCR unlocked once User A has saved and closed it? Would this require some sort of workflow that would automatically submit DCRs to staging (just a thought)?

Adam Stoller

Why is the DCR not being submitted to staging? - the DCR represents a source file which [quite clearly] changes over time, and as such should be put under version control.

When you try to edit a generated page - TeamSite recognizes that the page is templated (via the extended attributes) and re-directs the request to be for editing the DCR from which that page was generated - and thus you are attempting to have two people edit the same DCR in the same workarea - and TeamSite Templating does not allow that (for good reason IMO).

--fish
(Interwoven Senior Technical Consultant)

mikemalm

Point taken. Thanks for your help...we are going to set up a workflow that submits the entire templatedata folder on a regular basis. This is our first attempt at using templates for our intranet and we learn as we go. Thanks again.

sma

For my case, TeamSite is allowing the second user to edit the DCR even though it's locked by the first user??

Here's my scenario:
Let's say user A edited and saved an existing DCR, but didn't regenerate. This particular DCR is locked by editing and the lock is owned by user A. User B came along and edited the output HTML from this DCR. (This HTML has no lock on it at the time of editing) By editing this HTML, it is allowing user B to modify the locked DCR (own by user A). It seems like it's ignoring the locking mechanism on Teamsite.