date:20141018


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar closed OFBIZ-5820.
---

Its not a valid issue. All the missing data creates on clicking 'Set To 
Complete' button action.  

 Error in ofbizsetup wizard due to incorrect GlAccount data
 --

 Key: OFBIZ-5820
 URL: https://issues.apache.org/jira/browse/OFBIZ-5820
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: 13.07.01
Reporter: Arun Patidar
Priority: Minor

 Need to remove incomplete GlAccount data (GlAccountData.xml) to prevent error 
 in ofbizsetup wizard.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5821) Incomplete data of GlAccount for using ofbizsetup wizard


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar closed OFBIZ-5821.
---
Resolution: Fixed

Its not a valid issue. All the missing data creates on clicking 'Set To 
Complete' button action. 

 Incomplete data of GlAccount for using ofbizsetup wizard
 

 Key: OFBIZ-5821
 URL: https://issues.apache.org/jira/browse/OFBIZ-5821
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: Arun Patidar
Priority: Minor

 Add missing GlAccount data(GlAccountData.xml) to prevent error in ofbizsetup 
 wizard processes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar updated OFBIZ-4528:

Attachment: OFBIZ-4528.patch

Attached is a patch for same.

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 11.04, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5825) Create a product that include some items


[ 
https://issues.apache.org/jira/browse/OFBIZ-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175905#comment-14175905
 ] 

Pranay Pandey commented on OFBIZ-5825:
--

For questions you don't need to create an issue in JIRA.
Please use user mailing list for questions and support. 
http://ofbiz.apache.org/mailing-lists.html


 Create a product that include some items
 

 Key: OFBIZ-5825
 URL: https://issues.apache.org/jira/browse/OFBIZ-5825
 Project: OFBiz
  Issue Type: Wish
  Components: product
Reporter: Hoan Dang Van

 Hi everyone
 I want to create a product that includes some items but i don't want customer 
 to select items when they buy products (When customer select that product, 
 which  are  included in it will be  automatically  added to cart)
 How can i do this ?
 Thank all!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5825) Create a product that include some items


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5825.
--
Resolution: Invalid

Please ask question on user mailing list. 

You can check Configurable Goods. I am hopeful that you are looking for 
similar products in OFBiz.  

 Create a product that include some items
 

 Key: OFBIZ-5825
 URL: https://issues.apache.org/jira/browse/OFBIZ-5825
 Project: OFBiz
  Issue Type: Wish
  Components: product
Reporter: Hoan Dang Van

 Hi everyone
 I want to create a product that includes some items but i don't want customer 
 to select items when they buy products (When customer select that product, 
 which  are  included in it will be  automatically  added to cart)
 How can i do this ?
 Thank all!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175910#comment-14175910
 ] 

Gaudin Pierre commented on OFBIZ-5823:
--

Hi Deepak,

Ok thanks, i haven't seen that the metada were in the contentMapFacade... 

I use dataResource entity because in the CMS tree view of a website entity 
DataResource is used to store metadata.
Maybe we could add both  in metadata contentMapFacade : the ones from 
DataResource and the ones from ContentMetaData ?
Another solution is to use ContentMetaData in CMS tree view instead of 
dataResource ? 

Pierre

ps : My first mane is Pierre ;-)



 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-5826) Shipper Account screen not rendering shipper accounts

Deepak Dixit created OFBIZ-5826:
---

 Summary: Shipper Account screen not rendering shipper accounts
 Key: OFBIZ-5826
 URL: https://issues.apache.org/jira/browse/OFBIZ-5826
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Trunk, Release Branch 13.07
Reporter: Deepak Dixit
Priority: Minor


Here is the steps to regenerate issue:
{code}
PortalPagePortlet portalPageId=PartyProfile portalPortletId=ShipperAccount 
portletSeqId=1 columnSeqId=1 sequenceNum=7/
{code}

Upload the PortalPagePortlet data for shipper Account, and go to viewprofile 
screen. Now add shipper account from shipper account screen.

Expected Result: Newly added/ all shipper account of party should be listed 
under shipper account screen.

Actual Result:
No shipper accounts are listing.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5826) Shipper Account screen not rendering shipper accounts


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit updated OFBIZ-5826:

Attachment: OFBIZ-5826.patch

Here is the patch for the issue. Added list name in ListCarrierAccounts form.

 Shipper Account screen not rendering shipper accounts
 -

 Key: OFBIZ-5826
 URL: https://issues.apache.org/jira/browse/OFBIZ-5826
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Release Branch 13.07, Trunk
Reporter: Deepak Dixit
Priority: Minor
 Attachments: OFBIZ-5826.patch


 Here is the steps to regenerate issue:
 {code}
 PortalPagePortlet portalPageId=PartyProfile 
 portalPortletId=ShipperAccount portletSeqId=1 columnSeqId=1 
 sequenceNum=7/
 {code}
 Upload the PortalPagePortlet data for shipper Account, and go to viewprofile 
 screen. Now add shipper account from shipper account screen.
 Expected Result: Newly added/ all shipper account of party should be listed 
 under shipper account screen.
 Actual Result:
 No shipper accounts are listing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175921#comment-14175921
 ] 

Deepak Dixit commented on OFBIZ-5823:
-

Thanks Pierre,

ContentMapFacade have different way to render the content.
You can refer the HtmlHead.ftl for this.
{code}
meta name=description 
content=${(decoratedContent.subcontent.metaDescription.render)!}/
meta name=keywords 
content=${(decoratedContent.subcontent.metaKeywords.render)!}/
{code}

IMO we can close this task.

 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5824) Error in communication screen while perfom sorting


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-5824:
--

Assignee: Ashish Vijaywargiya

 Error in communication screen while perfom sorting
 --

 Key: OFBIZ-5824
 URL: https://issues.apache.org/jira/browse/OFBIZ-5824
 Project: OFBiz
  Issue Type: Bug
Affects Versions: Release Branch 13.07, Trunk
Reporter: Deepak Dixit
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5824.patch


 In partymgr contrller.xml, we have view request named 
 ViewCommunicationEvent, and this request call an service event, due to this 
 when we try to perform sorting on  Child Communication Events,  Customer 
 Request List or any other screen over Communication screen then it will thorw 
 following exception:
 {code}
 org.ofbiz.webapp.event.EventHandlerException: Found URL parameter 
 [communicationEventId] passed to secure (https) request-map with uri 
 [ViewCommunicationEvent] with an event that calls service 
 [setCommEventRoleToRead]; this is not allowed for security reasons! The data 
 should be encrypted by making it part of the request body (a form field) 
 instead of the request URL. Moreover it would be kind if you could create a 
 Jira sub-task of https://issues.apache.org/jira/browse/OFBIZ-2330 (check 
 before if a sub-task for this error does not exist). If you are not sure how 
 to create a Jira issue please have a look before at 
 http://cwiki.apache.org/confluence/x/JIB2 Thank you in advance for your help.
  {code}
 Also due to this service event call on view request entry we can't open the 
 communication events in new tab. Ideally this service should be call in 
 screen context instead view request.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5824) Error in communication screen while perfom sorting


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5824.
--
Resolution: Fixed

Thanks Deepak for the contribution. Your changes are committed to trunk at 
r1632745 and to Release Branch 13.07 at r1632746.

 Error in communication screen while perfom sorting
 --

 Key: OFBIZ-5824
 URL: https://issues.apache.org/jira/browse/OFBIZ-5824
 Project: OFBiz
  Issue Type: Bug
Affects Versions: Release Branch 13.07, Trunk
Reporter: Deepak Dixit
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5824.patch


 In partymgr contrller.xml, we have view request named 
 ViewCommunicationEvent, and this request call an service event, due to this 
 when we try to perform sorting on  Child Communication Events,  Customer 
 Request List or any other screen over Communication screen then it will thorw 
 following exception:
 {code}
 org.ofbiz.webapp.event.EventHandlerException: Found URL parameter 
 [communicationEventId] passed to secure (https) request-map with uri 
 [ViewCommunicationEvent] with an event that calls service 
 [setCommEventRoleToRead]; this is not allowed for security reasons! The data 
 should be encrypted by making it part of the request body (a form field) 
 instead of the request URL. Moreover it would be kind if you could create a 
 Jira sub-task of https://issues.apache.org/jira/browse/OFBIZ-2330 (check 
 before if a sub-task for this error does not exist). If you are not sure how 
 to create a Jira issue please have a look before at 
 http://cwiki.apache.org/confluence/x/JIB2 Thank you in advance for your help.
  {code}
 Also due to this service event call on view request entry we can't open the 
 communication events in new tab. Ideally this service should be call in 
 screen context instead view request.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-3485) Error in updating party postal address if party has an EftAccount


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-3485:
--

Assignee: Ashish Vijaywargiya

 Error in updating party postal address  if party has an EftAccount
 --

 Key: OFBIZ-3485
 URL: https://issues.apache.org/jira/browse/OFBIZ-3485
 Project: OFBiz
  Issue Type: Bug
  Components: party
