(OFBIZ-12075)
When you create a blog article with screen https://localhost:8443/content/control/EditBlogArticle?blogContentId=${blogId} by default you can create an article with a summary, an image and a long text.
After the creation all content related to this article was created by impossible to display this article correctly. The problem come from the contentAssoc of each relation where the mapKey isn't populate.
The root come from the conversion to entity-auto for the service createContent, where some seca are present and use some field to create some relation with attribute not present on a content (like the field mapKey)
To correct this I the simple way is to authorize these fields, and think for the future how do better.
Deleted the old mini-lang service file
Updated the service definitions with the new groovy methods
Added the groovy implementation (with minor enhancement)
(OFBIZ-11383)
Co-authored-by: Priya Sharma <priya.sharma@example.com>
unused services
(OFBIZ-11393)(OFBIZ-11394)
They were introduced by Al Byers in 2007 and, like some other stuff done then
by Al, were never used. We can safely close the 2 related issues as won't do
after removing the 2 services and all the references to them.
Thanks: Priya Sharma
(OFBIZ-11376)
I could not find any references for this service in the code base, i.e. this
service has not been used anywhere, do we still want to keep it?
Thanks: Devanshu Vyas for report, Priya Sharma for the proposition and the fix
(OFBIZ-10833)
This fixes the missing content association and wrong update of the
parent content reported by Ingo Wolfmayr. Thanks Sebastian Berg for
providing the patch.
(OFBIZ-11265)
Service parameter with allow-html="safe" does not check the OWASP sanitizer flag
ie. enabled or not and perform sanitization which causing policy error while
editing text data
getting following exception error:
"In field [textData] by our input policy, your input has not been accepted for
security reason. Please check and modify accordingly, thanks."
Thanks: Pradeep Choudhary for report and suggestion
(OFBIZ-10744)
It was due to missing default entity name in service definition while using entity-auto.
Thanks Ayushi Rathod for reporting the issue and providing the patch.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1849740 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-10245)
This commit introduce a new way to manage file transfer in OFBiz.
Inspired by mailing communication event management, a new communicationEventTypeId is created ('FILE_TRANSFER_COMM').
Such commEvent with classics : partyIdFrom/partyIdTo/contactMechIdTo/entryDate etc. are analysed by a job (like sendEmailDated), to send associated contents to a configured FTP/SFTP/FTPS server. If failure happens, it is catched and stored in communicationEvent, waiting for a new try.
For this purpose :
A new contactMechTypeId is introduced (FtpAddress), with its corresponding table. This contactMech store needed information for basic user/password authentication (server url and protocol, port, username, password, etc.)
A new service sendFileTransferDated that will look for pending file transfer and call following service.
A new service sendCommEventAsFtp that take a selected commEvent, check its structure and manage its status after trying the associated content file transfers.
A new service sendContentToFtp, that take a content and transfer it to a given FtpAddress.
A seca createCommEventFromFtpTransfer on sendContentToFtp to manage plural content file transfer, creating children communicationEvent to follow each content transfer separately (only for several content transfers).
A new Interface FtpClientInterface, with the 3 implementations of FTP, FTPS (To Implement), SFTP clients to manage Ftp connection and transfer.
A new property file to enable and manage redirection for testing purpose.
With this implementation, creating a communicationEvent, with a FtpAddress contactMechIdTo, and sendFileTransferDated job planned, the file is transfered to the ftp : communication event status set to COM_COMPLETE, if error occured the communication event status is set to COM_BOUNCED with error message on communicationEvent note.
Thanks Rishi for your feedbacks
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1831867 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-10401)
Like Suraj did for createRequirement, this uses
<override name="statusId" default-value="CTNT_IN_PROGRESS"/>
to replace the only thing specific in the Minilang implementation
Improves 2 related French labels
Thanks: Deepak for discussion and Suraj for initial idea
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1831511 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-9373)
After using plain text for the field [articleData], when I post the form,
I get the following error message:
The following required parameter is missing: [IN]
[createElectronicText.dataResourceId]]
jleroux: it was a bug introduced with r1765319 while refactoring to use
entity-auto
Thanks: Daniel Coric who find the reason and Yao who initially reported and
helped to find a solution
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1799088 13f79535-47bb-0310-9956-ffa450edef68
report creation
(OFBIZ-6919)
This are a non functional changes not yet used OOTB.
They are only intended to ease the sync between the svn trunk repo and
the github branch (using a fork)
So still a WIP...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1777586 13f79535-47bb-0310-9956-ffa450edef68
- facility
- marketting
- return
- entitysync
Also moved the permission check from implementation level to service defination level
(OFBIZ-8673)(OFBIZ-8673)(OFBIZ-8674)(OFBIZ-8739)(OFBIZ-8823)(OFBIZ-8825)(OFBIZ-8827)(OFBIZ-8850)(OFBIZ-8876)(OFBIZ-8875)(OFBIZ-8824)(OFBIZ-8826)(OFBIZ-8851)
Thanks Nameet Jain for your contribution
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1768188 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-8729)(OFBIZ-8730)(OFBIZ-8792)(OFBIZ-8793)(OFBIZ-8794)(OFBIZ-8795)(OFBIZ-8796)(OFBIZ-8797)(OFBIZ-8798)(OFBIZ-8799)(OFBIZ-8800)(OFBIZ-8801)(OFBIZ-8802)(OFBIZ-8803)(OFBIZ-8788)(OFBIZ-8789)(OFBIZ-8767)
(OFBIZ-8768)(OFBIZ-8769)(OFBIZ-8770)
Thanks: Chinmay Patidar, Amit Gadaley and Rishi Solanki for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1767965 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-8458) (OFBIZ-8347)
Actually it was a regression introduced by r1765499 for a ticket which did not
exist.
This also fixes OFBIZ-8347 for a typo (UPDATE permission instead of DELETE)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1766183 13f79535-47bb-0310-9956-ffa450edef68
(OFBIZ-8384)(OFBIZ-8388)(OFBIZ-8295)(OFBIZ-8294)(OFBIZ-8389)(OFBIZ-8390)(OFBIZ-8391)(OFBIZ-8392)(OFBIZ-8393)(OFBIZ-8407)
Thanks Pawan Verma for your contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1765500 13f79535-47bb-0310-9956-ffa450edef68