Daily Log for #alfresco IRC Channel

Alfresco discussion and collaboration. Stick around a few hours after asking a question.

Official support for Enterprise subscribers: support.alfresco.com.

Joining the Channel:

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.

Getting Help

More help is available in this list of resources.

Daily Log for #alfresco

2016-12-12 06:09:30 GMT <Xen_> hi does anybody knows where alfresco keeps its stock workflows. I want to add a snippet to one

2016-12-12 07:27:46 GMT <Xen_> hi all, i wanted to know, how do you give your users on alfresco read/edit and upload rights without giving them admin rights?

2016-12-12 07:50:48 GMT <yreg> Morning guys

2016-12-12 08:05:48 GMT <Xen_> hi guys where in alfresco community will i find the stock workflows? I just want to add a small snippet in the review and approve workflow. Its to small to want to create a seperate workflow

2016-12-12 08:06:42 GMT <yreg> Xen_, do you mean you want to edit one of the OOTB workflows ?

2016-12-12 08:06:59 GMT <Xen_> yes, just add one line of script to it

2016-12-12 08:08:14 GMT <yreg> Ok, here are the sources

2016-12-12 08:08:21 GMT <yreg> https://github.com/Alfresco/community-edition/tree/master/projects/repository/config/alfresco/workflow

2016-12-12 08:08:22 GMT <alfbot> Title: community-edition/projects/repository/config/alfresco/workflow at master · Alfresco/community-edition · GitHub (at github.com)

2016-12-12 08:09:38 GMT <yreg> Xen_, you can either customize the workflow and apply your amp to alfresco war before the very first bootstrap

2016-12-12 08:09:43 GMT <twen> good morning

2016-12-12 08:09:56 GMT <yreg> morning twen

2016-12-12 08:10:31 GMT <yreg> Xen_, or simply use the workflow console to redeploy your workflow

2016-12-12 08:10:35 GMT <Xen_> thnx yreg just not sure what to do with these files. having these files and editing them....where do i go from there

2016-12-12 08:11:04 GMT <yreg> are you familiar with the SDK ? and with alfresco extention ?

2016-12-12 08:11:36 GMT <Xen_> not realy but i see now, ill just add my code give the workflow a custom name and deploy it via spring

2016-12-12 08:11:56 GMT <Xen_> just to make sure...these are the ones thats inlcluded in alfresco already

2016-12-12 08:17:11 GMT <yreg> Xen_, doing so, you will duplicate the OOTB workflow not just modify it, you will need eventually to add some content model and some form configuration (if you are to change the name of the workflow)

2016-12-12 08:18:37 GMT <yreg> What I suggested is to modify the OOTB bpm20 definitions, and deploy them to your webapp/alfresco/WEB-INF/classes/alfresco/workflow

2016-12-12 08:19:23 GMT <yreg> that way they will have precedence over the files bundled in the out of the box alfresco-repository-version.jar

2016-12-12 08:19:24 GMT <Xen_> yreg: so i cant just change the workflow name: <process isExecutable="true" id="activitiReview" name="Review And Approve Activiti Process (Testing)">

2016-12-12 08:20:33 GMT <yreg> You can change the name, but if you change the ID as well, the workflow might just not function as expected

2016-12-12 08:20:48 GMT <yreg> as it would probably require some other stuff to be done

2016-12-12 08:24:29 GMT <Xen_> ok thnx so much

2016-12-12 08:28:41 GMT <yreg> once you modify the file and place it in the right folder hierarchy you can go to the workflow console and redeploy it

2016-12-12 08:29:15 GMT <yreg> What's your alfresco version ?

2016-12-12 08:30:04 GMT <Xen_> alfresco-community 201605

2016-12-12 08:30:54 GMT * yreg really hate this new naming scheme

2016-12-12 08:33:58 GMT <Xen_> yreg i redeployed the workflow using a different worfklow ID and name but it looks completely different.

2016-12-12 08:37:57 GMT <Hiten> Hi Guys, Today I have been facing an issue with one of my installation related to libreoffice

2016-12-12 08:38:41 GMT <Hiten> during viewing on .doc documents and uploading on any document an error is thrown in the logs

2016-12-12 08:38:49 GMT <Hiten> http://pastebin.com/b2VcGAmY

2016-12-12 08:38:50 GMT <alfbot> Title: Libreoffice_Error_while_viewing_document - Pastebin.com (at pastebin.com)

