Use of the withCredentials Jenkins statement to allow the injection of the credentials of the Git account used to push code change into the Github repo in the AutoDeploy build of the silverpeas mobile project.
6.4.3 has been released from build 6.4.3-build250411 (55e934b7cef4920baa8265a4b85d5b75a69bf142).Prepare for development iteration of next version 6.4.4 (details)
Remove the Firefox bug workaround as it is now fixed with Firefox 137 (details)
6.4.3 has been released from build 6.4.3-build250411 (55e934b7cef4920baa8265a4b85d5b75a69bf142).Prepare for development iteration of next version 6.4.4
The pb is the query part of the URI of HTTP GET requests isn't taken when checking for attempt to perform a CRUD operation on a resource in Silverpeas. Now all parts of the query is checked. Ensure also to avoid regexp flooding.
Guest users cannot access profiles of others users.
Fix minor bugs in directory. Fix null user id in the Ckeditor plugin identitycard.
Remove the login and specific identifier from the user data sent by the User Profile web service.
Refactor the way the search on users and groups are performed in Administration. Uses for doing a visitor pattern so that any additional treatments on the search criteria can be done easier.
Whatever a rich content of a contribution is added or updated, check the content cache for text to decide if a notification about contribution modification has to be triggered (in the case such notif is supported).
The bug was caused by the fact the sender isn't specified by default in the invitation sending. In fact, this is normal as by default the sender is the current requester. We have just to check the destinator isn't the sender himself.
Add a new sys event notifier for changes in the user roles for a given component instance. The related event is UserRoleEvent. Two listeners are added for this: - one for events about a user being removed from a user group - one for events about a change in the right profile of a component instance The first one figures out all the roles the group plays in all the component instances in order to send a notification about the user not playing anymore the role played by the group. The second one figures out the users who are removed from the right profile either directly or through a group removed from the right profile in order to send a notification about those users not playing anymore the role related by the right profile.
Add a listener of UserRoleEvents in order to figure out, for each concerned component instances, and for their nodes having local right profiles, the users related by the event and who play a role for the nodes. For those users, and in the case they don't play another role in the component instance, they are removed from the right profiles of the nodes.
Add a listener of ProfileInstEvent in order to spread to the nodes with local right profiles the remove of any user groups.
The two listeners above invoke the NodeProfileInstUpdater service to synchronize the changes of user roles in the component instance (and then also in the space of the component instance) to the nodes with specific local access rights.
NodeService#createNode methods return now the new NodeDetails instead of the NodePK of the created node.
Check directly the nullity of the returned ProfileInst object after the invocation of ProfileManager#getProfileInst(...) method in order to avoid to spread the nullity possibility of the ProfileInst object up to the chain of call.
In the TextDisplayer#getFieldValue method, converts blank characters in the text value to their HTML counterpart by using the WebEncodeHelper utility class.
In the commenting mechanism, when the content of the message and the additional message are the same, the additional message is dismissed in the sent notification. But, in the case of the notification about a comment, the additional message is the comment as is whereas the content of the message is the comment escaped for its printing in HTML! So, the two becomes different. In the case of a comment, there is no need to have both the additional message and the content of the notification message as they are identical. The fix here is to remove the extra message setting in the case of a notification about a comment.
Add FieldValueTemplate to model the template of a field value in a RecordTemplate of a form. This is to avoid to parse template parameters for both keys and values of fields in a FieldTemplate; the way they are encoded in the FieldTemplate has to be encapsulated and not exposed.
Attempt to provide a solution to bug #14399 by defining a new property with which we can set a timeout for the execution of a conversion task. By default, the timeout is set to 120000ms (2mn) but a greater value can be required on Windows as this system is a true bloatware.
The bug coming from the pagination was operated two times: - one by the web controller, - one by the ArrayPane itself. The fix has been to remove the pagination in the web controller side and to leave ArrayPane to controle the pagination of tikets.
In the WorkflowDesigner the side-effect operations are done by sending HTTP GET requests. Such requests require to have the session token to be specified in order to protect any CRSF attempts. But, in the case of removal, the request is performed directly by an explicit relocation (document.location) instead of using a simple anchor. In this situation, there is no session token set automatically. And, if the URL to which the relocation is performed contains some specific keywords (like creat for example), then the massive web shield forbiddes such relocation attempt without any anti-CRSF token. So, the fix was to replace the relocation mechanism by one in which a form is dynamically generated for the removal with as HTTP method POST.
By the way, I discovered by testing the fix the workflow designer wasn't designer to create a workflow from scratch but to edit existing ones. Besides that, I discovered also some hidden bugs. So I took the opportunity to clean up this mess up to a given level (in order to avoid to rewrite all the designer or to take too much time in this effort).
6.4.3 has been released from build 6.4.3-build250411 (37df12e5bfb887396a993a8bb3d98d53a149dcf7).Prepare for development iteration of next version 6.4.4 (details)
Fix URL to printContact.css in contact.jsp of YellowPages (details)
6.4.3 has been released from build 6.4.3-build250411 (37df12e5bfb887396a993a8bb3d98d53a149dcf7).Prepare for development iteration of next version 6.4.4
When checking a notification about a contribution change has to be triggered, the case of a new form is now taken into account (it was previously discarded).
Take into account the signature change of the NodeDetail#createNode methods.
When pasting a topic into another one, from a copy or a cut, take into account in KmeliaService the specific rights of a parent topic to the node in which the topic is pasted.
In Kmelia, fix bug by removing the encoding of the description for HTML but ensure it is well encoded for Js to avoid any attack by using js/HTML code injected in the description
Fix the bug: - Now the form used to create subscription is decoupled from the search form used to search and filter classifieds. It is generated directly from the two fields to use for search and for subscription. - Only one value is selectable for each field used for subscription: so they are selectable through a selection list. - When a field isn't valued for a subscription, set its value to an empty String.
Remove duplication code by providing reusable method in parent classes (the ClassifiedValidationHandler abstract class has been added for this purpose).
Add two new classes, SubscriptionField and SubscriptionFieldValue to model the two fields and their selectable values used in the subscription. They are used to generate the HTML form for subscription.
In ProcessManager, when the role of the current user has to be updated, before setting it, a check is performed to ensure the new role is among the roles he can play in the workflow.
6.4.3 has been released from build 6.4.3-build250411 (0d793f451ae2822fa89a779eed487790159a3a27).Prepare for development iteration of next version 6.4.4 (details)
6.4.3 has been released from build 6.4.3-build250411 (0d793f451ae2822fa89a779eed487790159a3a27).Prepare for development iteration of next version 6.4.4
6.4.3 has been released from build 6.4.3-build250411 (2bd9e5b3d4c9516811f574f4f53ce5e22532133b).Prepare for development iteration of next version 6.4.4 (details)
6.4.3 has been released from build 6.4.3-build250411 (2bd9e5b3d4c9516811f574f4f53ce5e22532133b).Prepare for development iteration of next version 6.4.4
6.4.3 has been released from build 6.4.3-build250411 (90e9347286664c1f250640839a01b6491f0c0a8d).Prepare for development iteration of next version 6.4.4 (details)
6.4.3 has been released from build 6.4.3-build250411 (90e9347286664c1f250640839a01b6491f0c0a8d).Prepare for development iteration of next version 6.4.4
6.4.3 has been released from build 6.4.3-build250411 (3b1f1764ddb2b1d8ced827f13b4bd00a9653fde7).Prepare for development iteration of next version 6.4.4 (details)
Remove a duplicated code by simplifying the if-statement (details)
6.4.3 has been released from build 6.4.3-build250411 (3b1f1764ddb2b1d8ced827f13b4bd00a9653fde7).Prepare for development iteration of next version 6.4.4
6.4.3 has been released from build 6.4.3-build250411 (f426a34c2164558c8e1bdc4f6d9b5000cae0b3ff).Prepare for development iteration of next version 6.4.4 (details)
Update dependency on Silverpeas to version 6.4.4-build250414 (details)
Update dependency on Silverpeas to version 6.4.4-build250417 (details)
Update dependency on Silverpeas to version 6.4.4-build250501 (details)
Update dependency on Silverpeas to version 6.4.4-build250508 (details)
6.4.3 has been released from build 6.4.3-build250411 (f426a34c2164558c8e1bdc4f6d9b5000cae0b3ff).Prepare for development iteration of next version 6.4.4