Reporter: Abdullah Shaikh
Assignee: Ashish Vijaywargiya

 Try to update the party Postal Address, which have an EftAccount, using the 
 Update button in Profile's Contact Information section, you get the below 
 error,
 The Following Errors Occurred:
 Error trying to begin transaction, could not process method: The current 
 transaction is marked for rollback, not beginning a new transaction and 
 aborting current operation; the rollbackOnly was caused by: Service 
 [updateEftAccount] threw an unexpected 
 exception/errororg.ofbiz.service.ServiceValidationException: The following 
 required parameter is missing: [updateEftAccount.nameOnAccount] (The 
 following required parameter is missing: [updateEftAccount.nameOnAccount])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-3485) Error in updating party postal address if party has an EftAccount


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-3485.
--
Resolution: Duplicate

Fix for this issue has already be taken care under OFBIZ-4804. Thanks Amardeep 
for your help in verification. Thanks Abdullah for reporting the issue. 

 Error in updating party postal address  if party has an EftAccount
 --

 Key: OFBIZ-3485
 URL: https://issues.apache.org/jira/browse/OFBIZ-3485
 Project: OFBiz
  Issue Type: Bug
  Components: party
Reporter: Abdullah Shaikh
Assignee: Ashish Vijaywargiya

 Try to update the party Postal Address, which have an EftAccount, using the 
 Update button in Profile's Contact Information section, you get the below 
 error,
 The Following Errors Occurred:
 Error trying to begin transaction, could not process method: The current 
 transaction is marked for rollback, not beginning a new transaction and 
 aborting current operation; the rollbackOnly was caused by: Service 
 [updateEftAccount] threw an unexpected 
 exception/errororg.ofbiz.service.ServiceValidationException: The following 
 required parameter is missing: [updateEftAccount.nameOnAccount] (The 
 following required parameter is missing: [updateEftAccount.nameOnAccount])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


[ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175930#comment-14175930
 ] 

Mridul Pathak commented on OFBIZ-4528:
--

I reviewed the patch and have couple suggestions,
1. filterOutOfStockProducts() method should be moved to ProductWorker.java and 
made public.
2. In the method calls there is additional white space before opening bracket.

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 11.04, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


[ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175932#comment-14175932
 ] 

Mridul Pathak commented on OFBIZ-4528:
--

Additional details around the actual problem and solution in the patch,

Actual Problem - The out of stock products were being filtered in 
CategoryDetail.groovy after receiving the product list from 
getProductCategoryAndLimitedMembers, while pagination values were being set and 
returned by the mentioned service. The list size at the end was changing and 
the pagination values returned were not in sync with the final list size.

Solution - The filtering of out of stock product must be done in 
getProductCategoryAndLimitedMembers service itself before setting the 
pagination values.

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 11.04, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5783) Shipment Box Type selection should be at package level instead of item level on Pack Order Screen


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mridul Pathak updated OFBIZ-5783:
-
Attachment: OFBIZ-5783.patch

Here is the patch for this change. This should resolve OFBIZ-4606 as well.

 Shipment Box Type selection should be at package level instead of item level 
 on Pack Order Screen
 -

 Key: OFBIZ-5783
 URL: https://issues.apache.org/jira/browse/OFBIZ-5783
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Release Branch 13.07, Trunk
Reporter: Mridul Pathak
Priority: Minor
 Fix For: Release Branch 13.07, Trunk

 Attachments: OFBIZ-5783.patch


 The Shipment Box Type selection is at line item level on Pack Order screen 
 where the package selection for each order item is made. It should instead be 
 at package level next to the package weight input box.
 Also, ShipmentBoxType values are supported only for USPS, which is hard coded 
 in PackOrder.groovy.
 There is a bug reported in OFBIZ-4606 for Release 11.04 but exists in Trunk 
 as well. It should be fixed if we make the above change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4461) Packaging slip for Purchase order related to drop shipment is empty


[ 
https://issues.apache.org/jira/browse/OFBIZ-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175935#comment-14175935
 ] 

Pranay Pandey commented on OFBIZ-4461:
--

Hi Kiran,

I executed the process by following the steps given and could see the error on 
packaging slip as mentioned.

IMO we should refer the use case here. For drop ship purchase order shipment 
creating packages is required or not. As no packages were created for the 
shipment, packaging slip is saying no packages found for this shipment. 

Yes we can surely mention it better on packaging slip, messaging can be 
corrected/updated if the process is working as expected. Instead of labeling it 
as an error. 

Lets finalize if it needs to be addressed or not. Please put your ideas and 
help concluding this issue. 



 Packaging slip for Purchase order related to drop shipment is empty
 ---

 Key: OFBIZ-4461
 URL: https://issues.apache.org/jira/browse/OFBIZ-4461
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Kiran Gawde

 1. Place an order for product under drop shipment category.
 2. Select the order in admin
 3. Choose the associated purchase order
 4. Approve the purchase order
 5. Click on 'Quick Drop Ship'
 6. Shipment and Packaging Slip button appear.
 7. Click on packaging slip. 
 Issue: It will say: ERROR: No packages found for this shipment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar updated OFBIZ-4528:

Attachment: OFBIZ-4528.patch

Thanks Mridul for reviewing. I have attached modified patch.

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 11.04, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch, OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya updated OFBIZ-4528:
---
Affects Version/s: (was: Release Branch 11.04)
   Release Branch 13.07

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 13.07, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch, OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5826) Shipper Account screen not rendering shipper accounts


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-5826:
--

Assignee: Ashish Vijaywargiya

 Shipper Account screen not rendering shipper accounts
 -

 Key: OFBIZ-5826
 URL: https://issues.apache.org/jira/browse/OFBIZ-5826
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Release Branch 13.07, Trunk
Reporter: Deepak Dixit
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5826.patch


 Here is the steps to regenerate issue:
 {code}
 PortalPagePortlet portalPageId=PartyProfile 
 portalPortletId=ShipperAccount portletSeqId=1 columnSeqId=1 
 sequenceNum=7/
 {code}
 Upload the PortalPagePortlet data for shipper Account, and go to viewprofile 
 screen. Now add shipper account from shipper account screen.
 Expected Result: Newly added/ all shipper account of party should be listed 
 under shipper account screen.
 Actual Result:
 No shipper accounts are listing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-1006) Webtools Find on Credit Card entity fails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-1006:
--

Assignee: Ashish Vijaywargiya

 Webtools Find on Credit Card entity fails
 -

 Key: OFBIZ-1006
 URL: https://issues.apache.org/jira/browse/OFBIZ-1006
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Reporter: Dave Tenerowicz
Assignee: Ashish Vijaywargiya
Priority: Minor

 Attempting a find operation on cardNumber column fails  to find records 
 (using webtools/entity reference) in the Credit Card entity. Suspect this is 
 related to encrypted values in the column. Find operation should encrypt the 
 value entered in the search field before executing SQL query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-2618) double forward slashes in ecommerce emails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Patidar updated OFBIZ-2618:

Attachment: OFBIZ-2618.patch

Attached is modified patch to fix the same issue. Issue can be check in Order 
Complete Notification email with orderId link.



 double forward slashes in ecommerce emails
 --

 Key: OFBIZ-2618
 URL: https://issues.apache.org/jira/browse/OFBIZ-2618
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: Release Branch 09.04, Trunk
Reporter: BJ Freeman
 Attachments: OFBIZ-2618.patch, Ofbiz_2618_ecommerceEmail.patch


 in the widets 
 set field=baseEcommerceSecureUrl
 value=${baseSecureUrl}/ecommerce/control//
 has a trailing forward slash
 then the added url has a leading forward slash
 /orderstatus?orderId=
 so you get
 /ecommerce/control//orderstatus?orderId=
 removed the trailing forward slash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-3329) commonext component has dependency on party management component

2014-10-18 Thread Divesh Dutta (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175945#comment-14175945
 ] 

Divesh Dutta commented on OFBIZ-3329:
-

Thanks [~jacques.le.roux] for your views. I discussed with [~arunpati] 
internally as he recently researched on use of Common ext component. As you 
mentioned that its a set up component, he also found that: 

'commonext'  component can be use to setup organization party, store, website, 
facility, catalog, category, product and customer over the seed data of OFBiz. 
We can only create single record for each using this component. 

So when ever you don't want to use demo data of OFBiz and set up your own/ext 
data or your client's data you can use commonext component to set up that data. 
 

So I think its OKAY that commonext component having dependency on other 
applications's component as its used to set up various set of data. 

So we can discard this  issue now. 

Thanks all for discussions and helping in conclusions :)


 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow

 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-2618) double forward slashes in ecommerce emails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel reassigned OFBIZ-2618:
---

Assignee: Anil K Patel

 double forward slashes in ecommerce emails
 --

 Key: OFBIZ-2618
 URL: https://issues.apache.org/jira/browse/OFBIZ-2618
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: Release Branch 09.04, Trunk
Reporter: BJ Freeman
Assignee: Anil K Patel
 Attachments: OFBIZ-2618.patch, Ofbiz_2618_ecommerceEmail.patch


 in the widets 
 set field=baseEcommerceSecureUrl
 value=${baseSecureUrl}/ecommerce/control//
 has a trailing forward slash
 then the added url has a leading forward slash
 /orderstatus?orderId=
 so you get
 /ecommerce/control//orderstatus?orderId=
 removed the trailing forward slash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-4528) Out of stock products screw up the pagination during category browsing


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-4528.
--
Resolution: Fixed

