Missing Update/Checkin button in OpenKM 7.0.1

[eldrich]

Hi,
We are testing updating from OpenKM 6.3 to 7.0 at the moment but have hit a huge snag, it seems that the 'Update/Checkin' button is missing, we have checked the profile and it is ticked there but always missing in the toolbar. We have added a document as a user, then clicked no edit but no Update button appears.

We also have worries about the new drag and drop interface as we noticed that people can just drag a different named file in their by accident thinking they are updating a file they have in edit mode and in fact all they do is add a new file.

So id there a way of turning off the drag and drop and goinh back to the 'edit' -> 'Update / find the file and upload' procedure that worked so well in 6.3?
Thanks

[eldrich]

A few other details, this is a new Ubuntu 24 LTS server, openjdk -11.
We tried creating a file as an admin user using the default profile, clicking on edit and even then no checkin/update button appears.

We use OpenKM in a very simple way, essentially to prevent multiple people editing documents at the same time, it works like this,
We have created a category for each user e.g. "For_Fred", "For_Jo", "For_Liz" etc
Person A uploads a file in the right place in the taxiomy , they then assigned a category to the file to let the next person know the document is ready for them e.g. "For_Liz"

Liz logs in checks her category and see the new document, checks it out, edits it and checks it back in, she then unassigns herself from it and assign the next person using the categories.

Alas with the new 7.0.1 this easy system breaks, the update button is missing and whereas before we could update from a category tab we no longer can which means our easy simple effective way of working doesn't work anymore.

Can anyone help with getting the update button back please?
Thanks,

[jllort]

I will answer your initial question, for the other add a new post.

I attach some screenshots:

[eldrich]

Thank you for the reply, I'm sorry but I think you've missed my problem, one of the many brilliant brilliant things about using OpenKM 6.3 was it forced our users to use the same name for each iteration of a document and then OpenKM handled all the versioning. When I user found a file the latest version was always presented to them to download as the previous versions where always 'hidden' from them.

In the 'new' system someone can checkout a document called say fred.docx, make edits to it and save it as fred1.docx, then carelessly just drag and drop it into the folder where fred.docx is still checked out. Now we have old fred.docx and new fred1.docx whereas under the 'old' OpenKM 6y.3 system they would have had to use the 'Update' button and it would have forced the use of the same document name and the next user would only see one document.

Given how windows loves to add things like (1) and (2) when users download newer versions of files to save overwriting previous ones this is actually a critical (and brilliant) feature of OpenKM for us.

[jllort]

Regarding file upload, this has always worked the same way. You have always had the option to download a file, rename it, and upload it using drag & drop (or without drag & drop) in the classic interface of version 6.3 CE. Another possibility is that you may not have realized that this could be done.

[eldrich]

I must say I did not know 6.3 had drag and drop, it something we never used, we always used the Upload/Update buttons to add new files or update files.

However we still have our original problem with 7.0.1 CE, the Update/Checkin button is missing from the toolbar/menubar. This gives us a major problem imagine this:
We have a file 'fred.docx' and it is version 1.12 in OpenKM, User A decides to edit it - clicks the edit button and on OpenKM 6.3 it locks. The user edits the document and saves it as 'fred (1).docx', they click on 'Update' in 6.3 and a file browser opens and they try to upload 'fred (1).docx' and OpenKM says No because the names are different. User A renames it to 'fred.docx' clicks on update, finds the file in the browser and it uploads and in OpenKM we have fred.docx ver 1.13. All is good

In the new system User A clicks on edit, the file is downloaded and locked, User A then does their edits and drags and drops 'fred (1).docx' and see it upload, we now have two documents presented in OpenKM 'fred.docx' which is ver. 1.12 and still locked out in edit mode, and now we have a 2nd document 'fred (1).docx' ver 1.0.

If the update button was available in the menu/tool bar in 7.0.1 CE and it opened a file browser and chcked that the file name was the same as it does in 6.3 then we would have less chance of "orphaned" edits and random files appearing by accident.

Or even you do something like you highlight a file which is in edit mode, you click on an 'Update' button and then drag and drop the new file but OpenKM 7.0 either checks the filename is the same or it allows the new file to upload but replace the highlighted file to become ver. 1.13.