2016-12-12 08:39:00 GMT <Hiten> http://pastebin.com/Z8FQ0u2X

2016-12-12 08:39:01 GMT <alfbot> Title: Possible Spam Detected (at pastebin.com)

2016-12-12 08:39:22 GMT <Hiten> http://pastebin.com/Z8FQ0u2X

2016-12-12 08:39:23 GMT <alfbot> Title: Libreoffice_Error_while_uploading_document - Pastebin.com (at pastebin.com)

2016-12-12 08:39:52 GMT <Hiten> I have checked and my libreoffice is running on port 8100

2016-12-12 08:40:05 GMT <Hiten> can anyone please explain me what needs t be done

2016-12-12 08:42:16 GMT <Hiten> When I run command ./libreoffice_ctl.sh status

2016-12-12 08:42:22 GMT <Hiten> I get the this result

2016-12-12 08:42:30 GMT <Hiten> libreoffice already running

2016-12-12 08:44:01 GMT <twen> may be livreoffice is not running on the port 8100...

2016-12-12 08:45:52 GMT <Hiten> @twen: it is running on 8100

2016-12-12 08:46:00 GMT <Hiten> netstat -plantu | grep 8100

2016-12-12 08:46:01 GMT <Hiten> tcp 0 0* LISTEN 7869/.soffice.bin

2016-12-12 08:46:04 GMT <twen> ok

2016-12-12 08:46:48 GMT <twen> the error is an illegalExcptionArgument... seems like LibreOffice doesn't like what Alfresco is giving him ?

2016-12-12 08:48:53 GMT <Hiten> not sure but by looking at logs it seems more of a connection issue

2016-12-12 08:49:47 GMT <Hiten> also, the exception is coming in the case of upload

2016-12-12 09:13:58 GMT <fcorti> Hi all, we are very close to the release of the GA version of the next Alfresco Community Edition.

2016-12-12 09:14:35 GMT <fcorti> I think you are all interested to know in advance

2016-12-12 09:28:09 GMT <yreg> a GA starting from the 3rd iteration ?

2016-12-12 09:30:27 GMT <yreg> fcorti, any heads up on when should we expect a new EE release ?

2016-12-12 09:30:35 GMT <yreg> 5.2.x

2016-12-12 09:32:09 GMT <AFaust> fcorti: When GA is shipped, what will be the status of Search Services module / SOLR 6, both in terms of maturity and "Open Source"-ness?

2016-12-12 09:36:55 GMT <fcorti> yreg: Alfresco One 5.2 GA will be released in may 2017

2016-12-12 09:37:22 GMT <yreg> fcorti, thanks for the info

2016-12-12 09:37:28 GMT <fcorti> you are welcome

2016-12-12 09:37:57 GMT <fcorti> main features: the new REST API, Share enhancements, Search Services (with Solr6)

2016-12-12 09:39:32 GMT <fcorti> AFaust: Solr6 will be fully integrated even if it is an alternative of Solr4.

2016-12-12 09:40:16 GMT <fcorti> About the status, it is fully integrated, but probably you are thinking to specific features/details we can discuss

2016-12-12 09:40:48 GMT <fcorti> About "open-source"-ness, also in this case, the idea is that it is... but probably you are thinking to further details

2016-12-12 09:41:11 GMT <fcorti> my suggestion is to wait few days for the GA release and then... start discussing about those details

2016-12-12 09:41:30 GMT <fcorti> I'm interested to hear about feedback and I could share them with the team

2016-12-12 09:41:34 GMT <fcorti> for the future releases

2016-12-12 09:46:31 GMT <AFaust> I am just thinking about "source repository / code being available" and "documentation being available"

2016-12-12 09:47:30 GMT <AFaust> e.g. if GA is released I usually expect all of this to be available, otherwise it is just another EA

2016-12-12 09:57:31 GMT <fcorti> ok, fair enough... about the first (source code) the only limitation I see is the github automatic link that is currently broken (will check it)

2016-12-12 09:58:06 GMT <fcorti> about the documentation, I'm pretty sure we will see have some technical delays.

2016-12-12 09:58:48 GMT <fcorti> They are working hard on this 5.2 documentation but the team is not fully working

2016-12-12 10:00:03 GMT <fcorti> oh... if someone is interested (UK area)

2016-12-12 10:00:04 GMT <fcorti> https://www.smartrecruiters.com/Alfresco/98860048-technical-writer

2016-12-12 10:00:06 GMT <alfbot> Title: Alfresco Technical Writer | SmartRecruiters (at www.smartrecruiters.com)