Thanks Arun for the contribution. Commited changes in trunk at r1632750 and in 
Release Branch 13.07 at r1632760.

 Out of stock products screw up the pagination during category browsing
 --

 Key: OFBIZ-4528
 URL: https://issues.apache.org/jira/browse/OFBIZ-4528
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/ecommerce
Affects Versions: Release Branch 13.07, Trunk
Reporter: Kiran Gawde
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-4528.patch, OFBIZ-4528.patch


 Pagination is handled in getProductCategoryAndLimitedMembers
 Then the out of stock filtering is done in CategoryDetail.groovy.
 Hence the pagination is screwed up. Certain pages might show less records or 
 no records based upon data condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-2618) double forward slashes in ecommerce emails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-2618:
--

Assignee: Ashish Vijaywargiya  (was: Anil K Patel)

 double forward slashes in ecommerce emails
 --

 Key: OFBIZ-2618
 URL: https://issues.apache.org/jira/browse/OFBIZ-2618
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: Release Branch 09.04, Trunk
Reporter: BJ Freeman
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-2618.patch, Ofbiz_2618_ecommerceEmail.patch


 in the widets 
 set field=baseEcommerceSecureUrl
 value=${baseSecureUrl}/ecommerce/control//
 has a trailing forward slash
 then the added url has a leading forward slash
 /orderstatus?orderId=
 so you get
 /ecommerce/control//orderstatus?orderId=
 removed the trailing forward slash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5723) Unable to override service and events in custom component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5723.
--
Resolution: Invalid

 Unable to override service and events in custom component
 -

 Key: OFBIZ-5723
 URL: https://issues.apache.org/jira/browse/OFBIZ-5723
 Project: OFBiz
  Issue Type: Bug
Reporter: Jagdeep Singh





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel reassigned OFBIZ-3329:
---

Assignee: Anil K Patel

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel

 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5783) Shipment Box Type selection should be at package level instead of item level on Pack Order Screen


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-5783:
--

Assignee: Ashish Vijaywargiya

 Shipment Box Type selection should be at package level instead of item level 
 on Pack Order Screen
 -

 Key: OFBIZ-5783
 URL: https://issues.apache.org/jira/browse/OFBIZ-5783
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Release Branch 13.07, Trunk
Reporter: Mridul Pathak
Assignee: Ashish Vijaywargiya
Priority: Minor
 Fix For: Release Branch 13.07, Trunk

 Attachments: OFBIZ-5783.patch


 The Shipment Box Type selection is at line item level on Pack Order screen 
 where the package selection for each order item is made. It should instead be 
 at package level next to the package weight input box.
 Also, ShipmentBoxType values are supported only for USPS, which is hard coded 
 in PackOrder.groovy.
 There is a bug reported in OFBIZ-4606 for Release 11.04 but exists in Trunk 
 as well. It should be fixed if we make the above change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel resolved OFBIZ-3329.
-
Resolution: Fixed

Looking at the conversation on the task, We can close this issue. There is 
nothing to be fixed. 
IMO: This application is special purpose, and should live in specialpurpose 
folder.

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel

 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel reopened OFBIZ-3329:
-

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel

 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel updated OFBIZ-3329:

Comment: was deleted

(was: Looking at the conversation on the task, We can close this issue. There 
is nothing to be fixed. 
IMO: This application is special purpose, and should live in specialpurpose 
folder.)

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel

 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5714) Comment does not save

2014-10-18 Thread Akash Jain (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175962#comment-14175962
]

Akash Jain commented on OFBIZ-5714:
---

Verified following scenarios:

Test Case 1:
# Go to Order Detail page of any purchase order.
# Make sure comment associated with any order item.

Expected Results:
# Comment should be shown on order item block.
# If multiple comment associated with any order item then comment history
should be shown for particular order item.

Test Case 2:
# Go to Order Detail page of any approved purchase order.
# Press Edit Items button for adding the order item.
# Add item with Desired Delivery Date and Comment through Add to Order form
below order item block.

Expected Result:
Desired (Estimated) Delivery Date and Comment should be associated with created
order item.

Test Case 3:
# Go to Order Detail page of any purchase order.
# Make sure comment associated with any order item.
# Press Edit Item button for editing the order item.
# Update comment of any order item.

Expected Result:
Comment should be updated for particular order item.

Comment does not save
--

Key: OFBIZ-5714
URL: https://issues.apache.org/jira/browse/OFBIZ-5714
Project: OFBiz
Issue Type: Bug
Components: order
Affects Versions: 12.04.03, 11.04.06, 12.04.05, 13.07.01, Upcoming Branch
Environment: Ubuntu 12.04, using postgres for data.
Reporter: joel fradkin
Assignee: Ashish Vijaywargiya
Priority: Minor

1. find P.O.
2. select approaved p.o.
3. edit items
4 add item (at bottom of screen)
5. Comment does not save.
Note! shouldn't the comment be displayed on some of the P.O. screens?
I only know it does not save as I edited the .FTL on viewpo and pdf to
include comment. Comments from the orignal create P.O. show up, ALso should
be able to edit a comment, when edit items is entered.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5714) Comment does not save

2014-10-18 Thread Akash Jain (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akash Jain updated OFBIZ-5714:
--
Attachment: OFBIZ-5714-trunk.patch
OFBIZ-5714-branch-13-07.patch
OFBIZ-5714-branch-12-04.patch

This issue will be fixed in trunk, 12.04  13.07 branch. Attached patch for the 
same.

 Comment does not save 
 --

 Key: OFBIZ-5714
 URL: https://issues.apache.org/jira/browse/OFBIZ-5714
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: 12.04.03, 11.04.06, 12.04.05, 13.07.01, Upcoming Branch
 Environment: Ubuntu 12.04, using postgres for data.
Reporter: joel fradkin
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5714-branch-12-04.patch, 
 OFBIZ-5714-branch-13-07.patch, OFBIZ-5714-trunk.patch


 1. find P.O.
 2. select approaved p.o.
 3. edit items
 4 add item (at bottom of screen)
 5. Comment does not save.
 Note! shouldn't the comment be displayed on some of the P.O. screens?
 I only know it does not save as I edited the .FTL on viewpo and pdf to 
 include comment. Comments from the orignal create P.O. show up, ALso should 
 be able to edit a comment, when edit items is entered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175964#comment-14175964
 ] 

Gaudin Pierre commented on OFBIZ-5823:
--

Many thanks Deepak, I was on the wrong way !!

But i think that we should change the way CMS tree view of a website stores 
metadata because it is store into DataResource entity, not  into 
ContentMetaData.
I'd like to provide a patch to fix this.

Do you agree with it?

Many thanks,

Pierre




 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5728) When in edit item in P.O. does not save comment or delivery date when appending

2014-10-18 Thread Akash Jain (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175965#comment-14175965
 ] 

Akash Jain commented on OFBIZ-5728:
---

This issue will be fixed with OFBIZ-5714 I have attached patch on OFBIZ-5714 
with testing scenarios.

 When in edit item in P.O. does not save comment or delivery date when 
 appending
 ---

 Key: OFBIZ-5728
 URL: https://issues.apache.org/jira/browse/OFBIZ-5728
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 12.04
 Environment: ubuntu 12.04
Reporter: joel fradkin
Assignee: Ashish Vijaywargiya
Priority: Minor

 edit a P.O. add a new item (fields at bottom of screen).
 When a new item is added it does not save the comment, or the delivery date. 
 (did not test other fields). It does add a new item, but those two fields are 
 not being saved it seems.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5783) Shipment Box Type selection should be at package level instead of item level on Pack Order Screen


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5783.
--
Resolution: Fixed

Thanks Mridul for the contribution. Your changes are committed in trunk at 
r1632772 and in RB13.07 at r1632775.

 Shipment Box Type selection should be at package level instead of item level 
 on Pack Order Screen
 -

 Key: OFBIZ-5783
 URL: https://issues.apache.org/jira/browse/OFBIZ-5783
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Release Branch 13.07, Trunk
Reporter: Mridul Pathak
Assignee: Ashish Vijaywargiya
Priority: Minor
 Fix For: Trunk, Release Branch 13.07

 Attachments: OFBIZ-5783.patch


 The Shipment Box Type selection is at line item level on Pack Order screen 
 where the package selection for each order item is made. It should instead be 
 at package level next to the package weight input box.
 Also, ShipmentBoxType values are supported only for USPS, which is hard coded 
 in PackOrder.groovy.
 There is a bug reported in OFBIZ-4606 for Release 11.04 but exists in Trunk 
 as well. It should be fixed if we make the above change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-251) On split payment screen, two small bugs

2014-10-18 Thread Amardeep Singh Jhajj (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175970#comment-14175970
]

Amardeep Singh Jhajj commented on OFBIZ-251:

