Alfresco discussion and collaboration. Stick around a few hours after asking a question.
Official support for Enterprise subscribers: support.alfresco.com.
Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.
More information about the channel is in the wiki.
More help is available in this list of resources.
2017-03-24 07:55:24 GMT <alfbot> yreg: Sent 18 hours and 55 minutes ago: <resplin> IRC truncated the long messages in your PM to me, so I got a bit lost.
2017-03-24 07:55:52 GMT <yreg> Morning guys
2017-03-24 08:03:48 GMT <DarkStar1> Bonjour a tous
2017-03-24 09:06:35 GMT <yreg> Bonjour mon ami :)
2017-03-24 10:00:08 GMT <DarkStar1> Put your hands up if you're getting sdk spam mail :)
2017-03-24 10:00:16 GMT <DarkStar1> sdk related*
2017-03-24 10:01:46 GMT <bhagyas> DarkStar1: Yeah, ohej is closing the issues without a resolution
2017-03-24 10:03:30 GMT <yreg> hehe, and here it goes !
2017-03-24 10:04:54 GMT <DarkStar1> bhagyas: the constant mail beep notification is interrupting my dubstep tunes :D
2017-03-24 10:07:06 GMT <DarkStar1> Wow lot of unresolved issues :)
2017-03-24 10:07:07 GMT <qwebirc71785> Hi, I'm looking for documentation in order to create a meeting workspace in alfresco
2017-03-24 10:13:27 GMT <yreg> qwebirc71785, have checked out Alvex ?
2017-03-24 10:14:24 GMT <qwebirc71785> Alvex?
2017-03-24 10:14:34 GMT <qwebirc71785> I don't know what is Alvex
2017-03-24 10:14:45 GMT <yreg> an alfresco addon suite
2017-03-24 10:15:33 GMT <yreg> I think previous version of it had something like that available out of the box
2017-03-24 10:15:44 GMT <qwebirc71785> where can I download it? Can you give me the url, please?
2017-03-24 10:15:55 GMT <yreg> http://alvexsoftware.com
2017-03-24 10:15:57 GMT <alfbot> Title: Alvex (at www.alvexcore.com)
2017-03-24 10:16:19 GMT <qwebirc71785> Thank you! I'll give a try
2017-03-24 11:12:31 GMT <bhagyas> DarkStar1: There must be a new music genre with notification music
2017-03-24 11:12:32 GMT <bhagyas> ;)
2017-03-24 11:14:01 GMT <bhagyas> yreg: How was the attack in Antwerp?
2017-03-24 11:14:59 GMT <bhagyas> -= THIS MESSAGE NOT LOGGED =-
2017-03-24 11:22:30 GMT <fwu> hi all!
2017-03-24 11:23:09 GMT <fwu> ppl, can someone help me on this:
2017-03-24 11:23:13 GMT <fwu> in my inline workflow code, Im getting the identifier of a security group like this:
2017-03-24 11:23:36 GMT <fwu> myGroup.properties.authorityName;
2017-03-24 11:24:03 GMT <fwu> but how can I get the group description
2017-03-24 11:24:04 GMT <fwu> ?
2017-03-24 11:24:30 GMT <fwu> Im looking at this: http://docs.alfresco.com/4.0/references/API-JS-ScriptGroup.html
2017-03-24 11:24:32 GMT <alfbot> Title: ScriptGroup object | Alfresco Documentation (at docs.alfresco.com)
2017-03-24 11:24:44 GMT <fwu> but there isnt even an authorityName property
2017-03-24 11:43:03 GMT <AFaust> fwu: Why are you looking at such an old documentation page?
2017-03-24 11:43:06 GMT <AFaust> Why not http://docs.alfresco.com/5.2/references/API-JS-ScriptGroup.html?
2017-03-24 11:43:07 GMT <alfbot> Title: ScriptGroup object | Alfresco Documentation (at docs.alfresco.com)
2017-03-24 11:43:21 GMT <AFaust> Also, the group does not have a description. It may have a displayName
2017-03-24 11:44:56 GMT <AFaust> Additionally, in your case, the "myGroup" is a ScritpNode, not a ScriptGroup, and you are accessing its properties (which aren't even defined for a ScriptGroup) and when accessing properties you can access any of the "cm:*" properties by just using the local name as a property name
2017-03-24 11:47:28 GMT <fwu> AFaust, thank you!
2017-03-24 11:51:15 GMT <fwu> I have another question here: where the fields shown in the workflow details page are defined (in terms of controls to be used9. In the share confing I define the workflows screens, but I dont see any related with the workflow details page.
2017-03-24 12:26:40 GMT <mrks_js1> registered for beecon - hooray
2017-03-24 12:26:53 GMT <ohej> Heads up: SDK3 is scheduled to go out on Monday
2017-03-24 12:27:04 GMT <mrks_js1> great news ohej
2017-03-24 12:27:29 GMT <ohej> as many of you have probably already seen, I did some cleaning on Github issues. I've closed off a TON of old issues. If you have any concerns now is the time to speak up
2017-03-24 12:27:59 GMT <ohej> mrks_js1: nice! Will be good to see you there :)
2017-03-24 12:30:15 GMT <ohej> repeating for bhagyas to see
2017-03-24 12:30:18 GMT <ohej> Heads up: SDK3 is scheduled to go out on Monday
2017-03-24 12:30:20 GMT <ohej> as many of you have probably already seen, I did some cleaning on Github issues. I've closed off a TON of old issues. If you have any concerns now is the time to speak up
2017-03-24 12:32:18 GMT <yreg> hehe
2017-03-24 12:33:41 GMT <bhagyas> ohej: Thanks
2017-03-24 12:34:04 GMT <bhagyas> ohej: Not a fan of closing issues without a resolution, that's a bad engineering practise and something I oppose
2017-03-24 12:34:37 GMT <bhagyas> but good work on SDK3, did you make any videos of it?
2017-03-24 12:35:34 GMT <bhagyas> ohej: A good tutorial is a must before a major release of the SDK, otherwise there wouldn't be anyone who would be willing to adopt it quicker in the pace you'd like to see
2017-03-24 12:36:35 GMT <bhagyas> ohej: I personally don't think I'd move into SDK 3 anytime soon, since it breaks most of our customisations due to some limitations, maybe will try AFausts SDK instead
2017-03-24 12:43:42 GMT <ohej> bhagyas: which issues are you concerned about?
2017-03-24 12:44:10 GMT <bhagyas> ohej: Stuff I've reported as well as by others, example: "Given the age of this issue I will close it. Feel free to reopen if this is still a valid issue with SDK3" on an issue from Jens
2017-03-24 12:44:11 GMT <ohej> I did provide feedback on most of the issues?
2017-03-24 12:44:25 GMT <bhagyas> ohej: most feedback is just a random statement saying you're closing it
2017-03-24 12:44:40 GMT <bhagyas> instead of any validation/investigation/resolution
2017-03-24 12:44:50 GMT <ohej> Concrete example
2017-03-24 12:44:50 GMT <ohej> ?
2017-03-24 12:44:59 GMT <bhagyas> https://github.com/Alfresco/alfresco-sdk/issues/168
2017-03-24 12:45:00 GMT <alfbot> Title: The AlfrescoPerson does not work in Maven SDK 1.1.1 · Issue #168 · Alfresco/alfresco-sdk · GitHub (at github.com)
2017-03-24 12:45:05 GMT <ohej> because a lot of these issues were all the way back from 2014
2017-03-24 12:45:14 GMT <bhagyas> "Not much progress has been made on the ATV tool. I will close this issue and open a new one if we go back and revisit the tool"
2017-03-24 12:45:15 GMT <ohej> OK that's a great example
2017-03-24 12:45:26 GMT <ohej> issue was raised in 2013
2017-03-24 12:45:51 GMT <ohej> reproduced in 2014, requested feedback in 2015, no response in two years
2017-03-24 12:46:05 GMT <bhagyas> https://github.com/Alfresco/alfresco-sdk/issues/343
2017-03-24 12:46:06 GMT <alfbot> Title: functional-testing profile could be organized better in AIO · Issue #343 · Alfresco/alfresco-sdk · GitHub (at github.com)
2017-03-24 12:46:46 GMT <ohej> We have a TON of things to do, if the person who reported it didn't get back to us over the course of TWO YEARS, I think the efforts are better placed elsewhere
2017-03-24 12:47:09 GMT <bhagyas> ohej: but is it a reason for closing? you're not running a customer support portal where you get measured by the number of closed tickets
2017-03-24 12:47:15 GMT <bhagyas> but rather an open source project
2017-03-24 12:47:49 GMT <ohej> Even open source projects should do some cleaning from time to time. What's the point of keeping old issues that haven't had any activitiy or feedback in over two years?
2017-03-24 12:48:07 GMT <bhagyas> ohej: that's why there are tags, since they can be known issues for the particular version
2017-03-24 12:48:08 GMT <ohej> If more people had come in and asked about it or provided more feedback during those two years it would have been handled differently
2017-03-24 12:48:24 GMT <bhagyas> "No activity for a long time on this one, closing"
2017-03-24 12:48:49 GMT <bhagyas> ohej: I've seen some issues that gets fixed after four years
2017-03-24 12:48:56 GMT <bhagyas> re
2017-03-24 12:49:16 GMT <bhagyas> resplin went doing the same last week for issues filed by AFaust, closing them without a resolution
2017-03-24 12:49:27 GMT <bhagyas> and I see you doing the same this week
2017-03-24 12:50:36 GMT <ohej> in the case of #168 I completely disagree with you.
2017-03-24 12:51:15 GMT <bhagyas> #168: jens asks "In SDK 3, this dependency does not exists anymore.
2017-03-24 12:51:16 GMT <bhagyas> So in SDK3 we have no generated unit-tests running.
2017-03-24 12:51:16 GMT <bhagyas> https://github.com/gravitonian and https://github.com/ohej : what is the current state of testing with SDK 3?"
2017-03-24 12:51:17 GMT <alfbot> Title: gravitonian (Martin Bergljung) · GitHub (at github.com)
2017-03-24 12:51:18 GMT <ohej> The issue was reported, a proposed fix was in place, the original reporter never got back to us, the proposed fix was even included in SDK 2.1 but even after that no one replied
2017-03-24 12:51:26 GMT <bhagyas> and your next response is closing down the issue
2017-03-24 12:52:06 GMT <bhagyas> ohej: the proposed fix is not logged in the issue :|
2017-03-24 12:52:17 GMT <ohej> @mindthegab mindthegab added a commit that referenced this issue on 23 Dec 2014
2017-03-24 12:52:17 GMT <ohej> @mindthegab closed issue #168. added dependencies for enterprise profile and test… …
2017-03-24 12:52:49 GMT <ohej> Gab meant to close the issue back in 2014, but github didn't pick it up
2017-03-24 12:53:13 GMT <bhagyas> so, let me be clear - a bug gets filed for a specific version of the SDK, and you close it saying its fixed in a new version that is not backwards compatible?
2017-03-24 12:53:21 GMT <bhagyas> 'kay
2017-03-24 12:53:35 GMT <bhagyas> brb
2017-03-24 12:56:18 GMT <IanW1> Speaking of beecon (pre SDK 3 discussion), does anybody know what is happening with speaker registration codes?
2017-03-24 12:58:45 GMT <ohej> ~later tell bhagyas All the testing related issues were closed with reference to SDK3, yes. The same with Spring Loaded issues as well as beans/classes that are loaded twice. There is no way to fix those issues without breaking backwards compatibility. So we could spend another month producing a new, in-compatible SDK 2.x release, or fix it in 3.0.
2017-03-24 12:58:45 GMT <alfbot> ohej: The operation succeeded.
2017-03-24 13:01:46 GMT <alfbot> bhagyas: Sent 3 minutes ago: <ohej> All the testing related issues were closed with reference to SDK3, yes. The same with Spring Loaded issues as well as beans/classes that are loaded twice. There is no way to fix those issues without breaking backwards compatibility. So we could spend another month producing a new, in-compatible SDK 2.x release, or fix it in 3.0.
2017-03-24 13:02:16 GMT <ohej> or in the case of spring loaded, no viable fix at all.
2017-03-24 13:04:11 GMT <ohej> as for #343 I actually did provide a reason when closing it but I must have messed it up or Github pulled my leg. In any case I have added a comment on that one.
2017-03-24 13:10:26 GMT <ohej> so while we're at it, I bet you're upset that I closed #360 without any comments too?
2017-03-24 13:38:05 GMT <bhagyas> he
2017-03-24 13:38:11 GMT <bhagyas> ohej: back, was at a meeting
2017-03-24 13:38:51 GMT <bhagyas> ohej: wasn't these issues tagged specifically to a particular version of SDK?
2017-03-24 13:41:24 GMT <ohej> the majority of them was not
2017-03-24 13:41:35 GMT <ohej> and most of them have just been pushed in front of us
2017-03-24 13:41:54 GMT <ohej> like we would see the issue, set it to a specific milestone. Once that release came and went, we would set it to the next
2017-03-24 13:42:38 GMT <ohej> All of these issues still have a ton of value even if they're closed. You can always just reopen an issue, but I do not see *any* value in having a 4-6 year old issue being open when the original reporter haven't even engaged in it in years
2017-03-24 13:42:52 GMT <ohej> We are never going to agree on this.
2017-03-24 13:43:51 GMT -yreg- A friendly reminder : Early Birds rates for BeeCon are ending this weekend, so if you haven't reserved your seat yet, you know what to do ;-) http://beecon.buzz/#tickets
2017-03-24 13:46:28 GMT <bhagyas> yreg: Got them! Will you be there this time?
2017-03-24 13:46:51 GMT <bhagyas> yreg: Also pose as a early worm, so the birds will come out :p
2017-03-24 14:37:33 GMT <douglascrp> hey guys
2017-03-24 14:38:14 GMT <douglascrp> I need help with a weird problem I am facing exclusively with windows clients using firefox or chrome to connect in share
2017-03-24 14:38:51 GMT <douglascrp> we the user edits a document's metadata (edit-metadata form), after the user clicks save, the normal behaviour would be to have the browser redirected to the origin url
2017-03-24 14:39:06 GMT <douglascrp> I mean, if the user was in the document library, that should be the destination after the save is done
2017-03-24 14:39:16 GMT <douglascrp> but on windows, the form stays open
2017-03-24 14:39:31 GMT <douglascrp> no errors, no messages, nothing happens, simply
2017-03-24 14:39:54 GMT <douglascrp> I see the formprocessor being called, and the 200 code being received
2017-03-24 14:40:04 GMT <douglascrp> on mac it works, for both firefox and chrome
2017-03-24 14:40:11 GMT <douglascrp> any idea on how to investigate this?
2017-03-24 14:40:30 GMT <douglascrp> using the browser's developer tools is not helping
2017-03-24 14:41:18 GMT <douglascrp> I can do a screen share if anyone wants to see it
2017-03-24 14:41:27 GMT <douglascrp> this is alfresco 201702
2017-03-24 14:49:56 GMT * AFaust is pondering if he really should start his trip down the rabbit hole with JLAN/SMB integration into distributed caches / clustering...
2017-03-24 14:52:08 GMT <Loftux> AFaust: Not with the current implementation of a very out dated protocol
2017-03-24 14:52:39 GMT <AFaust> I am just talking about the glue-code between the very outdated protocol and the caching / clustering layer...
2017-03-24 14:53:53 GMT <AFaust> Of course I could just say, "F*** it!" and state "does not support virtual filesystem support
2017-03-24 14:55:30 GMT <Loftux> AFaust: That is what I try to tell customers when they have read that Alfresco claims it supports cifs…
2017-03-24 14:57:01 GMT <AFaust> Problem is, that Alfresco actually supports "CIFS" - it just does not support SMB > 1 which is what almost all mistakingly refer to when they use the label "CIFS"...
2017-03-24 14:57:09 GMT <AFaust> I do about the same thing...
2017-03-24 14:58:00 GMT <AFaust> Basically tell them "Let me just ignore what you have read and tell you that there is no file system integration that I would use"
2017-03-24 14:59:49 GMT <douglascrp> AFaust, and what about IMAP? :D
2017-03-24 14:59:57 GMT <douglascrp> it is the same thing
2017-03-24 15:00:18 GMT <AFaust> douglascrp: I couldn't read what you were writing. Can you write a bit more sensible? ;)
2017-03-24 15:00:57 GMT <douglascrp> AFaust, I am afraid I didn't get the idea there
2017-03-24 15:01:15 GMT <AFaust> Just the variant of me ignoring that you mentioned IMAP...
2017-03-24 15:01:22 GMT <douglascrp> ah, ok... sorry
2017-03-24 15:01:40 GMT <AFaust> It looses in the translation from face-to-face to indirect text chat
2017-03-24 15:01:43 GMT <douglascrp> almost everyone wants to use the imap
2017-03-24 15:01:55 GMT <douglascrp> indeed
2017-03-24 15:01:57 GMT <AFaust> Really? Fortunately I have been spared those ideas
2017-03-24 15:02:06 GMT <douglascrp> yes, most of the new clients
2017-03-24 15:02:11 GMT <douglascrp> the latest one is actually using it
2017-03-24 15:02:36 GMT <douglascrp> trying to upload 5 years of emails inside alfresco
2017-03-24 15:02:57 GMT <douglascrp> I tried to convince them not to do so, but they insisted
2017-03-24 15:03:03 GMT <douglascrp> and they are doing it
2017-03-24 15:03:53 GMT <AFaust> Wow - I did that for my 9 years of emails from PRODYNA to archive them from Outlook proprietary archive file to standards-compliant EML format...
2017-03-24 15:03:58 GMT <AFaust> And it suuuucked
2017-03-24 15:04:14 GMT <douglascrp> I know the feeling
2017-03-24 15:04:30 GMT <douglascrp> and what is worse... they are also using the email inbound to direct all the new emails
2017-03-24 15:04:35 GMT <douglascrp> so, inbound and imap at the same time
2017-03-24 15:04:45 GMT <AFaust> To be fair... The problem is in the client. Those are mostly inefficient for large amounts of data, don't parallelize etc.
2017-03-24 15:04:56 GMT <Loftux> Have a customer that uses IMAP for email drop off. 1 folder with 3 subfolders. No more folders exposed. That should not have a performance hot? Right, Outlook on Terminal server gets the idea to rebuilds it cache very often… Solution is to create the drop of folder structure in Exchange and then use imap sync (there is such an app) to move the emails into Alfresco. Now works ok
2017-03-24 15:05:05 GMT <douglascrp> outlook 2016 is the most problematic one
2017-03-24 15:06:02 GMT <douglascrp> Loftux, by dropoff do you mean a folder to get the emails, and then moved to another folder?
2017-03-24 15:06:37 GMT <douglascrp> that is what we are using... a single folder mapped in thunderbird, and once the email is received, a folder rule move the email in folder structure for YYYY/MM/DD
2017-03-24 15:07:34 GMT <Loftux> douglascrp: Pretty much, the 3 folders is for initial classification, then they complete the classification in Alfresco.
2017-03-24 15:07:45 GMT <douglascrp> cool
2017-03-24 15:08:16 GMT <Loftux> Then it is moved to final storage based on customer id. This is the sync tool https://imapsync.lamiral.info/
2017-03-24 15:08:19 GMT <alfbot> Title: Official imapsync migration tool ( release 1.727 ) (at imapsync.lamiral.info)
2017-03-24 15:08:34 GMT <douglascrp> Loftux, thank you
2017-03-24 15:08:37 GMT <douglascrp> let me take a look
2017-03-24 15:08:41 GMT <douglascrp> maybe it can help this client
2017-03-24 15:11:36 GMT <Loftux> -= THIS MESSAGE NOT LOGGED =-
2017-03-24 15:36:55 GMT <douglascrp> Loftux, nice one
2017-03-24 15:37:08 GMT <douglascrp> the it is not annoying at all... I liked it :D
2017-03-24 15:38:36 GMT <Loftux> Thanks, actually done in 2012 and before the move to imap sync nut in principle work the same, now they drop if in Exchange shared folder.
2017-03-24 15:38:52 GMT <douglascrp> got it
2017-03-24 15:54:08 GMT <yreg> Guys, What can I do to gain a bit more performance in FTL rendering ?
2017-03-24 16:08:17 GMT <AFaust> yreg: What do you think is slow in your FTL rendering?
2017-03-24 16:21:07 GMT <yreg> Well, I can see in my profiler that alfresco is pending multiple seconds processing FTL for some solr tracking webscripts
2017-03-24 16:21:42 GMT <yreg> I do not know for sure if those files are compiled and cached or interpreted
2017-03-24 16:21:49 GMT <yreg> and I would like to know my options
2017-03-24 16:30:38 GMT <AFaust> yreg: For SOLR tracking, you should definitely drill down. You will very likely see that not FTL rendering is taking the time, but some logic in Alfresco that collects data...
2017-03-24 16:32:33 GMT <osaidi> why would nodeService.getProperties(nodeRef) give me different results for the same nodeRef?
2017-03-24 16:33:19 GMT <yreg> Oussama, it should not, unless the node properties got changed between both calls
2017-03-24 16:39:08 GMT <osaidi> actually it is the same call giving me different results when made from 2 different places
2017-03-24 16:42:30 GMT <osaidi> and i'm sure the node properties are not changed between the two calls i checked it on the node browser
2017-03-24 16:46:39 GMT *** thatguy is now known as thatguy50
2017-03-24 17:06:27 GMT <yreg> Ossama, could it be that you are accessing the node from different transactions ?
2017-03-24 17:18:23 GMT <trevr> I need a bit of advice about digital signatures, is there anyone around who could advise?
2017-03-24 17:43:56 GMT <douglascrp> I think I found the problem with the edit-metadata form
2017-03-24 17:44:34 GMT <douglascrp> the error happens if there is a date property, and if you click in the calendar button, it adds a # in the url, and that makes it fail
2017-03-24 17:48:16 GMT <douglascrp> if one types the date without clicking in the calendar button, the redirect works perfectly
2017-03-24 17:48:42 GMT <douglascrp> I am trying to track the changes between versions 5.1.g (which works) and 5.2.e (the version with the problem)
2017-03-24 18:01:14 GMT <trevr> Can anyone tell me whenever I try and install an amp and ampshare file my alfresco won't start properly and I get a "GetModelsDiff return status is 404" in my catalina.out?
2017-03-24 18:01:47 GMT <douglascrp> trevr, usually a full solr reindex fix the issue
2017-03-24 18:01:50 GMT <douglascrp> you should try it
2017-03-24 18:02:48 GMT <trevr> cool, so shutdown tomcat and then follow http://docs.alfresco.com/5.1/tasks/solr-reindex.html ???
2017-03-24 18:02:49 GMT <alfbot> Title: Performing a full reindex with Solr | Alfresco Documentation (at docs.alfresco.com)
2017-03-24 18:03:05 GMT <douglascrp> trevr, yes
2017-03-24 18:03:30 GMT <trevr> thanks douglascrp, I'll feedback in a few
2017-03-24 18:03:33 GMT <douglascrp> that's a recommended step for when you install amps dealing with content models
2017-03-24 18:07:58 GMT <douglascrp> trevr, I see you are the guy trying to install the DigitalSigning addon
2017-03-24 18:10:56 GMT <trevr> I am, I've just done the reindex
2017-03-24 18:13:19 GMT <trevr> I'm waiting for catalina.out to update :-) It's "INFO: Server startup in 9144 ms"
2017-03-24 18:13:29 GMT <douglascrp> that means it worked
2017-03-24 18:14:24 GMT <trevr> I guess it'll take a while to update as I'm still getting a 404 on everything
2017-03-24 18:14:41 GMT <douglascrp> hmmm
2017-03-24 18:27:12 GMT <trevr> okay, thanks douglascrp, I've managed to install the amps and I now need to configure the signatures
2017-03-24 19:05:08 GMT <douglascrp> ok guys, I have found the cause for the problem I was talking about before
2017-03-24 19:05:20 GMT <douglascrp> this is the one to blame https://github.com/Alfresco/share/commit/050be46165463f8d1625e72c5c13260e034da059
2017-03-24 19:05:21 GMT <alfbot> Title: Merged 5.2.N (5.2.1) to trunk (5.2) · Alfresco/share@050be46 · GitHub (at github.com)
2017-03-24 19:28:20 GMT <douglascrp> https://issues.alfresco.com/jira/browse/ALF-21887
The other logs are at http://esplins.org/hash_alfresco