2016-12-12 10:00:08 GMT <fcorti> Let me know ;-)

2016-12-12 10:06:21 GMT <IanW1> fcorti - hoping this one is fixed before GA - https://issues.alfresco.com/jira/browse/ACE-5661

2016-12-12 10:07:29 GMT <fcorti> I see it as opened... I?m afraid it won't be but I have to ask for the final answer

2016-12-12 10:08:24 GMT <Xen_> yreg: my pc crashed can you please share that link again with the alfesco workflow OOTB repo

2016-12-12 10:08:27 GMT <Xen_> please

2016-12-12 10:10:10 GMT <yreg> Xen_, every thing that goes on this channel gets logged in http://chat.alfresco.com

2016-12-12 10:10:11 GMT <alfbot> Title: Logs for #alfresco IRC channel (at chat.alfresco.com)

2016-12-12 10:10:51 GMT <yreg> (unless when the line starts with [nolog])

2016-12-12 10:11:53 GMT <Xen_> oh ok cool ill go and check

2016-12-12 10:12:08 GMT <yreg> Xen_, and when/if you do not find the full log, that means alfbot did not flush its buffer yet, so you might execute :

2016-12-12 10:12:18 GMT <yreg> alfbot flushlog

2016-12-12 10:12:18 GMT <alfbot> yreg: Woooosh, your log has been flushed...

2016-12-12 10:12:49 GMT <yreg> just to make it flush the buffer right away !

2016-12-12 10:12:53 GMT <Xen_> i found it thanks allot

2016-12-12 10:18:06 GMT <IanW1> That would make yet another GA I can't use without adding my own bug fixes

2016-12-12 11:09:55 GMT <Loftux> fcorti: Any updates on when move to gitlab for repository source will take place? Hard to work with our custom builds now when git sync has stopped working (and not going to be fixed according to resplin since moving to gitlab).

2016-12-12 11:10:51 GMT <fcorti> Loftux: we are currently working on it but no deadlines that I know. I'll ask and update on this and back to you.

2016-12-12 11:23:44 GMT <Loftux> fcorti: Thanks. Another question: On what criteria will this be a GA release? I've raised my opinion before that I'm no fan of the EA/GA model, especially since it seem to be just a gut feeling or "GA is due now since we've not had one for long" on what becomes what. So something documented on the criterias used would be appreciated.

2016-12-12 11:24:14 GMT <fcorti> Loftux... interesting

2016-12-12 11:24:23 GMT <fcorti> ok, got it

2016-12-12 11:24:39 GMT <fcorti> Probably it could be a good content for a post

2016-12-12 11:25:45 GMT <Loftux> fcorti: Initially a post for introduction, but also a public document that is followed every time.

2016-12-12 11:27:21 GMT <fcorti> Yes, in the post I imagine the "rules".

2016-12-12 11:27:49 GMT <fcorti> The release note could be the document to inform about every new release (also about exeptions).

2016-12-12 11:54:13 GMT <iblanco> Hi everyone

2016-12-12 11:57:06 GMT <iblanco> I'm doing some customization that requires managing some versioning issues and whenever I have to do such things I feel quite uncomfortable about how Alfresco's/Share's versioning works. And I'm wondering if it's just me that feels like this and I'm getting something wrong.

2016-12-12 11:58:30 GMT <iblanco> Whenever a new content is updated with Share a new version is created, that's ok but what you might expect to be the current version really it isn't, is just the "future version". I'll try to explain.

2016-12-12 11:59:06 GMT <iblanco> I upload "A.pdf", the I upload a new version with file "B.pdf".

2016-12-12 11:59:31 GMT <iblanco> Share says that I have versión 1.0 with the content of A.pdf and 1.1 with the content of B.pdf. So far so good.

2016-12-12 12:01:05 GMT <iblanco> Now I change the description with the "edit properties" option. Everything in share makes me think that I'm changing properties in version 1.1, but that's not true, because version 1.1 is already "frozen" in the version store.

2016-12-12 12:01:49 GMT <iblanco> When now I upload "C.pdf" as version 1.2 a new version is created that does have the description change, but the 1.1 doesn't have the description change reflected.

2016-12-12 12:02:25 GMT <Loftux> iblanco: http://docs.alfresco.com/community/tasks/autoversion-disable.html

2016-12-12 12:02:26 GMT <alfbot> Title: Disabling the auto-versioning feature | Alfresco Documentation (at docs.alfresco.com)