Okay lets try concluding this issue.

IMO It is very difficult for ecommerce site user to understand this OOTB split
payment feature flow, its UI/UX is quite confusing and should be updated.
I tried understanding the issues mentioned here. Couldn't reach upto the place
where I can actually see whats being reported. May be the complex split payment
process which exists in ecommerce app confused me. Because when I reached the
place being mentioned in the issue detail nothing looks like the way its
mentioned here. We should figure out the use case and work on fixing the issue.

If someone from community can join me and help in understanding whats being
reported, I am willing to work on this issue.

If its not a valid issue, we can simply close it.

On split payment screen, two small bugs
---

Key: OFBIZ-251
URL: https://issues.apache.org/jira/browse/OFBIZ-251
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/ecommerce
Reporter: Jacopo Cappellato
Priority: Minor

Copy of two issues reported by Les Austin in the old server:
===
When a credit card and another form of payment are split, if the box for up
to amount after the card is not completed, all charges go to other form of
payment. An error message or reminder notice would be friendly and preclude
customers from becoming upset over this procedural error.
===
When using split payment option, once a radio button is selected, can only
change to another radio button as one of choices. When customer desires to
use two cards or a card and a gift certificate after having selected a radio,
this path is not available. Suggest: an undo button, or a button for credit
card/gift card only.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-4606) While packing picklist bin items, shipmentBoxType is setting same for every package even if we select different box types.


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-4606.
--
Resolution: Fixed

Based on Mridul's comment on jira issue OFBIZ-5783, we can close this task. 
Thanks Mridul. 

 While packing picklist bin items, shipmentBoxType is setting same for every 
 package even if we select different box types.
 --

 Key: OFBIZ-4606
 URL: https://issues.apache.org/jira/browse/OFBIZ-4606
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: Release Branch 11.04
Reporter: Suprit Udawat
 Attachments: OFBIZ-4606.patch


 Steps to regenerate bug in packing process under Facility:
 1) Create/Place an order with having two or more items and shipping option as 
 USPS.
 2) Go to packing screen and then pack that order using normal packing but not 
 weigh packages.
 3) Make more then two packages for all line items and also select 
 shipmentBoxType for each line item.
 4) After creating packages and setting shipment boxTypes for them, complete 
 the pack order process.
 5) Now you can see in ShipmentPackage entity that for each package, the box 
 type is same as that of the last package box type.
 Now, user will expecting that for every package there will be different box 
 type he selected for packages.
 NOTE: For now if there are three line items and user selected different box 
 types for each (say large box of item 1, tube box for item 2 and 10kg box for 
 item 3) and user selects same package for each item (say package 1), then 
 ideally there will not be three different box types for 1 package, so system 
 will set last selected box type (i.e. 10kg box) for package 1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5714) Comment does not save


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5714.
--
Resolution: Fixed

Thanks Joel for reporting the issue. Thanks Akash for providing the patch for 
the same. Changes are contributed in trunk, RB13.07 and RB12.04. Please refer 
revisions - r1632777, r1632779 and r1632780.

 Comment does not save 
 --

 Key: OFBIZ-5714
 URL: https://issues.apache.org/jira/browse/OFBIZ-5714
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: 12.04.03, 11.04.06, 12.04.05, 13.07.01, Upcoming Branch
 Environment: Ubuntu 12.04, using postgres for data.
Reporter: joel fradkin
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5714-branch-12-04.patch, 
 OFBIZ-5714-branch-13-07.patch, OFBIZ-5714-trunk.patch


 1. find P.O.
 2. select approaved p.o.
 3. edit items
 4 add item (at bottom of screen)
 5. Comment does not save.
 Note! shouldn't the comment be displayed on some of the P.O. screens?
 I only know it does not save as I edited the .FTL on viewpo and pdf to 
 include comment. Comments from the orignal create P.O. show up, ALso should 
 be able to edit a comment, when edit items is entered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5728) When in edit item in P.O. does not save comment or delivery date when appending


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5728.
--
Resolution: Fixed

Based on Akash's comment we can close this issue. Thanks Akash for your 
contribution and thanks Joel for creating the issue.

 When in edit item in P.O. does not save comment or delivery date when 
 appending
 ---

 Key: OFBIZ-5728
 URL: https://issues.apache.org/jira/browse/OFBIZ-5728
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Release Branch 12.04
 Environment: ubuntu 12.04
Reporter: joel fradkin
Assignee: Ashish Vijaywargiya
Priority: Minor

 edit a P.O. add a new item (fields at bottom of screen).
 When a new item is added it does not save the comment, or the delivery date. 
 (did not test other fields). It does add a new item, but those two fields are 
 not being saved it seems.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5682) Hardcoded stylesheets and javascript resources


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel reassigned OFBIZ-5682:
---

Assignee: Anil K Patel

 Hardcoded stylesheets and javascript resources
 --

 Key: OFBIZ-5682
 URL: https://issues.apache.org/jira/browse/OFBIZ-5682
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/cmssite
Affects Versions: Release Branch 11.04, Release Branch 12.04, Release 
 Branch 13.07, Trunk
Reporter: Pierre Smits
Assignee: Anil K Patel

 The 'HtmlHead.ftl' file of the cmssite component contains following hardcoded 
 style sheet and javascript resources:
 * /images/fieldlookup.js
 * /images/selectall.js
 * /images/ecommain.css
 * /ecommerce/images/blog.css
 * /content/images/contentForum.css



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5682) Hardcoded stylesheets and javascript resources


[ 
https://issues.apache.org/jira/browse/OFBIZ-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175979#comment-14175979
 ] 

Anil K Patel commented on OFBIZ-5682:
-

Pierre,
IMO this issue is not a Bug, instead, it is improvement. Do you agree?

 Hardcoded stylesheets and javascript resources
 --

 Key: OFBIZ-5682
 URL: https://issues.apache.org/jira/browse/OFBIZ-5682
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/cmssite
Affects Versions: Release Branch 11.04, Release Branch 12.04, Release 
 Branch 13.07, Trunk
Reporter: Pierre Smits
Assignee: Anil K Patel

 The 'HtmlHead.ftl' file of the cmssite component contains following hardcoded 
 style sheet and javascript resources:
 * /images/fieldlookup.js
 * /images/selectall.js
 * /images/ecommain.css
 * /ecommerce/images/blog.css
 * /content/images/contentForum.css



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-2618) double forward slashes in ecommerce emails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-2618.
--
Resolution: Fixed

Thanks BJ for creating the issue and providing first patch. Thanks Arun for the 
contribution. 

Anil has committed the patch at revisions - r1632764, r1632781, r1632782

 double forward slashes in ecommerce emails
 --

 Key: OFBIZ-2618
 URL: https://issues.apache.org/jira/browse/OFBIZ-2618
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: Release Branch 09.04, Trunk
Reporter: BJ Freeman
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-2618.patch, Ofbiz_2618_ecommerceEmail.patch


 in the widets 
 set field=baseEcommerceSecureUrl
 value=${baseSecureUrl}/ecommerce/control//
 has a trailing forward slash
 then the added url has a leading forward slash
 /orderstatus?orderId=
 so you get
 /ecommerce/control//orderstatus?orderId=
 removed the trailing forward slash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5682) Hardcoded stylesheets and javascript resources


[ 
https://issues.apache.org/jira/browse/OFBIZ-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175982#comment-14175982
 ] 

Anil K Patel commented on OFBIZ-5682:
-

We have various ways to model content assoc for example, 

!-- Add css file links to HHEAD --
DataResource dataResourceId=BOOTSTRAP_MIN_CSS dataResourceTypeId=LINK 
objectInfo=https://maxcdn.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css;
 mimeTypeId=text/css/
Content contentId=BOOTSTRAP_MIN_CSS contentTypeId=DOCUMENT 
contentName=Bootstrap compiled and minified CSS 
dataResourceId=BOOTSTRAP_MIN_CSS/
ContentAssoc contentId=DSITE_HHEAD contentIdTo=BOOTSTRAP_MIN_CSS 
sequenceNum=1 contentAssocTypeId=SUB_CONTENT mapKey=stylesheet 
fromDate=2014-10-02 00:00:00/

And then, 
Put code like following in htmlhead file,
#assign nothing = thisContent.setMapKeyFilter(stylesheet)/
#list thisContent.subcontent_all as content
link rel=stylesheet 
href=@ofbizContentUrl${StringUtil.wrapString(content.toString())}/@ofbizContentUrl
 type=text/css/
/#list

I am working on similar idea, to see more complete code, here is link,
https://github.com/ofbizecosystem/evolvingofbiz/blob/trunk/hot-deploy/dcommerce/data/DcommerceSiteData.xml
 


 Hardcoded stylesheets and javascript resources
 --

 Key: OFBIZ-5682
 URL: https://issues.apache.org/jira/browse/OFBIZ-5682
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/cmssite
Affects Versions: Release Branch 11.04, Release Branch 12.04, Release 
 Branch 13.07, Trunk
