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.
2019-03-29 08:44:00 GMT <hi-ko> Hi AFaust, feedback for my working / not working activity post issue: its an issue of the implementation done in a front end manner rather than in a backend manner as I expected.
2019-03-29 08:44:23 GMT <alfresco-discord> <dgradecak> do not say we did not tell it 😉
2019-03-29 08:45:24 GMT <hi-ko> The activity post entry is beeing created by a XHR request on /share/proxy/alfresco/slingshot/doclib/activity !!!
2019-03-29 08:46:08 GMT <hi-ko> If a user navigates to the same directory by the repository path no post is beeing created ...
2019-03-29 08:46:53 GMT <hi-ko> damn - looks like alfresco hired "full stack" developers ;-)
2019-03-29 08:47:20 GMT <hi-ko> same grap like in the rendition implementation
2019-03-29 08:47:26 GMT <alfresco-discord> <dgradecak> I would say that it is like "evolved" development
2019-03-29 08:47:42 GMT <alfresco-discord> <dgradecak> devlopment 3.0 😉
2019-03-29 08:48:25 GMT <hi-ko> why do we need behavior if we could code everything in the front end? ;-)
2019-03-29 08:48:36 GMT <alfresco-discord> <dgradecak> so that you have something to do
2019-03-29 08:48:55 GMT <alfresco-discord> <dgradecak> otherwise why would people engage "us" 😄
2019-03-29 08:50:32 GMT <alfresco-discord> <dgradecak> any idea if there is a way to get a property of the node being deleted in BeforeDeleteNodePolicy or any other policy?
2019-03-29 08:50:33 GMT <hi-ko> I'd prefer create new stuff instead of spent so mucht time in fixing architecture things.
2019-03-29 08:51:13 GMT <hi-ko> what is the issue with BeforeDeleteNodePolicy?
2019-03-29 08:52:16 GMT <alfresco-discord> <dgradecak> in such a behavior there is a "read of a property" but of course it does not work since the public NodeService checks the "deleted = true"
2019-03-29 08:52:47 GMT <alfresco-discord> <dgradecak> now I wonder how to intercept that delete just before it is deleted actually ... maybe some other private services
2019-03-29 08:53:58 GMT <angelborroy> I don’t remember the behaviour in that way
2019-03-29 08:54:24 GMT <angelborroy> Anyway, as workaround, you can create a new transaction just to gather the properties you need
2019-03-29 08:54:25 GMT <alfresco-discord> <dgradecak> that was my bet too
2019-03-29 08:54:53 GMT <angelborroy> it’s not an elegant solution, but it will work
2019-03-29 08:54:56 GMT <alfresco-discord> <dgradecak> hm ... could work but ...
2019-03-29 08:57:12 GMT <hi-ko> sounds like create for every transaction another transaction to work around DeleteNodePolicy behavior :-(
2019-03-29 08:57:28 GMT <alfresco-discord> <dgradecak> yep ... transaction isolation is great 😃
2019-03-29 08:57:39 GMT <angelborroy> I know, I said it was not a good solution
2019-03-29 08:57:57 GMT <alfresco-discord> <dgradecak> will try to find another way, I am sure AFaust would have a different way, but he must be sleeping 😉
2019-03-29 08:57:59 GMT <angelborroy> It seems weird that Alfresco will not give you access to properties when OnBeforeDelete
2019-03-29 08:58:05 GMT <alfresco-discord> <dgradecak> indeed
2019-03-29 08:58:34 GMT <alfresco-discord> <dgradecak> since the doc says: "Called before a node is deleted."
2019-03-29 08:59:13 GMT <alfresco-discord> <dgradecak> hm maybe it has to do with the notification frequency, I see it is on TRANSACTION_COMMIT
2019-03-29 09:00:04 GMT <angelborroy> right
2019-03-29 09:00:13 GMT <angelborroy> you can use FIRST_EVENT
2019-03-29 09:00:25 GMT <alfresco-discord> <dgradecak> yes, trying that
2019-03-29 09:00:32 GMT <angelborroy> https://angelborroy.wordpress.com/2015/05/22/alfresco-implementing-delete-behavior/
2019-03-29 09:00:33 GMT <alfbot> Title:Alfresco – Implementing delete behavior | Programming and So (at angelborroy.wordpress.com)
2019-03-29 09:00:43 GMT <angelborroy> You have access to node properties if you use FIRST_EVENT
2019-03-29 09:00:56 GMT <alfresco-discord> <dgradecak> sounds logical
2019-03-29 09:02:15 GMT <alfresco-discord> <dgradecak> in your post, why are you using a tx listener? just curious?
2019-03-29 09:02:27 GMT <alfresco-discord> <dgradecak> since it is already bound to the tx
2019-03-29 09:02:41 GMT <angelborroy> to make an operation afterCommit
2019-03-29 09:03:49 GMT <alfresco-discord> <dgradecak> of course it was because of the notif. freq.
2019-03-29 09:04:54 GMT <alfresco-discord> <dgradecak> I see for the after commit, could use an async rule (kidding a bit)
2019-03-29 09:05:03 GMT <alfresco-discord> <dgradecak> sorry async action
2019-03-29 09:05:15 GMT <angelborroy> right
2019-03-29 09:14:15 GMT <AFaust> dgradecak: Not sure I understand why you cannot read a property on BeforeDelete - I do that quite often...
2019-03-29 09:15:09 GMT <hi-ko> but not on reading properties after TRANSACTION_COMMIT ;-)
2019-03-29 09:15:20 GMT <AFaust> No, not sleeping, just busy getting some functionality working that has to deal with dynamic name/address resolution between different, network isolated + NATed Docker instances...
2019-03-29 09:15:44 GMT <AFaust> Well, who in the world would be so crazy to use TRANSACTION_COMMIT?
2019-03-29 09:16:09 GMT <AFaust> Oh wait... everyone listening to Alfresco recommendations instead of what is sensible...
2019-03-29 09:16:57 GMT <hi-ko> and who was so crazy to combine NATed docker instances ? ;-)
2019-03-29 09:17:02 GMT <AFaust> Ok, I actually skipped over the line where dgradecak said he was using commit...
2019-03-29 09:17:37 GMT <AFaust> With NATed Docker instances I meant the normal address translation that Docker already does...
2019-03-29 09:18:34 GMT <hi-ko> sure - in our containers we run the tiers directly bridge like a vm
2019-03-29 09:19:23 GMT <hi-ko> if the container is meant as a server service not as a developer local running instance
2019-03-29 09:22:47 GMT <hi-ko> btw: we asked > 20 Alfresco customers and only 1 is interested in running docker/containers in production, but this one revoked his decision since the guy with container and kubernetes knowlege left the organisation ;-)
2019-03-29 09:57:54 GMT <alfresco-discord> <dgradecak> I was not using that:) I was changing the old code hehe
2019-03-29 09:58:05 GMT <alfresco-discord> <dgradecak> or legacy code 😉
2019-03-29 10:20:35 GMT <alfresco-discord> <dgradecak> btw, I am really following why TX_COMMIT is that wrong in your opinion AFaust, although I read your "posts" about that anyhow, I also think that the FIRST_EVENT is needed to be used in cases of auto versioning ant this kind of delete (where access to the node properties is required) but for the rest TX_COMMIT I never had issues,
2019-03-29 10:21:12 GMT <alfresco-discord> <dgradecak> I am not saying there was client's existing code that did not have issues due to the underlying logic that does not belong into a behavior
2019-03-29 10:22:18 GMT <AFaust> I can't remember when I last used FIRST_EVENT either. For me, only EVERY_EVENT is the "right" event.
2019-03-29 10:23:28 GMT <AFaust> And TRANSACTION_COMMIT is not "wrong" per se, it just makes it extremely easy for most people to get it right. Obviously people who worked with Alfresco for a long time should not have that many issues with it.
2019-03-29 10:23:46 GMT <AFaust> extremely easy to get right => extremely easy to shoot themselves in the foot
2019-03-29 10:26:20 GMT <alfresco-discord> <dgradecak> that makes sense
2019-03-29 11:13:09 GMT <alfresco-discord> <FZeller> @angel.borroy Just wanna thank you again, the solr cross locale solved my problem with full indexing file copied from aos drive.
2019-03-29 11:13:53 GMT <angelborroy> @FZeller thanks for the feedback
2019-03-29 11:14:12 GMT <angelborroy> I something we have to improve for next releases
2019-03-29 11:14:30 GMT <angelborroy> Documentation states “Optional” but it should by “Mandatory” for many users in EU
2019-03-29 11:37:37 GMT <AFaust> angelborroy: Are you guys really, finally going to fix that?
2019-03-29 11:37:53 GMT <angelborroy> I’ll try
2019-03-29 11:38:09 GMT <angelborroy> But they (still) don’t see this as a “real” problem
2019-03-29 11:38:10 GMT <AFaust> Is it just because you now bring the non-English influence to the table, or did our complaints from Twitter / DevCon 2 years ago finally have an effect?
2019-03-29 11:38:19 GMT <angelborroy> I know
2019-03-29 11:38:43 GMT <angelborroy> Let me gain more strength inside the Team ;-)
2019-03-29 11:45:27 GMT <angelborroy> Next April 9, I’m going to deliver a presentation (or probably 2, as Ole is missing) at Seville Meetup
2019-03-29 11:45:59 GMT <angelborroy> My presentation is about configuring Search Services properly for multi-locale
2019-03-29 11:46:25 GMT <angelborroy> Probably I’m going to provide some Docker template to help people to start with this
2019-03-29 12:38:52 GMT <alfresco-discord> <digcat> can we not roll the config into the community version, so people dont have to waste brain cells on it, so it just works ?
2019-03-29 14:04:46 GMT <alfresco-discord> <AHT> Im following step by step :Writing a Custom Transformer chapter in a jeff potts book called "Alfresco developer guide" and nothing works 😦
2019-03-29 14:05:34 GMT <angelborroy> This project is more or less the same
2019-03-29 14:05:35 GMT <angelborroy> https://github.com/keensoft/alfresco-zip-previewer
2019-03-29 14:05:36 GMT <alfbot> Title:GitHub - keensoft/alfresco-zip-previewer: Alfresco ZIP and RAR entries preview for Share (at github.com)
2019-03-29 14:05:39 GMT <angelborroy> Hope it helps
2019-03-29 14:06:43 GMT <alfresco-discord> <AHT> yep I found some solution in your repo.. so just startet to follow you in git... now im your stalker 😛
2019-03-29 14:06:48 GMT <alfresco-discord> <AHT> thnks a lot 😄
2019-03-29 14:07:24 GMT <alfresco-discord> <AHT> the book example was great becouse it was just what i need.. a little integration of Ms project (mpp) with alfresco ) 😃
2019-03-29 14:07:38 GMT <alfresco-discord> <AHT> i will check that thanks again 😄
2019-03-29 14:07:45 GMT <angelborroy> There should be a small changes...
2019-03-29 14:07:57 GMT <angelborroy> … Jeff material is great, but probably is some outdated
2019-03-29 14:08:21 GMT <alfresco-discord> <AHT> I started to learn alfresco with jeff blog.. it was my bible 😛
2019-03-29 15:03:26 GMT <alfresco-discord> <ohej> @dgradecak , @angel.borroy @digcat Just following up on the conversation about the Transform Service. The Transform Services is Enterprise Only at this point in time. We still have the Renditions APIs available and doing transformations like we've always done is still fully supported. Now for a twist of events, we announced in the 6.1 release notes that the rendition services are deprecated. This puts
2019-03-29 15:03:27 GMT <alfresco-discord> us in a pickle because if we then remove it, we effectively remove the option for renditions and transformations inside Community Edition. I cannot stress this enough: This is NOT the intention. If we can make a business decision to make the Transform Service available to community, we will go ahead and phase out the rendition service. However this is a long term conversation and it's not clear which direction we
2019-03-29 15:03:27 GMT <alfresco-discord> will go. Hope this clear things up a bit?
2019-03-29 15:30:43 GMT <hi-ko> ohej: Ouch - it looks more and more like Alfresco CE will become a cool car without wheels, windows and steering wheel. So we should focus on checking if it's worth to keep the engine ...
2019-03-29 15:31:21 GMT <angelborroy> I strongly disagree with ohej message
2019-03-29 15:31:30 GMT <angelborroy> But, obviously, I’m just a developer
2019-03-29 15:31:30 GMT <alfresco-discord> <digcat> @ohej thank you for the update, of course I hope the decision is to open up the transformation stuff to community so we can help test it in many ways, of course the sales team need to be less insecure in their understanding of open source,
2019-03-29 15:33:20 GMT <angelborroy> -= THIS MESSAGE NOT LOGGED =-
2019-03-29 15:33:56 GMT <alfresco-discord> <digcat> +1 to that 😃
2019-03-29 15:37:29 GMT <hi-ko> @angelborroy: maybe we get this somehow easier: we developed for 2 huge Alfresco systems our smart transformer to scale up transformation with Aflresco and since devcon we are thinking if and how to put that to the public.
2019-03-29 15:37:53 GMT <angelborroy> nice
2019-03-29 15:37:54 GMT <hi-ko> Removal means also breaking Share
2019-03-29 15:38:18 GMT <angelborroy> Share is broken (internally) since 206
2019-03-29 15:38:22 GMT <angelborroy> 206 > 2016
2019-03-29 15:38:35 GMT <alfresco-discord> <digcat> isnt that just cos the devs all left ?
2019-03-29 15:38:51 GMT <hi-ko> but the only visible client here in german speaking countries
2019-03-29 15:38:51 GMT <angelborroy> I don’t know the cause
2019-03-29 15:39:37 GMT <alfresco-discord> <digcat> i know share is using YUI which has been discontinued by yahoo,
2019-03-29 15:39:43 GMT <hi-ko> my feeling is alfresco never had expertise in UI and starts again and again and ...
2019-03-29 15:40:00 GMT <angelborroy> Share is using YUI 2.9.0
2019-03-29 15:40:11 GMT <angelborroy> This is not discontinued, this is prehistoric
2019-03-29 15:40:46 GMT <hi-ko> this having said: there is no working alternative until now.
2019-03-29 15:40:52 GMT <alfresco-discord> <digcat> ahh yes, yui 3
2019-03-29 15:42:45 GMT <hi-ko> ecm implementation means you need a client for the most common use cases to be configured. Only a very few companies are willing to take a "framework" to develop their own client. because TCO is much to high
2019-03-29 15:43:54 GMT <hi-ko> so if you say Share is dead: what is the alternative as a ready to go client having required extension points for different solutions to be combined?
2019-03-29 15:44:04 GMT <angelborroy> ACA or ADF
2019-03-29 15:44:49 GMT <hi-ko> but this is a framework not a product
2019-03-29 15:45:24 GMT <angelborroy> ACA is a "product"
2019-03-29 15:45:36 GMT <hi-ko> without extension points
2019-03-29 15:45:38 GMT <angelborroy> For Enterprise “we” call ACA ADW
2019-03-29 15:45:42 GMT <angelborroy> ACA has extension points
2019-03-29 15:46:06 GMT <angelborroy> https://alfresco-content-app.netlify.com/#/extending/
2019-03-29 15:46:07 GMT <alfbot> Title:Alfresco Content App (at alfresco-content-app.netlify.com)
2019-03-29 15:50:19 GMT <hi-ko> this is worth a deeper look but on the other hand if this is not available (even for money) for CE the market is much to small to develop solutions using these extension points. We had this discussion for Explorer and Share.
2019-03-29 15:53:46 GMT <hi-ko> <angelborroy
2019-03-29 15:54:51 GMT <hi-ko> angelborroy: will extension for ACA and ADW be compatible (CE/EE)?
2019-03-29 15:55:10 GMT <angelborroy> Sure
2019-03-29 15:55:14 GMT <angelborroy> At least, now
2019-03-29 15:55:24 GMT <angelborroy> Both are (basically) the same thing
2019-03-29 15:55:29 GMT <angelborroy> At least by now
2019-03-29 15:55:39 GMT <alfresco-discord> <yreg> hi-ko AFAIK, ADW is nothing more than ACA + a couple of extensions on top ...
2019-03-29 15:55:48 GMT <angelborroy> right
2019-03-29 15:56:54 GMT <hi-ko> the main pain will be to get a pendant to the Sites which is beeing used as the most important feature in building teams in projects
2019-03-29 15:57:59 GMT <alfresco-discord> <yreg> and last I checked you could even develop your extensions separately, publish them to an npm registry (nexus3 has that capability) and have them added to any ACA project simply by adding few lines to the packages.json and app.extensions.json ....
2019-03-29 15:58:17 GMT <alfresco-discord> <yreg> which sounds like a way cleaner solution than the way we extend share
2019-03-29 15:58:59 GMT <alfresco-discord> <yreg> on the other hand the extension mechanism is still quite limited and needs to be used so missing usecases are raised and addressed ...
2019-03-29 16:01:48 GMT <alfresco-discord> <yreg> we've been collaborating with ADF team feeding them feedback about missing features we encountred while trying to craft our own set of ACA extensions tailored for case-management use-cases, and I can say with confidence that ADF team was quite collaborative and receptive for the critics/suggestions we gave ...
2019-03-29 16:03:01 GMT <alfresco-discord> <yreg> they are a bit down on firepower though, so things are evolving a bit slowly ....
2019-03-29 16:03:53 GMT * AFaust has had quite a different experience concerning receptiveness with one answer at DevCon Q&A being only a thinly veiled, polite variants of "f*** off"
2019-03-29 16:06:40 GMT <alfresco-discord> <yreg> fall off ??
2019-03-29 16:07:14 GMT <AFaust> I'll let you go through the entire list of words starting with an "f" that match that pattern...
2019-03-29 16:08:07 GMT <angelborroy> I remember that
2019-03-29 16:08:26 GMT <angelborroy> Basically you were not making a question, you were writing a blog post :D
2019-03-29 16:08:30 GMT <angelborroy> That one, right?
2019-03-29 16:12:08 GMT <AFaust> The original question was a single sentence. Unfortunately in their limited view of the world they did not understand it, so it required a longer explanation from my side...
2019-03-29 16:21:19 GMT <alfresco-discord> <digcat> @angel.borroy on a different point have you been able to pick up any vibrations about solrs version, moving to 7 or waiting on 8
2019-03-29 16:28:33 GMT <hi-ko> anyhow - if this is the environment alfresco delivers we should find a constructive way to work with it and to bring it forward. It's easier to team and extend a product step by step than to work with an overengeneered one full of concept bugs ;-)
2019-03-29 16:29:42 GMT <hi-ko> which does not mean we need a strong product management beeing able to involve the commumity.
2019-03-29 16:29:49 GMT <hi-ko> have a nice WE!
2019-03-29 18:34:46 GMT <alfresco-discord> <angel.borroy> @digcat waiting for 8
The other logs are at http://esplins.org/hash_alfresco