2016-12-12 12:03:32 GMT <Loftux> iblanco: You can select what properties in the edit that will trigger auto-versioning i.e new minor version

2016-12-12 12:04:40 GMT <iblanco> Thanks Loftux, I know that I can disable the autoversion or even make it so that every property change creates a new version.

2016-12-12 12:05:32 GMT <Loftux> iblanco: What if you actually check out the document, edit the properties, upload new version (check in)?

2016-12-12 12:07:10 GMT <iblanco> In fact enabling versioning on all properties changes seems to me to be the only way in which what Share suggest's matches the really, because in this case there is never a discrepancy between current version X.X and the "frozen" version X.X.

2016-12-12 12:08:59 GMT <iblanco> I'm not asking for a solution, I was just wondering if I'm the only one that feels there is something "unclear" about how the versioning works. Is just me?

2016-12-12 12:09:00 GMT <Loftux> So without check-out, the version you upload does note have the property edits, it cannot know about the future edits. why should they be backported? Since a restore version will restore the content and properties, I'm not sure it can work in a different way.

2016-12-12 12:10:18 GMT <iblanco> Well I thingk there would be 2 reasonable aproaches: A) Share shouldn't call the current version with the same label as the already frozen version B) Frozen version should not be created until a new version is started

2016-12-12 12:10:26 GMT <iblanco> well in fact I think both are more or less the same

2016-12-12 12:10:39 GMT <AFaust> iblanco: You are not alone to feel uncomfortable. At the last BeeCon hackathon a few people came together to work on summarizing current issues and potential improvements. Unfortunately time was limited and priorities were somewhere else so the resulting document has not received any updates since.

2016-12-12 12:10:50 GMT <AFaust> https://community.alfresco.com/docs/DOC-6294-versioningimprovements

2016-12-12 12:10:51 GMT <alfbot> Title: VersioningImprovements | Alfresco Community (at community.alfresco.com)

2016-12-12 12:12:37 GMT <Loftux> iblanco: Maybe you can add a feature "Release major" that takes current state including properties and content and just creates next available major version. Then all minor versions are just steps on the way.

2016-12-12 12:13:07 GMT <AFaust> iblanco: One key problem with the suggestion that Share should not display the version label of the frozen version: What version should it display? The app does not yet know what kind of verison the next one will be (major vs. minor)

2016-12-12 12:13:19 GMT <iblanco> AFaust: Thanks I'll give it a look.

2016-12-12 12:15:35 GMT <iblanco> Loftux: Thanks for your suggestion.

2016-12-12 12:24:00 GMT <iblanco> AFaust: I understand that, but if it's not real maybe it would be better just not showing anything. The "current" version is just the "current" version and 1.0, 1.1 are just historic versions that happened some time ago. Just don't pretend that the "live" document is the "version".

2016-12-12 12:25:22 GMT <iblanco> Share right know makes people think that the changes he is doing in "1.1" (or whatever the current version Share says we are in) are part of 1.1 and are not, will be part of a future release.

2016-12-12 12:25:24 GMT <AFaust> Agreed in principle - but often users / managers want to be able to see the (content) version of a document at a quick glance

2016-12-12 12:26:12 GMT <AFaust> And regarding the content of the document the version is actually correct - they are looking at the 1.1 version and when they upload a new content then they will create the 1.2 or 2.0 version

2016-12-12 12:26:30 GMT <AFaust> The confusion only originates from the metadata aspect of the use case

2016-12-12 12:27:13 GMT <AFaust> And if each metadata change would create a new version than it would all be correct / consistent

2016-12-12 12:28:33 GMT <iblanco> AFaust: Yes that's true. From the content point of view is correct.

2016-12-12 12:29:38 GMT <AFaust> And Alfresco has the autoVersionOnProps node property which one might set via a rule / policy to force all version to be consistent even with metadata changes

2016-12-12 12:31:29 GMT <iblanco> AFaust: Yes there are workarounds, like enabling autoVersionOnProps, but soemtimes its just overkill.

2016-12-12 12:32:36 GMT <iblanco> Another issue with the actual approach though is that you can't just update the content of the current version and make the version history consistent. But of course this is something very special.

2016-12-12 12:33:12 GMT <iblanco> For example suppose you have a PDF and a signing action, suppose that you do not consider the signing to mean a new version.

2016-12-12 12:33:30 GMT <iblanco> You just can't do it in a reasonable way.