Reporter: Pierre Smits
Assignee: Anil K Patel

 The 'HtmlHead.ftl' file of the cmssite component contains following hardcoded 
 style sheet and javascript resources:
 * /images/fieldlookup.js
 * /images/selectall.js
 * /images/ecommain.css
 * /ecommerce/images/blog.css
 * /content/images/contentForum.css



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4927) The updation and deletion of content meta data tab is not working.Needs a change of entity ContentMetaData.


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel updated OFBIZ-4927:

Description: The updation and deletion of content meta data tab is not 
working. Needs a change of entity ContentMetaData. As metaDataValue is changed 
from primary key to non primary key as the value can be updated.  (was: The 
updation and deletion of content meta data tab is not working.Needs a change of 
entity ContentMetaData.As metaDataValue is changed from primary key to non 
primary key as the value can be updated.)

 The updation and deletion of content meta data tab is not working.Needs a 
 change of entity ContentMetaData.
 ---

 Key: OFBIZ-4927
 URL: https://issues.apache.org/jira/browse/OFBIZ-4927
 Project: OFBiz
  Issue Type: Improvement
  Components: content
Affects Versions: Release 09.04, Release 10.04, Release 11.04.01
 Environment: windows
Reporter: Tata Consultancy Services ltd
 Attachments: OFBIZ-4927.patch, updatemeta.txt


 The updation and deletion of content meta data tab is not working. Needs a 
 change of entity ContentMetaData. As metaDataValue is changed from primary 
 key to non primary key as the value can be updated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-1006) Webtools Find on Credit Card entity fails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mridul Pathak updated OFBIZ-1006:
-
Attachment: OFBIZ-1006.png

Can not reproduce. Please see attached screenshot.

 Webtools Find on Credit Card entity fails
 -

 Key: OFBIZ-1006
 URL: https://issues.apache.org/jira/browse/OFBIZ-1006
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Reporter: Dave Tenerowicz
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-1006.png


 Attempting a find operation on cardNumber column fails  to find records 
 (using webtools/entity reference) in the Credit Card entity. Suspect this is 
 related to encrypted values in the column. Find operation should encrypt the 
 value entered in the search field before executing SQL query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-1006) Webtools Find on Credit Card entity fails


 [ 
https://issues.apache.org/jira/browse/OFBIZ-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-1006.
--
Resolution: Cannot Reproduce

Based on Mridul's comment we are closing this issue. Thanks Mridul. 
Thanks Dave for creating the issue. 

 Webtools Find on Credit Card entity fails
 -

 Key: OFBIZ-1006
 URL: https://issues.apache.org/jira/browse/OFBIZ-1006
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Reporter: Dave Tenerowicz
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-1006.png


 Attempting a find operation on cardNumber column fails  to find records 
 (using webtools/entity reference) in the Credit Card entity. Suspect this is 
 related to encrypted values in the column. Find operation should encrypt the 
 value entered in the search field before executing SQL query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-1006) Webtools Find on Credit Card entity fails


[ 
https://issues.apache.org/jira/browse/OFBIZ-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175988#comment-14175988
 ] 

Anil K Patel commented on OFBIZ-1006:
-

I see that Credit Card number is shown in clear text. 
Its ok to show in user entered field,  but in the results list I think we 
should mask (show last 4 digits only) credit card number?


 Webtools Find on Credit Card entity fails
 -

 Key: OFBIZ-1006
 URL: https://issues.apache.org/jira/browse/OFBIZ-1006
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Reporter: Dave Tenerowicz
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-1006.png


 Attempting a find operation on cardNumber column fails  to find records 
 (using webtools/entity reference) in the Credit Card entity. Suspect this is 
 related to encrypted values in the column. Find operation should encrypt the 
 value entered in the search field before executing SQL query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5438) Virtual feature selection and selected variant price inconsistencies

[
https://issues.apache.org/jira/browse/OFBIZ-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175991#comment-14175991
]

Mridul Pathak commented on OFBIZ-5438:
--

The product WG-9944 is an OOTB example of a feature explosion. The variants are
created dynamically during sales order entry workflow. When a new variant is
being created, if there is feature price associated with the selected features
the variant price is calculated by adding virtual product price and feature
price(s).
On the other hand as mentioned in the description when virtual product default
price or the feature price is updated the change is not reflected in variant
product price.

I agree that we could have additional logic to handle this. A batch service
that updates the variant product prices on update in virtual product price or
feature price (only if feature price exist) could be implemented. Though it
seems more like a missing functionality rather than a bug. I think that we
should probably change the issue type to improvement.

Virtual feature selection and selected variant price inconsistencies

Key: OFBIZ-5438
URL: https://issues.apache.org/jira/browse/OFBIZ-5438
Project: OFBiz
Issue Type: Bug
Components: order
Reporter: Christian Carlow
Assignee: Ashish Vijaywargiya

To reproduce this issue:
1. Create a sales order for DemoCustCompany
2. Add WG-9944 to the cart
3. Select Black (notice +$4.30) and 4-Wheels and click Add to Cart
4. Click the check mark for the WG-9944 variant item that was added to the
cart and then click the Remove Selected button
5. Navigate to the WG-9944 product features page
6. Click feature 9000 to edit the Black Color feature
7. Update the feature price from 4.3 to 1.3
8. Add WG-9944 to the cart again by selecting the Black (notice now +$1.30)
and 4-Wheel feature options
After step 9, notice that the item price is actually calculated using the
previous feature default price value even though the new feature price is
listed with the option.
A similar problem occurs if the virtual product default price is changed.
The feature selection page shows the updated virtual product price but once
the features are selected, the default price of the variant product which was
set when the variant was initially created is still set to the previous
default price that existed before the variant default price was changed.
Maybe some logic should exist to check that the selected features prices add
up to the variant default price value and if they do not, then the previous
variant default price thruDate should be set and a new default price
consistent with the feature price sum created.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5438) Virtual feature selection and selected variant price inconsistencies

[
https://issues.apache.org/jira/browse/OFBIZ-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ashish Vijaywargiya updated OFBIZ-5438:
---
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)

Virtual feature selection and selected variant price inconsistencies

Key: OFBIZ-5438
URL: https://issues.apache.org/jira/browse/OFBIZ-5438
Project: OFBiz
Issue Type: Improvement
Components: order
Reporter: Christian Carlow
Assignee: Ashish Vijaywargiya
Priority: Minor

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-3329) commonext component has dependency on party management component

2014-10-18 Thread Divesh Dutta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Divesh Dutta updated OFBIZ-3329:

Attachment: OFBiz-3329-trunk.patch

Removing dependency of framework component from commonext component:

1) Ui labels of CommonExtUiLabels are not used in common component. so not 
loading Ui labels of CommonExtUiLabels  in LookupDecorator of HelpScreens.xml 

2) When ant create-component is used basic component is set up in hot-deploy. 
So when component is created, main-decorator refers to ApplicationDecorator  of 
CommonExt component because it refers to main-decorator of 
framework/resources/templates/CommonScreens.xml . And main-decorator of 
framework/resources/templates/CommonScreens.xml was referring to 
ApplicationDecorator of CommonExt component. So used Global Decorator instead 
of ApplicationDecorator. One who will be using the ant create-component can 
make changes in his custom CommonScreens.xml to use decorator of his choice. 

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel
 Attachments: OFBiz-3329-trunk.patch


 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-3329) commonext component has dependency on party management component

2014-10-18 Thread Divesh Dutta (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176005#comment-14176005
 ] 

Divesh Dutta commented on OFBIZ-3329:
-


OFBiz-3329-trunk.patch should also work on OFBiz 13.07 

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel
 Attachments: OFBiz-3329-trunk.patch


 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5632) Changing Visual theme in Order manager results in error message

