(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.
(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-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
Cases considered for this update are:
1. One PK: Takes new sequence if PK not passed.
2. Two PK: Both PK should be mandatory except the case of secondary primary key (like agreementItemSeqId) where next subsequence is generated.
3. More than two PK's, all PK's should be mandatory except the fromDate.
Thanks Amardeep Singh Jhajj for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1749532 13f79535-47bb-0310-9956-ffa450edef68
I removed duplicate paths were componentname was uselessly repeated after component://componentname/script/org/ofbiz (projectmngr was the only one using there project instead)
I had few typos, easily fixed thanks to the tests. There could be still typos but they are unexpected and anyway no-brainer to fix
I'm still wondering about specialpurpose/example/minilang/README.txt.
I changed its content to
"The minilang directory is for static resources that are interpreted at run time rather than being compiled. This goes on the classpath, but does not get built or put into a JAR file."
not sure it makes any sense, I don't see how this relates to the classpath.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1747712 13f79535-47bb-0310-9956-ffa450edef68
We here at [Lusini|http://www.lusini.de/] did several improvements to the CMS backend to make it more usable for large CMS installations.
* Improved performance of CMS tree
** loading nodes dynamically using AJAX
*** Created ContentJsonEvents to handle the JSON calls
** use OFBiz entity caches
** removed duplicate execution of WebSitePublishPoint.groovy
*** removed reference from controller.xml as it is not used anywhere
* Moving nodes in CMS tree possible now using drag'n'drop
** ContentJsonEvents returns updated node attributes
** Adjusted WebSiteCMSNav.ftl to update the moved node with the data from the ajax request
** Needed to replace the jstree jQuery plugin by the current version available on the jstree website
* Made nodes deleteable
** added remove to context menu
** We did not want to delete the WebSitePathAlias entities right away, so we added a fromDate and thruDate to it.
*** extended WebSitePathAlias entity definition: added fromDate and thruDate
*** now checking for date range everywhere when accessing path aliases
*** This also allows users to publish or unpublish contents under a certain URL automatically at some time in the future.
** created event to "delete" a node
*** thruDate of all assocs pointing to this node are set to current timestamp
*** thruDate of WebSitePathAliases pointing to this content or any contents below are set to current timestamp
*** this way nothing is actually removed from the DB and a "undo" would be possible if necessary
** extracted context menu to variable so it can be reused for all trees
* fixed missing references to uiLabels in CMS menu bar
* Activated cookie plugin so the selected node is remembered
jleroux: I made few changes
* Use of UtilGenerics.cast() in new ContentJsonEvents.java rather than @SuppressWarnings("unchecked")
* Removal of the commented out block "Lusini: disable RTE". I see no reasons why we would not use elRTE. Notably in relation with adding errors where it's currently used in trunk demo
* I changed the line
var unmovableSubtrees = [false, "categoryChildren_LusiniBrowseRoot", "homeContentsRoot", "merchantContentsRoot"];
We have no such subtrees OOTB but it's good to keep the idea, I just renamed categoryChildren_LusiniBrowseRoot to categoryChildren and put an explaining comment
* I have roughly added the labels ContentWebSiteErrors, ContentWebSiteAddNewErrors and ContentWebSiteAddError, though I have a doubt about how this works. At least it's different than on trunk demo where it seems to works better (despite having uncommented out elRTE in this commit). ALso I don't remember how to add a menu worked (if it worked).
* I checked the version of jstree we use is the same than in the original patch from Christoph Neuroth. BTW at r1559769 I tried to update jstree to jstree 3 but gave up.
* I removed the jquery.cookie.js implemnentation and replaced link in WebSiteCMSNav.ftl. I already updted to jquery.cookie-1.4.0 at r1559769
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1738588 13f79535-47bb-0310-9956-ffa450edef68
* DataResourceAttribute
* ContentRole (not for create will set on second step)
* ContentMetaData
* ContentOperation
* ContentPurpose
* ContentPurposeOperation
* ContentAttribute
* ContentKeyword
* ContentType
* ContentAssocType
* ContentAssocPredicate
* ContentPurposeType
I also move some service definition from file services.xml to services_content.xml for all entities that concern content
relate issue OFBIZ-6745
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1715960 13f79535-47bb-0310-9956-ffa450edef68
After r751990, <<allow-html="any">> and <<allow-html="safe">> are the same: they do nothing! The only difference is the warning message from the OWASP Antisamy IntrusionDetector, which is both, as Christoph noted "giving you a false sense of security" or as I wrote "disturbing, wrong and useless". So there are no longer any reasons for differencing "safe" and "any".
This
* Deprecates "safe" (making it clear in the XSD documentation), keeping only "none" and "any". This is for backward compatibility, else we could completely remove the misleading "safe". Note that "none" is the default.
* Replaces in services definition all allow-html="safe" by allow-html="any"
* Remove from ModelService.java (near line 587) the code which throws the OWASP Antisamy IntrusionDetector message in log
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1536324 13f79535-47bb-0310-9956-ffa450edef68
1. Adding sequenceNum field on ContentPurpose entity.
2. Adding ContentAssocAndContentPurpose view entity.
3. Fixed NPE issue on WebSiteCMSContent.ftl file.
4. Created ContentPurposeType data for "LANDING_PAGE_IMAGE".
Thanks Amit & Vivek for the contribution
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@911774 13f79535-47bb-0310-9956-ffa450edef68
Moving services to correct component | location and renaming services so would be verbose enough to understand its purpose.
Thanks Mridul for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@885414 13f79535-47bb-0310-9956-ffa450edef68
Add a new feature in Product Content to add all four images at a time and one can preview those images in larger view on mouse over of particular image.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@883280 13f79535-47bb-0310-9956-ffa450edef68
I checked the commit logs and I don't see what changed to cause these services to stop working, so I took the shotgun approach and changed all occurrences of GenericValue service attributes.
If anyone has a better solution, please feel free to revert this commit and change it.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@765864 13f79535-47bb-0310-9956-ffa450edef68
Following best practice.
Changed location="org/ofbiz/......... to location="component:// in the service location attribute.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@755928 13f79535-47bb-0310-9956-ffa450edef68
key for the newly created content.
I made changes so that createContentAssoc would return "fromDate", but that did not help "createContent" because it was an eca
and I did not want to specify a "result-map-name" attribute.
So I modified createContent so that it would accept a fromDate as input, so at least I can know what the fromDate value is by
setting it to nowTimestamp before calling createContent.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@571052 13f79535-47bb-0310-9956-ffa450edef68