2016-12-12 12:34:23 GMT <iblanco> If you have you unsigned PDF as version 1.1, when you sign it you'll have to make a 1.2 version because if you just pretend to update the content you are screwed because the frozen 1.1 version is not pointing to the same content.

2016-12-12 12:35:28 GMT <iblanco> I'm not saying that this is something usual or not even stating that not making it an 1.2 version is a good decision, I'm just pointing one of the limitations of the current approach.

2016-12-12 12:39:07 GMT <Loftux> iblanco: I'm thinking that check-out can help here, but then again you don't know if it will be a major/minor version on check-in. So maybe select already at checkout; checkout as major/minor version and it ticks up version id. You do you edits and then check in and it becomes that version. then your signing example can add the signed version (and knowing the version label). Possibly something to add to the "VersioningImprovements" docume

2016-12-12 12:48:14 GMT <Xen_> hi hi im trying to set permissions in my workflow http://pastebin.com/MWy19bAK to only allow a assignee to approve a workflow and not the initiator. by adding this snippet in front of my script in the reviewTask userTask id

2016-12-12 12:48:15 GMT <alfbot> Title: Permissions - Pastebin.com (at pastebin.com)

2016-12-12 12:48:37 GMT <Xen_> is it at the correct place or must it be placed under another userTask

2016-12-12 12:48:54 GMT <Xen_> as i keep on getting script syntax errors

2016-12-12 12:51:33 GMT <Xen_> this is my full definition http://pastebin.com/1dnxKUNU

2016-12-12 12:51:34 GMT <alfbot> Title: full workflow definition - Pastebin.com (at pastebin.com)

2016-12-12 12:58:39 GMT <yreg> Xen_, if I interpret your code right, this should mean that you are breaking inheritance on the attached files, then giving read permissions to the initiator then setting the assignee as owner of the document so that he can make changes to the document

2016-12-12 12:59:48 GMT <yreg> Xen_, the initiator would still be able to execute the task as, according to alfresco's logic, any one has the rights to execute any task in workflows he initiated

2016-12-12 12:59:53 GMT <Xen_> hmmm i want it other way around, the initiator can edit, but not approve, the assignee/reviewer can approve but not edit

2016-12-12 13:00:48 GMT <Xen_> the thing is that piece of code i added doesnt seem to execute at all, i just keep on getting a syntax error

2016-12-12 13:01:17 GMT <yreg> to prevent that, you will need to either override WorkflowService_Security bean, or just implement an extra interceptor on WorkflowService in order to prevent the initiator from updating tasks that are not assigned to him/he is not a candidate user to

2016-12-12 13:02:12 GMT <Xen_> hmmmm any ideas on how to accomplish that

2016-12-12 13:03:33 GMT <Xen_> i saw as default when you install alfresco no one can upload or edit document, only if a set them to Alfersco_Admin, but i dont want to do that.

2016-12-12 13:03:46 GMT <maria_> can i add custom properties on site?

2016-12-12 13:04:19 GMT <maria_> and how they will appear in create/edit site form?

2016-12-12 13:06:16 GMT <Xen_> yreg: where is the WorkflowService located as i cant seem to find it

2016-12-12 13:08:38 GMT <maria_> yreg_ https://github.com/Alfresco/community-edition/tree/master/projects/repository/source/java/org/alfresco/service/cmr/workflow

2016-12-12 13:08:39 GMT <alfbot> Title: community-edition/projects/repository/source/java/org/alfresco/service/cmr/workflow at master · Alfresco/community-edition · GitHub (at github.com)

2016-12-12 13:11:56 GMT <maria_> how can i extend the site type with custom properties?

2016-12-12 13:15:50 GMT <gcampoverde> Hello friends! I'm trying to install a SSL certificate in my Alfresco installation but I don't know how to start. Please, can you provide me some information about it?

2016-12-12 13:19:11 GMT <Xen_> what does this mean: org.activiti.engine.ActivitiException: Exception while invoking TaskListener: Exception while invoking TaskListener: script is a mandatory parameter

2016-12-12 13:23:21 GMT <yreg> Xen_, you probably added a script task listener, but did not provide any script to be executed

2016-12-12 13:23:41 GMT <Xen_> i saw thanx

2016-12-12 13:23:55 GMT <yreg> You will need to either remove that listener or add any instruction to it (a log perhaps) ?

2016-12-12 13:24:22 GMT <Xen_> already did that, jst sorting out my script now