[
https://issues.apache.org/jira/browse/OFBIZ-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ashish Vijaywargiya closed OFBIZ-5632.
--

Changing Visual theme in Order manager results in error message
---

Key: OFBIZ-5632
URL: https://issues.apache.org/jira/browse/OFBIZ-5632
Project: OFBiz
Issue Type: Bug
Components: order
Affects Versions: Release Branch 13.07, Trunk
Environment: Primarily tested on Ubuntu, but affects all OS.
Reporter: Vyom Jain
Assignee: Ashish Vijaywargiya
Attachments: ChangeVisualTheme.png, OFBIZ-5632_12.04.patch,
OFBIZ-5632_trunk_13.07.patch, RemoveCart.png

The reported issue has been observed in the order manager application. It
happens when there's no shopping cart in the session.
Steps to test -
1. Try changing visual theme in the order manager application.
Observations -
1. Returns ERROR MESSAGE - org.ofbiz.widget.screen.ScreenRenderException:
Error rendering screen
[component://order/widget/ordermgr/OrderEntryOrderScreens.xml#quickFinalizeOrder]:
java.lang.IllegalArgumentException: Error running script at location
[component://order/webapp/ordermgr/WEB-INF/actions/entry/CheckoutPayment.groovy]:
java.lang.NullPointerException: Cannot invoke method getRelated() on null
object (Error running script at location
[component://order/webapp/ordermgr/WEB-INF/actions/entry/CheckoutPayment.groovy]:
java.lang.NullPointerException: Cannot invoke method getRelated() on null
object)
Thanks.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel closed OFBIZ-3329.
---

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel
 Attachments: OFBiz-3329-trunk.patch


 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel resolved OFBIZ-3329.
-
Resolution: Fixed

Fix applied to Trunk and Release 13.07. 
Thanks Divesh, Mridul for fix and Adrian and Chris for reporting the issue.

 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel
 Attachments: OFBiz-3329-trunk.patch


 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-1006) Webtools Find on Credit Card entity fails

2014-10-18 Thread Adrian Crum (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176009#comment-14176009
 ] 

Adrian Crum commented on OFBIZ-1006:


This was fixed in the trunk, but it still exists in the branches.

 Webtools Find on Credit Card entity fails
 -

 Key: OFBIZ-1006
 URL: https://issues.apache.org/jira/browse/OFBIZ-1006
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Reporter: Dave Tenerowicz
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-1006.png


 Attempting a find operation on cardNumber column fails  to find records 
 (using webtools/entity reference) in the Credit Card entity. Suspect this is 
 related to encrypted values in the column. Find operation should encrypt the 
 value entered in the search field before executing SQL query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176010#comment-14176010
 ] 

Deepak Dixit commented on OFBIZ-5823:
-

Hi Pierre,

Are you referring 
http://demo-trunk-ofbiz.apache.org/content/control/WebSiteCms?webSiteId=CmsSite 
screen?

 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5785) Extend freemakerImports support to allow more than one freemarkerImports


[ 
https://issues.apache.org/jira/browse/OFBIZ-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176011#comment-14176011
 ] 

Anil K Patel commented on OFBIZ-5785:
-

Adrian,
Deepak's patch looks good to me. I want to make sure you are comfortable before 
we commit it. Please let us know if you like this patch or if you will like to 
handle it differently.

 Extend freemakerImports support to allow more than one freemarkerImports
 

 Key: OFBIZ-5785
 URL: https://issues.apache.org/jira/browse/OFBIZ-5785
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk, Upcoming Branch
Reporter: Deepak Dixit
Priority: Minor
 Attachments: OFBIZ-5785.patch


 Need to extend the freemarker imports support so that user can add custom 
 freemarker macros or can override the OOTB macros for customization.
 As per current implementation user need to maintain a patch for the same.
 If we allow to add more then one freemarkerImports.properties (like 
 freemarkerTransforms.properties) then user can add custom imports or can 
 override the OOTB macros without maintaining the patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5826) Shipper Account screen not rendering shipper accounts


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5826.
--

 Shipper Account screen not rendering shipper accounts
 -

 Key: OFBIZ-5826
 URL: https://issues.apache.org/jira/browse/OFBIZ-5826
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Release Branch 13.07, Trunk
Reporter: Deepak Dixit
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: OFBIZ-5826.patch


 Here is the steps to regenerate issue:
 {code}
 PortalPagePortlet portalPageId=PartyProfile 
 portalPortletId=ShipperAccount portletSeqId=1 columnSeqId=1 
 sequenceNum=7/
 {code}
 Upload the PortalPagePortlet data for shipper Account, and go to viewprofile 
 screen. Now add shipper account from shipper account screen.
 Expected Result: Newly added/ all shipper account of party should be listed 
 under shipper account screen.
 Actual Result:
 No shipper accounts are listing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4668) CommunicationEventAndRole entity: Field with name custRequestDate not found


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mridul Pathak updated OFBIZ-4668:
-
Attachment: OFBIZ-4668.patch

In the attached patch I have used form widget attribute 
sort-field-parameter-name to make sort field parameter exclusive to each of 
the list forms. OFBIZ-5105 is similar to this issue, so the patch would fix 
that issue as well.

 CommunicationEventAndRole entity: Field with name custRequestDate not found
 ---

 Key: OFBIZ-4668
 URL: https://issues.apache.org/jira/browse/OFBIZ-4668
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Erwan de FERRIERES
  Labels: portal
 Attachments: OFBIZ-4668.patch


 when displaying this portal page:
 https://localhost:8443/myportal/control/main?portalPageId=MYPORTAL_EMPLOYEE0parentPortalPageId=MYPORTAL_EMPLOYEE
 this message is thrown to the console:
 Message: Roll back error, could not commit transaction, was rolled back 
 instead because of: Error in Service [executeFind]: Error running Find on the 
 CommunicationEventAndRole entity: Field with name custRequestDate not found 
 in the CommunicationEventAndRole Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: svn commit: r1632793 - in /ofbiz/trunk/framework: common/widget/HelpScreens.xml resources/templates/CommonScreens.xml

2014-10-18 Thread Adrian Crum

I don't think we need to change the component templates. This is a 
regression - components created with the ant target will not function 
properly.


Adrian Crum
Sandglass Software
www.sandglass-software.com

On 10/18/2014 3:11 PM, apa...@apache.org wrote:

Author: apatel
Date: Sat Oct 18 14:11:50 2014
New Revision: 1632793

URL: http://svn.apache.org/r1632793
Log:
[OFBIZ-3329] Removing framework code on resources in commonext.
Thanks Divesh and Mridul for helping with resuluation.
Thanks Adrian for reporting it.
Thanks Chris Snow for reporting the issue

Modified:
 ofbiz/trunk/framework/common/widget/HelpScreens.xml
 ofbiz/trunk/framework/resources/templates/CommonScreens.xml

Modified: ofbiz/trunk/framework/common/widget/HelpScreens.xml
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/common/widget/HelpScreens.xml?rev=1632793r1=1632792r2=1632793view=diff
==
--- ofbiz/trunk/framework/common/widget/HelpScreens.xml (original)
+++ ofbiz/trunk/framework/common/widget/HelpScreens.xml Sat Oct 18 14:11:50 2014
@@ -25,7 +25,6 @@ under the License.
  section
  actions
  property-map resource=CommonUiLabels map-name=uiLabelMap 
global=true/
-property-map resource=CommonExtUiLabels map-name=uiLabelMap 
global=true/
  property-map resource=ContentUiLabels map-name=uiLabelMap 
global=true/
  service service-name=getUserPreferenceGroup 
result-map=prefResult
  field-map field-name=userPrefGroupTypeId 
value=GLOBAL_PREFERENCES/

Modified: ofbiz/trunk/framework/resources/templates/CommonScreens.xml
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/resources/templates/CommonScreens.xml?rev=1632793r1=1632792r2=1632793view=diff
==
--- ofbiz/trunk/framework/resources/templates/CommonScreens.xml (original)
+++ ofbiz/trunk/framework/resources/templates/CommonScreens.xml Sat Oct 18 
14:11:50 2014
@@ -17,7 +17,7 @@
  set field=applicationTitle 
value=${uiLabelMap.@component-resource-name@Application} global=true/
  /actions
  widgets
-include-screen name=ApplicationDecorator 
location=component://commonext/widget/CommonScreens.xml/
+include-screen name=GlobalDecorator 
location=component://common/widget/CommonScreens.xml/
  /widgets
  /section
  /screen

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176014#comment-14176014
 ] 

Gaudin Pierre commented on OFBIZ-5823:
--

Hi Deepak,

Yes, if you select one page and add meta data, then for each meta data a 
Content with a DataResource is created.

Thanks

Pierre

 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-4668) CommunicationEventAndRole entity: Field with name custRequestDate not found


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-4668:
--

Assignee: Ashish Vijaywargiya

 CommunicationEventAndRole entity: Field with name custRequestDate not found
 ---

 Key: OFBIZ-4668
 URL: https://issues.apache.org/jira/browse/OFBIZ-4668
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Erwan de FERRIERES
Assignee: Ashish Vijaywargiya
  Labels: portal
 Attachments: OFBIZ-4668.patch


 when displaying this portal page:
 https://localhost:8443/myportal/control/main?portalPageId=MYPORTAL_EMPLOYEE0parentPortalPageId=MYPORTAL_EMPLOYEE
 this message is thrown to the console:
 Message: Roll back error, could not commit transaction, was rolled back 
 instead because of: Error in Service [executeFind]: Error running Find on the 
 CommunicationEventAndRole entity: Field with name custRequestDate not found 
 in the CommunicationEventAndRole Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-4668) CommunicationEventAndRole entity: Field with name custRequestDate not found


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-4668:
--

Assignee: Anil K Patel  (was: Ashish Vijaywargiya)

 CommunicationEventAndRole entity: Field with name custRequestDate not found
 ---

 Key: OFBIZ-4668
 URL: https://issues.apache.org/jira/browse/OFBIZ-4668
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Erwan de FERRIERES
Assignee: Anil K Patel
  Labels: portal
 Attachments: OFBIZ-4668.patch


 when displaying this portal page:
 https://localhost:8443/myportal/control/main?portalPageId=MYPORTAL_EMPLOYEE0parentPortalPageId=MYPORTAL_EMPLOYEE
 this message is thrown to the console:
 Message: Roll back error, could not commit transaction, was rolled back 
 instead because of: Error in Service [executeFind]: Error running Find on the 
 CommunicationEventAndRole entity: Field with name custRequestDate not found 
 in the CommunicationEventAndRole Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-5105) My communication page error


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-5105:
--

