Daniele Baggio 8 Years Ago Good, finally someone smart like you solves this annoying missing feature.But the mistery remains..why it was missing? Please sign in to reply. Reply as... Cancel Jan Eerdekens Daniele Baggio 8 Years Ago Thank you and that's a great question! I guess they haven't had a need for it and ordered/sorted their articles in some other way? Would be nice to hear from someone at Liferay what the actual reason is. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi guys, I am sorry I can not solve the mistery either, but I guess that the priority was added to asset publisher at some point as part of the asset framework but none of the apps is leveraging it so far. As you mentioned, this would be really easy to include in the product itself. Jan, would you be willing to contribute this feature to the Portal for 7.0? I would be very happy to review your pull request! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago @Julio:I definitely would like to give it a try, but I guess you want it integrated in Liferay and not as a hook like it is now? Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi Jan, yes, that would be awesome. Otherwise, if it gets complicated, send me what you can do and I will adapt it. I have created a Story so that we can keep track of this improvement: https://issues.liferay.com/browse/LPS-58412Thank you! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Jan Eerdekens Daniele Baggio 8 Years Ago Thank you and that's a great question! I guess they haven't had a need for it and ordered/sorted their articles in some other way? Would be nice to hear from someone at Liferay what the actual reason is. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi guys, I am sorry I can not solve the mistery either, but I guess that the priority was added to asset publisher at some point as part of the asset framework but none of the apps is leveraging it so far. As you mentioned, this would be really easy to include in the product itself. Jan, would you be willing to contribute this feature to the Portal for 7.0? I would be very happy to review your pull request! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago @Julio:I definitely would like to give it a try, but I guess you want it integrated in Liferay and not as a hook like it is now? Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi Jan, yes, that would be awesome. Otherwise, if it gets complicated, send me what you can do and I will adapt it. I have created a Story so that we can keep track of this improvement: https://issues.liferay.com/browse/LPS-58412Thank you! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Julio Camarero Jan Eerdekens 8 Years Ago Hi guys, I am sorry I can not solve the mistery either, but I guess that the priority was added to asset publisher at some point as part of the asset framework but none of the apps is leveraging it so far. As you mentioned, this would be really easy to include in the product itself. Jan, would you be willing to contribute this feature to the Portal for 7.0? I would be very happy to review your pull request! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago @Julio:I definitely would like to give it a try, but I guess you want it integrated in Liferay and not as a hook like it is now? Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi Jan, yes, that would be awesome. Otherwise, if it gets complicated, send me what you can do and I will adapt it. I have created a Story so that we can keep track of this improvement: https://issues.liferay.com/browse/LPS-58412Thank you! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Jan Eerdekens Julio Camarero 8 Years Ago @Julio:I definitely would like to give it a try, but I guess you want it integrated in Liferay and not as a hook like it is now? Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago Hi Jan, yes, that would be awesome. Otherwise, if it gets complicated, send me what you can do and I will adapt it. I have created a Story so that we can keep track of this improvement: https://issues.liferay.com/browse/LPS-58412Thank you! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Julio Camarero Jan Eerdekens 8 Years Ago Hi Jan, yes, that would be awesome. Otherwise, if it gets complicated, send me what you can do and I will adapt it. I have created a Story so that we can keep track of this improvement: https://issues.liferay.com/browse/LPS-58412Thank you! Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio, It took me quite some time to get liferay-portal cloned... but I got there in the end. Now I'm looking for some information about building Liferay 7, but can't seem to find a lot. I think I found a good place to add the priority stuff in the existing code, the updateAsset method in the Journal Service stuff, but now I'm wondering how to only get my small changes deployed without needing to do ant all? Is there a way to build and update/refresh a certain module? Please sign in to reply. Reply as... Cancel
Jan Eerdekens Julio Camarero 8 Years Ago Hi Julio,I managed to get a bit further and found out how to only build/deploy a module. I think I can solve the priority stuff by changing the updateAsset method signature in the Journal module to have a priority parameter. This also means I have to change the Asset service a bit so that it accepts a Double priority instead of an Integer (strange choice as the priority field is already a double).With these changes I'm able to retrieve the priority from the serviceContext when a journal article is added/updated, pass it onto the updateAsset which will pass it on to the existing AssetEntry stuff (now just as a Double instead of an Integer).I also found out I can add the priority menu item using 2 portal properties instead of overwriting a JSP (something I will have to change in my blog post).So getting there... slowly. Please sign in to reply. Reply as... Cancel Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Julio Camarero Jan Eerdekens 8 Years Ago And thanks to Jan, this feature will be part of Liferay 7!! Thanks a ton Jan, your contribution was awesome! https://issues.liferay.com/browse/LPS-58412It will actually be available in the Alpha Release that will be published in the next weeks. Please sign in to reply. Reply as... Cancel Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Julio Camarero Julio Camarero 8 Years Ago By the way, if anyone wants to contribute the priority field to other entities (documents, bookmarks, blog entries...) we will be extremely happy to accept that contribution ;) Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Olivier Fock Si Ming Julio Camarero 8 Years Ago I have added support in my own project for documents priority, but it was much trickier because of the order Liferay creates asset entries after each document. However the big problem in 6.2.x is that the values for priority is not imported / exported in LAR (therefore staging is affected as well). I would really appreciate a backport of this feature for 6.2.x. Cheers Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel
Julio Camarero Olivier Fock Si Ming 8 Years Ago Hi Olivier, thanks for your feedback!Can you explain the problem you had with documents? Would you be willing to contribute that? It should be much easier after Jan's changes.Regarding the Export/Import, that is a very good point. I am not sure we even did that for 7.0... I will check that out!Regarding the backport, we never backport features to previous branches. Only bug fixes. You can achieve this feature using a hook for 6.2.x though, as Jan explained in this post. Thanks a lot!! Please sign in to reply. Reply as... Cancel Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel
Olivier Fock Si Ming Julio Camarero 8 Years Ago Hi Julio,The case with web content is straightforward just override the method addArticle and updateArticle of JournalArticleLocalService.For Documents, while updateFileEntry in DLFileEntryLocalService does the trick, overriding addFileEntry does not work because when the method finishes the asset related to the file entry does not yet exist. The assets are created in a higher level service, so I add to override addFileEntry of DLAppService.Anyway, this feature is unusable for me since I use staging, these values are not kept. Unless you know a way to extend the behavior of staging/LAR ?Thank you. Please sign in to reply. Reply as... Cancel Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel
Julio Camarero Olivier Fock Si Ming 8 Years Ago Thank you Olivier, I think you did the right thing with the DLApp Service. Will you be willing to contribute that as Jan did with Web Content? We will review your changes and make sure they work, so don't worry if you are not sure if they are correct.Regarding the import/export, I just verified it is currently not exported/imported in 7.0 either. We are going to implement that as part of this Story: https://issues.liferay.com/browse/LPS-59863In 6.2 you can extend the behavior of the Data Handlers using an EXT Plugin. You will ned to override the liferay-portlet.xml to use a new JournalArticleStagedModelDataHandler in the Journal Portlet. This new data handler can extend the existing one and you only need to override the methods you want with the custom logic for the priority.Thanks a lot! Please sign in to reply. Reply as... Cancel
Arnaldo Trujillo Julio Camarero 7 Years Ago By default the priority value is 0. I would like that the value would be 1. In this way you can increase or decrease the value, not only increase. Please sign in to reply. Reply as... Cancel ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
ghadeer raad Arnaldo Trujillo 3 Years Ago - Edited hi sir i use 7.2 and i need to change the value of priority to character not number such us "high" instead of "0" how i can do this please? Please sign in to reply. Reply as... Cancel
Firoza Saiyed 8 Years Ago Quite informative blog. Thank you for sharing. Please sign in to reply. Reply as... Cancel