2016-12-12 13:45:25 GMT <dilanhant> Hello. Tell me, is scheduled to release an update to JLAN-server?

2016-12-12 13:48:06 GMT <AFaust> dilanhant: No - as I am sure I must have already commented on community.alfresco.com, the JLAN server is no longer maintained and released as a separate project.

2016-12-12 13:48:26 GMT <AFaust> There has not been any release since 2009

2016-12-12 13:48:55 GMT <AFaust> I mean, fcorti is free to contradict me, but I there is no reason to expect this to change...

2016-12-12 13:51:45 GMT <AFaust> fcorti: One thing you could do is check if a very clear WARNING can be placed on the sourceforge pages for JLAN server. For some reason there are currently a few people trying to work with the old and outdated releases available there, and looking for input via the community platform.

2016-12-12 13:52:38 GMT <Xen_> yreg: i got my workflow to work thanx, i just want to find out one thing, when you do a clean install, none of the users can upload or edit any docs, apart from giving everyone admin rights, how can i assign properties to users to be able to upload and edit docs

2016-12-12 13:53:12 GMT <AFaust> fcorti: Talking about https://sourceforge.net/projects/alfresco/files/JLAN/

2016-12-12 13:54:25 GMT <yreg> Xen_, you can use the Permissions doclib action to set specific permissions on specific nodes

2016-12-12 13:54:54 GMT <Xen_> do you have a link so i can look it up

2016-12-12 13:55:07 GMT <yreg> and by default, I am pretty sure every one has Manager right over his home folder + Contributor right over the shared folder

2016-12-12 13:55:28 GMT <yreg> google "alfresco share permission" and see what you get

2016-12-12 13:55:51 GMT <AFaust> It has 15 weekly downloads, so people strangely seem to be fine with dusty software. (Alfresco is using an outdated, broken JSON library from 2009, so the same bewilderment applies there as well)

2016-12-12 13:57:32 GMT <Xen_> hmmmmm so if i place all our repo folders inside the share folder my issue is resolved, wonderful

2016-12-12 13:58:41 GMT <yreg> Xen_, depending on your usecase there is probably a better solution

2016-12-12 13:58:55 GMT <yreg> Share sites can be one of them

2016-12-12 13:59:04 GMT <Xen_> we dont use that

2016-12-12 13:59:07 GMT <Xen_> only repos

2016-12-12 13:59:47 GMT <maria_> how can i extend the site content with custom properties? what do i need to do?

2016-12-12 14:00:08 GMT <maria_> (the create/ edit form of site)

2016-12-12 14:00:25 GMT <dilanhant> Probably in 2009, the community was not sufficiently developed to promote Jlan-server in Open Source.

2016-12-12 14:01:57 GMT <dilanhant> No analogues so far for Jlan-server.

2016-12-12 14:02:36 GMT <maria_> on one hand i could add aspect, etc, but what about edit-site.get.html.ftl and create-site.get.html.ftl?

2016-12-12 14:03:04 GMT <maria_> do i need to overide them?

2016-12-12 14:07:12 GMT <yreg> ___Dave, I am trying to port some share customizations to 5.1.1

2016-12-12 14:07:24 GMT <___Dave> ok

2016-12-12 14:07:28 GMT <yreg> and I am hitting a strange issue with select2 not working

2016-12-12 14:07:34 GMT <yreg> after digging a bit

2016-12-12 14:08:18 GMT <yreg> I think Aikau is loading a newer version of jQuery 1.11.x which is wiping the old one 1.8.2

2016-12-12 14:08:37 GMT <___Dave> ok, interesting... what version of Aikau are you on?

2016-12-12 14:08:52 GMT <___Dave> what are you customizing?

2016-12-12 14:09:01 GMT <yreg> it should be the default, let me check

2016-12-12 14:09:25 GMT <yreg>

2016-12-12 14:10:01 GMT <___Dave> the version of JQuery that Aikau loads should be imported as an AMD dependency, so I would hope it's scoped to where it's used and shouldn't pollute the global namesapce

2016-12-12 14:11:02 GMT <yreg> I am porting an old doclib multiple items action that creates a dialog form ...

2016-12-12 14:12:29 GMT <yreg> And when I breakpoint inside a js snippet from my select2 form control and try to check the value of : $.fn.jquery I get 1.11.1

2016-12-12 14:13:04 GMT <___Dave> what is the "select2" form control?

2016-12-12 14:13:13 GMT <___Dave> is that a 3rd party control?