Assignee: Ashish Vijaywargiya

 My communication page error
 ---

 Key: OFBIZ-5105
 URL: https://issues.apache.org/jira/browse/OFBIZ-5105
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/projectmgr
Affects Versions: Release 11.04.01, Trunk
Reporter: Naofumi Fukue
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: checkSortField.patch


 My communication page has two widgets. Incomming customer requests and party 
 communications. And each of widget has sortable list table. 
 Two sortable table commonly use sortField parameter. But source database 
 table columns of each widgets are not same. For example, selecting 
 lastModifiedDate or entryDate causes error of one side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5785) Extend freemakerImports support to allow more than one freemarkerImports

2014-10-18 Thread Adrian Crum (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176015#comment-14176015
 ] 

Adrian Crum commented on OFBIZ-5785:


I already suggested a way of handling it differently. I am not opposed to the 
change, I just want to make it clear that the change is unnecessary.

 Extend freemakerImports support to allow more than one freemarkerImports
 

 Key: OFBIZ-5785
 URL: https://issues.apache.org/jira/browse/OFBIZ-5785
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk, Upcoming Branch
Reporter: Deepak Dixit
Priority: Minor
 Attachments: OFBIZ-5785.patch


 Need to extend the freemarker imports support so that user can add custom 
 freemarker macros or can override the OOTB macros for customization.
 As per current implementation user need to maintain a patch for the same.
 If we allow to add more then one freemarkerImports.properties (like 
 freemarkerTransforms.properties) then user can add custom imports or can 
 override the OOTB macros without maintaining the patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-4668) CommunicationEventAndRole entity: Field with name custRequestDate not found


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-4668:
--

Assignee: Ashish Vijaywargiya  (was: Anil K Patel)

 CommunicationEventAndRole entity: Field with name custRequestDate not found
 ---

 Key: OFBIZ-4668
 URL: https://issues.apache.org/jira/browse/OFBIZ-4668
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Erwan de FERRIERES
Assignee: Ashish Vijaywargiya
  Labels: portal
 Attachments: OFBIZ-4668.patch


 when displaying this portal page:
 https://localhost:8443/myportal/control/main?portalPageId=MYPORTAL_EMPLOYEE0parentPortalPageId=MYPORTAL_EMPLOYEE
 this message is thrown to the console:
 Message: Roll back error, could not commit transaction, was rolled back 
 instead because of: Error in Service [executeFind]: Error running Find on the 
 CommunicationEventAndRole entity: Field with name custRequestDate not found 
 in the CommunicationEventAndRole Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-4668) CommunicationEventAndRole entity: Field with name custRequestDate not found


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-4668.
--
Resolution: Fixed

Thanks Mridul for the contribution and thanks Erwan for Creating the issue. 
Changes are committed in trunk and RB13.07 at r1632801 and r1632802 
respectively. 

 CommunicationEventAndRole entity: Field with name custRequestDate not found
 ---

 Key: OFBIZ-4668
 URL: https://issues.apache.org/jira/browse/OFBIZ-4668
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Erwan de FERRIERES
Assignee: Ashish Vijaywargiya
  Labels: portal
 Attachments: OFBIZ-4668.patch


 when displaying this portal page:
 https://localhost:8443/myportal/control/main?portalPageId=MYPORTAL_EMPLOYEE0parentPortalPageId=MYPORTAL_EMPLOYEE
 this message is thrown to the console:
 Message: Roll back error, could not commit transaction, was rolled back 
 instead because of: Error in Service [executeFind]: Error running Find on the 
 CommunicationEventAndRole entity: Field with name custRequestDate not found 
 in the CommunicationEventAndRole Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-5105) My communication page error


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-5105.
--
Resolution: Fixed

Based on Mridul's comment on OFBIZ-4668, we can close this issue. 

 My communication page error
 ---

 Key: OFBIZ-5105
 URL: https://issues.apache.org/jira/browse/OFBIZ-5105
 Project: OFBiz
  Issue Type: Bug
  Components: order, specialpurpose/projectmgr
Affects Versions: Release 11.04.01, Trunk
Reporter: Naofumi Fukue
Assignee: Ashish Vijaywargiya
Priority: Minor
 Attachments: checkSortField.patch


 My communication page has two widgets. Incomming customer requests and party 
 communications. And each of widget has sortable list table. 
 Two sortable table commonly use sortField parameter. But source database 
 table columns of each widgets are not same. For example, selecting 
 lastModifiedDate or entryDate causes error of one side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4461) Packaging slip for Purchase order related to drop shipment is empty

2014-10-18 Thread Kiran Gawde (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176019#comment-14176019
]

Kiran Gawde commented on OFBIZ-4461:

Hello Pranay,

If you want to put brand logo on the packaging slip no matter who ships it,
you need to make such packaging slip available to supplier. In our case, we
were planning to email the packaging slip and order to supplier. Hence we
were looking to generate packaging slip.

Regards,
Kiran Gawde

Senior Software Architect
Object Edge Inc
925 943 5558 x108
There are two kind of people: Those who do the work and those who take the
credit. Try to be in the first group because there is less competition
there.
Never give up on what you really want to do. The person with big dreams is
more powerful than one with all the facts - Albert Einsteine.

On Sat, Oct 18, 2014 at 3:24 AM, Pranay Pandey (JIRA) j...@apache.org

This email message (including any attachments) is for the sole use of the
intended recipient and may contain confidential and privileged information.
Any unauthorized review; use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply
email and destroy all copies of the original message.
Thank you.

Packaging slip for Purchase order related to drop shipment is empty
---

Key: OFBIZ-4461
URL: https://issues.apache.org/jira/browse/OFBIZ-4461
Project: OFBiz
Issue Type: Bug
Components: order
Affects Versions: Trunk
Reporter: Kiran Gawde

1. Place an order for product under drop shipment category.
2. Select the order in admin
3. Choose the associated purchase order
4. Approve the purchase order
5. Click on 'Quick Drop Ship'
6. Shipment and Packaging Slip button appear.
7. Click on packaging slip.
Issue: It will say: ERROR: No packages found for this shipment

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5785) Extend freemakerImports support to allow more than one freemarkerImports


[ 
https://issues.apache.org/jira/browse/OFBIZ-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176021#comment-14176021
 ] 

Anil K Patel commented on OFBIZ-5785:
-

Deepak,
Let us write a sample code as per Adrian's recommendations. May be all we need 
is well documented best practice for adding marcros. 

 Extend freemakerImports support to allow more than one freemarkerImports
 

 Key: OFBIZ-5785
 URL: https://issues.apache.org/jira/browse/OFBIZ-5785
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: Trunk, Upcoming Branch
Reporter: Deepak Dixit
Priority: Minor
 Attachments: OFBIZ-5785.patch


 Need to extend the freemarker imports support so that user can add custom 
 freemarker macros or can override the OOTB macros for customization.
 As per current implementation user need to maintain a patch for the same.
 If we allow to add more then one freemarkerImports.properties (like 
 freemarkerTransforms.properties) then user can add custom imports or can 
 override the OOTB macros without maintaining the patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4461) Packaging slip for Purchase order related to drop shipment is empty


[ 
https://issues.apache.org/jira/browse/OFBIZ-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176023#comment-14176023
 ] 

Pranay Pandey commented on OFBIZ-4461:
--

Thanks Kiran, that makes sense. In this case may be the appropriate solution 
would be to create a default package and put all the shipment items in it. So 
that packaging slip shows items in case of dropship PO.

 Packaging slip for Purchase order related to drop shipment is empty
 ---

 Key: OFBIZ-4461
 URL: https://issues.apache.org/jira/browse/OFBIZ-4461
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Kiran Gawde

 1. Place an order for product under drop shipment category.
 2. Select the order in admin
 3. Choose the associated purchase order
 4. Approve the purchase order
 5. Click on 'Quick Drop Ship'
 6. Shipment and Packaging Slip button appear.
 7. Click on packaging slip. 
 Issue: It will say: ERROR: No packages found for this shipment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5823) Add CMS metadata into renderer context


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit updated OFBIZ-5823:

Attachment: Screen Shot 2014-10-18 at 8.19.17 PM.png

Hi Pierre,

I am not able to add the metadata from the 
http://demo-trunk-ofbiz.apache.org/content/control/WebSiteCms?webSiteId=CmsSite 
screen?

I am trying to add sub-content from content tree.

 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch, Screen Shot 2014-10-18 at 8.19.17 
 PM.png


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-4461) Packaging slip for Purchase order related to drop shipment is empty


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya updated OFBIZ-4461:
---
  Priority: Minor  (was: Major)
Issue Type: Improvement  (was: Bug)

 Packaging slip for Purchase order related to drop shipment is empty
 ---

 Key: OFBIZ-4461
 URL: https://issues.apache.org/jira/browse/OFBIZ-4461
 Project: OFBiz
  Issue Type: Improvement
  Components: order
