topic Re: Change version label after checkin in CIFS? in Alfresco Archive

Change version label after checkin in CIFS?

loggheci — Tue, 06 Feb 2007 09:38:27 GMT

We are using Alfresco 1.4 Enterprise Edition and we like the rich possibilities of CIFS. The checkinout.exe in the CIFS folders therefore is very helpfull…But if we add the aspect versioning to our content, after a checkin, the version label stays blank… (thats normal).Is there a possibility to add

Re: Change version label after checkin in CIFS?

bsawler — Thu, 05 Apr 2007 14:59:08 GMT

Hi,

I am using 2.0 Community and when I check-in a document the versioning notes never appear and always remain blank?

Did you every resolve this issue?

Thanks,
Bradley

Re: Change version label after checkin in CIFS?

kevinr — Fri, 20 Apr 2007 08:42:52 GMT

I am using 2.0 Community and when I check-in a document the versioning notes never appear and always remain blank?

Do you mean checkin through CIFS or the web-client?

Thanks,

Kevin

Re: Change version label after checkin in CIFS?

bsawler — Fri, 20 Apr 2007 13:02:51 GMT

Hi Kevin,

The version notes works fine, with one exception… you need to do step 2 first and then step 1. For example step 1 asks you to enter version notes, and you do… then you go to step 2 and upload a file, and when you upload a file it clears what you did in Step 1 (i.e. clears your notes). So if you do step 2 and then step 1 all works fine.

Any change of fixing this! It's hard for a lot of us, to think to do step 2 before step 1… it just doesn't fit. ha ha

Regards,
Bradley

Re: Change version label after checkin in CIFS?

kevinr — Fri, 20 Apr 2007 13:14:04 GMT

Ahh yes that problem it's been an issue since V1.0 - unfortunately it's a limitation of the JSF Web UI Framework we are using without going into details, having an upload component that is compatable with both Portals and WebApps inside a JSF Form causes an issue which led to the confusing page layout that you mention. There are solutions, but the priority to fix the page has never been high enough unfortunately. Feel free to raise the issue in JIRA so users can vote on it!

Thanks,

Kevin