2016-12-12 14:14:05 GMT <yreg> Yes, it appears that this was done a while ago

2016-12-12 14:15:28 GMT <___Dave> I'm not sure what to suggest to be honest

2016-12-12 14:15:56 GMT <___Dave> can this code be updated to make use of the newer version of JQuery?

2016-12-12 14:18:18 GMT <yreg> I probably can find a newer version of the library that works for 1.11.1

2016-12-12 14:18:52 GMT <yreg> but I will need to make it load after jQuery

2016-12-12 14:19:01 GMT <___Dave> right, I see what you mean

2016-12-12 14:19:15 GMT <yreg> and I do not want to a js import inside my control

2016-12-12 14:20:02 GMT <yreg> any way you can recommend to import that new js in a way that it gets loaded after jQuery ?

2016-12-12 14:21:06 GMT <___Dave> well, JQuery is imported by the main Page.js module

2016-12-12 14:21:26 GMT <___Dave> so it would just need to go after whatever Surf component / markup section that is building the Aikau content

2016-12-12 14:21:38 GMT <___Dave> so that would be dependant upon the page

2016-12-12 14:22:47 GMT <yreg> that would be 3 pages : repository, site doclib and advanced search

2016-12-12 14:23:21 GMT <___Dave> all 3 of which will just have the header component for Aikau content

2016-12-12 14:23:42 GMT <___Dave> so an extension would want to import the JavaScript dependency after that header component markup location

2016-12-12 14:25:25 GMT * DarkStar1 bids you all a Good <insert_local_time_of_day> :)

2016-12-12 14:27:10 GMT <DarkStar1> hey douglascrp.

2016-12-12 14:27:25 GMT <douglascrp> DarkStar1, hey man

2016-12-12 14:27:33 GMT <douglascrp> how are you?

2016-12-12 14:28:13 GMT <DarkStar1> douglascrp: Good.

2016-12-12 14:35:22 GMT <yreg> ___Dave, after second though, it looks like that jQuery is not loaded directly from within an HTML

2016-12-12 14:35:43 GMT <yreg> it is actually dojo.js that loads it

2016-12-12 14:36:16 GMT <yreg> an wherever I move my import, I will still get the same issue probably

2016-12-12 14:36:42 GMT <___Dave> Dojo is probably only loading it because it's a dependency of Page.js

2016-12-12 14:36:50 GMT <___Dave> and therefore it's going through the Dojo AMD loader

2016-12-12 14:40:07 GMT <yreg> I found a reference to it in an packages of the dojoConfig

2016-12-12 14:46:36 GMT <___Dave> yes, that's the configuration set up by Aikau

2016-12-12 14:46:48 GMT <___Dave> it defines the locations of all the modules

2016-12-12 14:47:04 GMT <___Dave> module roots I mean

2016-12-12 14:50:42 GMT <DarkStar1> It's been a while so excuse my asking, is there an SDK that has an amp project that with solr for indexing?

2016-12-12 14:53:34 GMT <fcorti> Sorry AFaust, jumping in several meetings

2016-12-12 14:53:54 GMT <AFaust> np

2016-12-12 14:54:06 GMT <AFaust> I am aware of the channel rules to "wait a couple of hours"

2016-12-12 14:54:26 GMT <fcorti> yes, but I'm a polite guy

2016-12-12 14:54:27 GMT <fcorti> :-)

2016-12-12 14:54:34 GMT <fcorti> coming to your question

2016-12-12 14:54:56 GMT <fcorti> yes, it's fair to put something to say: dated

2016-12-12 14:55:03 GMT <fcorti> or a link to comment or something

2016-12-12 14:55:06 GMT <fcorti> I take a note

2016-12-12 15:01:14 GMT <fcorti> Loftlux: about your question below.

2016-12-12 15:01:15 GMT <fcorti> On what criteria will this be a GA release? I've raised my opinion before that I'm no fan of the EA/GA model, especially since it seem to be just a gut feeling or "GA is due now since we've not had one for long" on what becomes what. So something documented on the criterias used would be appreciated

2016-12-12 15:02:25 GMT <fcorti> The reply is that the release note document should contain this description...

2016-12-12 15:02:28 GMT <fcorti> something like:

2016-12-12 15:02:37 GMT <fcorti> It is feature complete and we have started stabilization testing.

2016-12-12 15:03:23 GMT <fcorti> If you are asking this question.. it's because probably it is not clear anough

2016-12-12 15:03:28 GMT <fcorti> so we are gong to it beter