Affects Versions: Trunk
Reporter: Kiran Gawde
Priority: Minor

 1. Place an order for product under drop shipment category.
 2. Select the order in admin
 3. Choose the associated purchase order
 4. Approve the purchase order
 5. Click on 'Quick Drop Ship'
 6. Shipment and Packaging Slip button appear.
 7. Click on packaging slip. 
 Issue: It will say: ERROR: No packages found for this shipment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4461) Packaging slip for Purchase order related to drop shipment is empty


[ 
https://issues.apache.org/jira/browse/OFBIZ-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176024#comment-14176024
 ] 

Pranay Pandey commented on OFBIZ-4461:
--

We should change the issue type to improvement.

 Packaging slip for Purchase order related to drop shipment is empty
 ---

 Key: OFBIZ-4461
 URL: https://issues.apache.org/jira/browse/OFBIZ-4461
 Project: OFBiz
  Issue Type: Bug
  Components: order
Affects Versions: Trunk
Reporter: Kiran Gawde

 1. Place an order for product under drop shipment category.
 2. Select the order in admin
 3. Choose the associated purchase order
 4. Approve the purchase order
 5. Click on 'Quick Drop Ship'
 6. Shipment and Packaging Slip button appear.
 7. Click on packaging slip. 
 Issue: It will say: ERROR: No packages found for this shipment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (OFBIZ-3329) commonext component has dependency on party management component


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anil K Patel reopened OFBIZ-3329:
-

We will discuss part of the code changes made in previous commit related to 
this issue. Its possible that we will revert partial code change.


 commonext component has dependency on party management component
 

 Key: OFBIZ-3329
 URL: https://issues.apache.org/jira/browse/OFBIZ-3329
 Project: OFBiz
  Issue Type: Bug
  Components: commonext/setup
Affects Versions: Trunk
Reporter: chris snow
Assignee: Anil K Patel
 Attachments: OFBiz-3329-trunk.patch


 I've just tried commenting out all components except commonext on trunk (i.e. 
 in component-load.xml).
 I  ran the ant tasks create-admin-user-login, then run and then tried to
 access the url https://localhost:8443/webtools/
 I received the following error message:
 org.ofbiz.widget.screen.ScreenRenderException: Error rendering
 screen [component://common/widget/CommonScreens.xml#GlobalDecorator]:
 org.ofbiz.base.util.GeneralException: Error running Groovy script at
 location [component://commonext/script/changeOrgPartyId.groovy] (Could
 not find definition for entity name PartyAcctgPrefAndGroup) (Error
 running Groovy script at location
 [component://commonext/script/changeOrgPartyId.groovy] (Could not find
 definition for entity name PartyAcctgPrefAndGroup))
 It seems that commonext has a dependency on the party component.  I'm not 
 sure is this is an issue - is there any guidelines on what dependencies can 
 go in commonext?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-3382) inter-app hyperlink generates incorrect url


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya reassigned OFBIZ-3382:
--

Assignee: Ashish Vijaywargiya

 inter-app hyperlink generates incorrect url
 ---

 Key: OFBIZ-3382
 URL: https://issues.apache.org/jira/browse/OFBIZ-3382
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk
Reporter: Nathan Liang
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-3382.patch


 steps to reproduce:
 1, defines a hyper link as the following in component projectmgr:
 link url-mode=inter-app target=/mytest/control/main text=Create my test 
 document style=smallSubmit
 parameter 
 param-name=workEffortId/
 parameter param-name=returnUrl 
 value=/projectmgr/control/EditTaskContents?workEffortId=${workEffortId}/
 /link
 parameter returnUrl is the url that external app can return back.
 2, defines a hyper link as the following in component mytest
 section
 condition
 not
 if-empty field=returnUrl/
 /not
 /condition
 widgets
 container
 link url-mode=inter-app 
 text=Back
   target=${returnUrl} 
 style=smallSubmit
 /link
 /container
 /widgets
 /section
 3. click generated url from component projectmgr to jump to component mytest, 
 parameter returnUrl will be encoded as string: 
 #47;projectmgr#47;control#47;EditTaskContents#63;workEffortId#61;10003
 4, from component mytest, we have the incorrectly generated url 
 http://localhost:8080/projectmgr/control/EditTaskContents?workEffortId=10003?externalLoginKey=,
  two ? characters in the generated url, can not go back the task screen in 
 projectmgr from that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-3382) inter-app hyperlink generates incorrect url


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pranay Pandey updated OFBIZ-3382:
-
Attachment: OFBIZ-3382.patch

Issue is reproducible with given steps. Supplying slightly updated patch. 
Thanks Nathan.

 inter-app hyperlink generates incorrect url
 ---

 Key: OFBIZ-3382
 URL: https://issues.apache.org/jira/browse/OFBIZ-3382
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk
Reporter: Nathan Liang
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-3382.patch, OFBIZ-3382.patch


 steps to reproduce:
 1, defines a hyper link as the following in component projectmgr:
 link url-mode=inter-app target=/mytest/control/main text=Create my test 
 document style=smallSubmit
 parameter 
 param-name=workEffortId/
 parameter param-name=returnUrl 
 value=/projectmgr/control/EditTaskContents?workEffortId=${workEffortId}/
 /link
 parameter returnUrl is the url that external app can return back.
 2, defines a hyper link as the following in component mytest
 section
 condition
 not
 if-empty field=returnUrl/
 /not
 /condition
 widgets
 container
 link url-mode=inter-app 
 text=Back
   target=${returnUrl} 
 style=smallSubmit
 /link
 /container
 /widgets
 /section
 3. click generated url from component projectmgr to jump to component mytest, 
 parameter returnUrl will be encoded as string: 
 #47;projectmgr#47;control#47;EditTaskContents#63;workEffortId#61;10003
 4, from component mytest, we have the incorrectly generated url 
 http://localhost:8080/projectmgr/control/EditTaskContents?workEffortId=10003?externalLoginKey=,
  two ? characters in the generated url, can not go back the task screen in 
 projectmgr from that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-3382) inter-app hyperlink generates incorrect url


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashish Vijaywargiya closed OFBIZ-3382.
--
Resolution: Fixed

Thanks Nathan for creating the issue and Thanks Pranay for the contribution. 
Changes are committed in trunk at r1632803 and in RB13.07 at r1632804

 inter-app hyperlink generates incorrect url
 ---

 Key: OFBIZ-3382
 URL: https://issues.apache.org/jira/browse/OFBIZ-3382
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk
Reporter: Nathan Liang
Assignee: Ashish Vijaywargiya
 Attachments: OFBIZ-3382.patch, OFBIZ-3382.patch


 steps to reproduce:
 1, defines a hyper link as the following in component projectmgr:
 link url-mode=inter-app target=/mytest/control/main text=Create my test 
 document style=smallSubmit
 parameter 
 param-name=workEffortId/
 parameter param-name=returnUrl 
 value=/projectmgr/control/EditTaskContents?workEffortId=${workEffortId}/
 /link
 parameter returnUrl is the url that external app can return back.
 2, defines a hyper link as the following in component mytest
 section
 condition
 not
 if-empty field=returnUrl/
 /not
 /condition
 widgets
 container
 link url-mode=inter-app 
 text=Back
   target=${returnUrl} 
 style=smallSubmit
 /link
 /container
 /widgets
 /section
 3. click generated url from component projectmgr to jump to component mytest, 
 parameter returnUrl will be encoded as string: 
 #47;projectmgr#47;control#47;EditTaskContents#63;workEffortId#61;10003
 4, from component mytest, we have the incorrectly generated url 
 http://localhost:8080/projectmgr/control/EditTaskContents?workEffortId=10003?externalLoginKey=,
  two ? characters in the generated url, can not go back the task screen in 
 projectmgr from that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5823) Add CMS metadata into renderer context


[ 
https://issues.apache.org/jira/browse/OFBIZ-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176039#comment-14176039
 ] 

Gaudin Pierre commented on OFBIZ-5823:
--

Hi Deepak,

OK,

Click one page from the content tree (ie CMS Site Demo blog screen example [ 
CMSS_DEMO_BLOG ])
On the right side of the tree, the content is shown. Above shown content , 
there is 3 links in black color. Select link Meta Tags . Then add the value 
and save. 

Please, find a screen shot as attachment.

Thanks,

Pierre

 Add CMS metadata into renderer context
 --

 Key: OFBIZ-5823
 URL: https://issues.apache.org/jira/browse/OFBIZ-5823
 Project: OFBiz
  Issue Type: Improvement
  Components: content, specialpurpose/cmssite
Affects Versions: Trunk
Reporter: Gaudin Pierre
Priority: Minor
 Fix For: Trunk

 Attachments: CMSMetadata.patch, Screen Shot 2014-10-18 at 8.19.17 
 PM.png


 In website CMS, for a page, you can specify metadata.
 Unfortunatly those metadata are not availables into the cms page context.
 This patch add metadata into context of all pages. Thus you can use them.
 To test this patch, add metadata  associated to a cms page (ie 
 metaDescription).
 Edit the cms page to add ${metaDescription}.
 Then display the page 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5823) Add CMS metadata into renderer context