2016-12-12 15:03:46 GMT <Loftux> For me that a feature is not there does not make it EA

2016-12-12 15:04:53 GMT <Loftux> What does not exist does not make it non-production. So that new features comes into place does not suddenly make it GA, maybe the contrary.

2016-12-12 15:06:44 GMT <Loftux> So again, it is GA just because it seems like good timing.

2016-12-12 15:09:38 GMT <fcorti> Probably it's not clearly explained but "it is feature complete" means "fully defined with all the features avialable"

2016-12-12 15:09:43 GMT <AFaust> But how is that different from the previous Major.Minor.a > Major.Minor.b > Major.Minor.c etc. progression? All labeled releases until the last essentially were EAs...

2016-12-12 15:10:00 GMT <AFaust> And stabilization of features continued throughout...

2016-12-12 15:10:22 GMT <Loftux> Which is fine. I just think that EA/GA only confuses. If it passes test and has NOT any very new features, then it can be released (without EA/GA labels). With the current system you make users afraid to use. Maybe the should be, I don't know.

2016-12-12 15:13:54 GMT <AFaust> I don't know how the labeling could be handled differently to still provide some kind of differentiation for "we know this might be unstable" and "this should generally work"

2016-12-12 15:15:12 GMT <AFaust> If EA/GA differentiation is dropped, more users might unknowingly use a release that is very early in the development stages and dismiss Alfresco as an unstable product if they encounter some issues that may naturally occur due with such a EA build...

2016-12-12 15:16:34 GMT <AFaust> And I don't believe Alfresco will ever drop the business differentiation that Enterprise gets most of the QA while Community is tested "lightly"

2016-12-12 15:21:05 GMT <IanW1> I do think it's quite useful to have the EA/GA distinction but the danger is that it's possible to think that the GA version is better tested than it is

2016-12-12 15:22:36 GMT <IanW1> To me the GA designation implies some form of quality assurance but observations now lead me to think that perhaps it means more like feature complete

2016-12-12 15:23:15 GMT <IanW1> I did write a blog on roughly this subject http://tech.wrighting.org/2016/06/upgrade-time/

2016-12-12 15:23:16 GMT <fcorti> ...and we have started stabilization testing

2016-12-12 15:23:17 GMT <alfbot> Title: Upgrade time? Thoughts about technical things (at tech.wrighting.org)

2016-12-12 15:28:47 GMT <IanW1> It's a shame Community can't have one? more release per cycle dedicated to bug fixes although I accept that's part of the Enterprise differentiation (in addition to the extra features that are in Enterprise) - it might help avoid having two GAs in quick succession....

2016-12-12 15:30:37 GMT <fcorti> I think it's a value to be able to preview the features at least one time per month... but this is my personal opinion

2016-12-12 15:35:37 GMT <IanW1> Feature preview is valuable and it's great to have that - the thing is, if you're using Community, you need to know when it's a good time to upgrade

2016-12-12 15:51:50 GMT <iblanco> AFaust: I've added to your versions document the need for the developers to be able to update content without creating a new version in a versioned document.

2016-12-12 16:01:44 GMT <Loftux> AFaust: "we know this might be unstable" is nightlys. "this should generally work" is a release. I don't see the point of EA/beta releases at all. I'm ok with a release where they point out new features such as the coming release with linking support to be new and risk of less tested, but good enough not to break the entire install.

2016-12-12 16:07:15 GMT <AFaust> nightlies are "we definitely know these might be unstable"

2016-12-12 16:07:44 GMT <AFaust> I do see a value in EA releases at certain milestones / features being added (should also be planned ahead and defined with conditions)

2016-12-12 16:09:24 GMT <AFaust> And I do see the necessity to differentiate these releases from those that less tech-savvy users should consider as "stable enough" releases

2016-12-12 16:16:50 GMT <Loftux> The less tech-savvy are the ones I'm thinking of, we don't help them with this EA/GA. It is just confusion if it can be used or not. A release is something that can be dowloaded and used. If not, it should not be released. But I guess I'm alone in this thinking.

2016-12-12 16:25:26 GMT <gcamp> Hello, Can some one help me ?

2016-12-12 16:29:49 GMT <yreg> ___Dave, I ended up modifying the jquery import I had with the file aikau ships, and that solved my issue

2016-12-12 20:19:06 GMT <Xiomin> Hello. can someone help me ?

End of Daily Log

The other logs are at http://esplins.org/hash_alfresco