[jira] [Updated] (OFBIZ-10386) Empty field is reflecting on Contact list section on Profile Page

2020-11-25 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-10386:
-
Sprint: OFBiz Community Day (Nov 2020)

> Empty field is reflecting on Contact list section on Profile Page
> -
>
> Key: OFBIZ-10386
> URL: https://issues.apache.org/jira/browse/OFBIZ-10386
> Project: OFBiz
>  Issue Type: Bug
> Environment: https://demo-trunk.ofbiz.apache.org/ecomseo/viewprofile
>Reporter: Archana Asthana
>Assignee: Devanshu Vyas
>Priority: Major
> Attachments: EmptyFields.png, ViewProfileV2.patch
>
>
> Steps to generate: 
> Open https://demo-trunk.ofbiz.apache.org/ecomseo/viewprofile
> On the profile page, Go down to Contact list
> Empty fields are displaying before Verify Subscription button
> Expected: The field should have some specifications to be filled up
> Image is attached for reference



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-10971) Use ReturnContactMech entity

2020-08-18 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-10971:
-
Sprint: OFBiz Community Day (Aug 2020)

> Use ReturnContactMech entity
> 
>
> Key: OFBIZ-10971
> URL: https://issues.apache.org/jira/browse/OFBIZ-10971
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Vaibhav Jain
>Assignee: Devanshu Vyas
>Priority: Major
>
> Use ReturnContactMech entity to capture the contactMech information of 
> parties involved in a return like OrderContactMech is used of orders



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-05-25 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116423#comment-17116423
 ] 

Swapnil Mane commented on OFBIZ-11472:
--

Thank you [~jleroux], was waiting for your approval.
Closing the ticket, thanks!

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Closed] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-05-25 Thread Swapnil Mane (Jira)


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

Swapnil Mane closed OFBIZ-11472.

Resolution: Done

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-05-20 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-11472:
-
Sprint: OFBiz Community Day (May 2020)

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-04-14 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083235#comment-17083235
 ] 

Swapnil Mane commented on OFBIZ-11472:
--

Hello team,
 The demo instance for 17.12 release is live at 
[https://demo-stable.ofbiz.apache.org/ecommerce/control/main]

All the script are updated on [OFBiz 
tools|https://github.com/apache/ofbiz-tools] repository and details on OFBiz 
website too.
 Also the updates are shared on users list [https://s.apache.org/kn153] 

Thank you so much [~jleroux] for your great help! :)

As discussed, 
Please feel free to update the details on Let's Encrypt in 
ofbiz-tools/demo-backup/README file as per your convenience.

Thanks again

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064495#comment-17064495
 ] 

Swapnil Mane edited comment on OFBIZ-11472 at 3/23/20, 2:47 AM:


Hello team,
 Here is the PR to update the deployment scripts to set up the demo instance 
for OFBiz 17.12 release and obsolete 13.07 demo.

[https://github.com/apache/ofbiz-tools/pull/2]

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :
 # {color:#0e101a}Clone the 17.12 release branch on VM 
{color}{color:#0e101a}git clone -b release17.12 
{color}[https://gitbox.apache.org/repos/asf/ofbiz-framework.git] 
{color:#0e101a}branch17.12{color}
 # {color:#0e101a}Update the deployment scripts on VM as per the PR
 [https://github.com/apache/ofbiz-tools/pull/2] {color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7{color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
 @Team,
 Please have a look and let me know your kind feedback.
 
 Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 


was (Author: swapnilmmane):
Hello team,
 Here is the PR to update the deployment scripts to set up the demo instance 
for OFBiz 17.12 release and obsolete 13.07 demo.

[https://github.com/apache/ofbiz-tools/pull/2]

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :
 # {color:#0e101a}Clone the 17.12 release branch on VM{color}

{color:#0e101a}git clone -b release17.12 
{color}[{color:#4a6ee0}[https://gitbox.apache.org/repos/asf/ofbiz-framework.git]{color}]{color:#0e101a}
 branch17.12{color}
 # {color:#0e101a}Update the deployment scripts on VM as per the PR
[https://github.com/apache/ofbiz-tools/pull/2] 
{color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7
 {color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
 @Team,
 Please have a look and let me know your kind feedback.
 
 Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064495#comment-17064495
 ] 

Swapnil Mane edited comment on OFBIZ-11472 at 3/23/20, 2:47 AM:


Hello team,
 Here is the PR to update the deployment scripts to set up the demo instance 
for OFBiz 17.12 release and obsolete 13.07 demo.

[https://github.com/apache/ofbiz-tools/pull/2]

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :
 # {color:#0e101a}Clone the 17.12 release branch on VM 
{color}{color:#0e101a}git clone -b release17.12 
{color}[https://gitbox.apache.org/repos/asf/ofbiz-framework.git] 
{color:#0e101a}branch17.12{color}
 # {color:#0e101a}Update the deployment scripts on VM as per the PR
 [https://github.com/apache/ofbiz-tools/pull/2] {color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7{color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
 @Team,
 Please have a look and let me know your kind feedback.
 
 Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 


was (Author: swapnilmmane):
Hello team,
 Here is the PR to update the deployment scripts to set up the demo instance 
for OFBiz 17.12 release and obsolete 13.07 demo.

[https://github.com/apache/ofbiz-tools/pull/2]

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :
 # {color:#0e101a}Clone the 17.12 release branch on VM 
{color}{color:#0e101a}git clone -b release17.12 
{color}[https://gitbox.apache.org/repos/asf/ofbiz-framework.git] 
{color:#0e101a}branch17.12{color}
 # {color:#0e101a}Update the deployment scripts on VM as per the PR
 [https://github.com/apache/ofbiz-tools/pull/2] {color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7{color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
 @Team,
 Please have a look and let me know your kind feedback.
 
 Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064495#comment-17064495
 ] 

Swapnil Mane edited comment on OFBIZ-11472 at 3/23/20, 2:46 AM:


Hello team,
 Here is the PR to update the deployment scripts to set up the demo instance 
for OFBiz 17.12 release and obsolete 13.07 demo.

[https://github.com/apache/ofbiz-tools/pull/2]

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :
 # {color:#0e101a}Clone the 17.12 release branch on VM{color}

{color:#0e101a}git clone -b release17.12 
{color}[{color:#4a6ee0}[https://gitbox.apache.org/repos/asf/ofbiz-framework.git]{color}]{color:#0e101a}
 branch17.12{color}
 # {color:#0e101a}Update the deployment scripts on VM as per the PR
[https://github.com/apache/ofbiz-tools/pull/2] 
{color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7
 {color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
 @Team,
 Please have a look and let me know your kind feedback.
 
 Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 


was (Author: swapnilmmane):
Hello team,
Here is the PR to update the deployment scripts to set up the demo instance for 
OFBiz 17.12 release and obsolete 13.07 demo.

https://github.com/apache/ofbiz-tools/pull/2

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :


 # {color:#0e101a}Clone the 17.12 release branch on VM{color}

{color:#0e101a}git clone -b release17.12 
{color}[{color:#4a6ee0}https://gitbox.apache.org/repos/asf/ofbiz-framework.git{color}]{color:#0e101a}
 branch17.12
{color}

 # {color:#0e101a}Update the deployment scripts on VM as per the PR
[https://github.com/apache/ofbiz-tools/pull/2
]
{color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7

{color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
@Team,
Please have a look and let me know your kind feedback.

Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064495#comment-17064495
 ] 

Swapnil Mane commented on OFBIZ-11472:
--

Hello team,
Here is the PR to update the deployment scripts to set up the demo instance for 
OFBiz 17.12 release and obsolete 13.07 demo.

https://github.com/apache/ofbiz-tools/pull/2

After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :


 # {color:#0e101a}Clone the 17.12 release branch on VM{color}

{color:#0e101a}git clone -b release17.12 
{color}[{color:#4a6ee0}https://gitbox.apache.org/repos/asf/ofbiz-framework.git{color}]{color:#0e101a}
 branch17.12
{color}

 # {color:#0e101a}Update the deployment scripts on VM as per the PR
[https://github.com/apache/ofbiz-tools/pull/2
]
{color}
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 2 was occupied by 13.7

{color}
 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 
instances.{color}

{color:#0e101a}
@Team,
Please have a look and let me know your kind feedback.

Thank you so much [~jleroux] for your inputs and guidance in this.{color}

 

> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> ---
>
> Key: OFBIZ-11472
> URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> Project: OFBiz
>  Issue Type: Task
>  Components: Demo
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
>  
> For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

2020-03-22 Thread Swapnil Mane (Jira)
Swapnil Mane created OFBIZ-11472:


 Summary: Demo instance setup for OFBiz 17.12 release and obsolete 
13.07 demo
 Key: OFBIZ-11472
 URL: https://issues.apache.org/jira/browse/OFBIZ-11472
 Project: OFBiz
  Issue Type: Task
  Components: Demo
Reporter: Swapnil Mane
Assignee: Swapnil Mane


As discussed at [https://s.apache.org/kn1f9] thread,

We will setup new demo instance for 17.12 and obsolete 13.07. 
The OFBiz demos are hosted at ofbiz-vm3.apache.org VM

Currently, OFBiz has three demo instance:
-- Previous Stable Release 13.07 - Demo
https://demo-old.ofbiz.apache.org/ordermgr/control/main

-- Current Stable Release 16.11 - Demo
https://demo-stable.ofbiz.apache.org/ordermgr/control/main

-- Developer Trunk - Demo
https://demo-trunk.ofbiz.apache.org/ordermgr/control/main

So, as per new plan.
https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
pointed at https://demo-stable.ofbiz.apache.org)


And the newly setup 17.12 will be served at https://demo-stable.ofbiz.apache.org
 
For this, we will need to make changes in the deployment scripts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OFBIZ-11471) Git PR notifications should be sent to notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064212#comment-17064212
 ] 

Swapnil Mane edited comment on OFBIZ-11471 at 3/22/20, 9:17 AM:


Oh, mistakenly created ticket in OFBiz space, 
I thought, I was selecting the Project field as OFBiz on Infra Jira ticket.
 Apologies, closing the ticket.


was (Author: swapnilmmane):
Oh, mistakenly created ticket in OFBiz space, 
Apologies, closing the ticket.

> Git PR notifications should be sent to notifications@ofbiz.apache.org
> -
>
> Key: OFBIZ-11471
> URL: https://issues.apache.org/jira/browse/OFBIZ-11471
> Project: OFBiz
>  Issue Type: Task
>  Components: git
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>
> Hello Infra team,
> The OFBiz community wants the Pull Request related notifications (like on 
> creation of PR or comment on PR) for following repositories should be sent to 
> [notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.
> [https://github.com/apache/ofbiz]
> [https://github.com/apache/ofbiz-framework]
> [https://github.com/apache/ofbiz-plugins]
> [https://github.com/apache/ofbiz-tools]
>  
> Here is the thread for community consensus on this 
> [https://s.apache.org/zcjc6]
> Please let me know if you need any further information or assistance.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Closed] (OFBIZ-11471) Git PR notifications should be sent to notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)


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

Swapnil Mane closed OFBIZ-11471.

Resolution: Invalid

> Git PR notifications should be sent to notifications@ofbiz.apache.org
> -
>
> Key: OFBIZ-11471
> URL: https://issues.apache.org/jira/browse/OFBIZ-11471
> Project: OFBiz
>  Issue Type: Task
>  Components: git
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>
> Hello Infra team,
> The OFBiz community wants the Pull Request related notifications (like on 
> creation of PR or comment on PR) for following repositories should be sent to 
> [notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.
> [https://github.com/apache/ofbiz]
> [https://github.com/apache/ofbiz-framework]
> [https://github.com/apache/ofbiz-plugins]
> [https://github.com/apache/ofbiz-tools]
>  
> Here is the thread for community consensus on this 
> [https://s.apache.org/zcjc6]
> Please let me know if you need any further information or assistance.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-11471) Git PR notifications should be sent to notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064212#comment-17064212
 ] 

Swapnil Mane commented on OFBIZ-11471:
--

Oh, mistakenly created ticket in OFBiz space, 
Apologies, closing the ticket.

> Git PR notifications should be sent to notifications@ofbiz.apache.org
> -
>
> Key: OFBIZ-11471
> URL: https://issues.apache.org/jira/browse/OFBIZ-11471
> Project: OFBiz
>  Issue Type: Task
>  Components: git
>Reporter: Swapnil Mane
>Priority: Minor
>
> Hello Infra team,
> The OFBiz community wants the Pull Request related notifications (like on 
> creation of PR or comment on PR) for following repositories should be sent to 
> [notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.
> [https://github.com/apache/ofbiz]
> [https://github.com/apache/ofbiz-framework]
> [https://github.com/apache/ofbiz-plugins]
> [https://github.com/apache/ofbiz-tools]
>  
> Here is the thread for community consensus on this 
> [https://s.apache.org/zcjc6]
> Please let me know if you need any further information or assistance.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OFBIZ-11471) Git PR notifications should be sent to notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)


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

Swapnil Mane reassigned OFBIZ-11471:


Assignee: Swapnil Mane

> Git PR notifications should be sent to notifications@ofbiz.apache.org
> -
>
> Key: OFBIZ-11471
> URL: https://issues.apache.org/jira/browse/OFBIZ-11471
> Project: OFBiz
>  Issue Type: Task
>  Components: git
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
>
> Hello Infra team,
> The OFBiz community wants the Pull Request related notifications (like on 
> creation of PR or comment on PR) for following repositories should be sent to 
> [notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.
> [https://github.com/apache/ofbiz]
> [https://github.com/apache/ofbiz-framework]
> [https://github.com/apache/ofbiz-plugins]
> [https://github.com/apache/ofbiz-tools]
>  
> Here is the thread for community consensus on this 
> [https://s.apache.org/zcjc6]
> Please let me know if you need any further information or assistance.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11471) Git PR notifications should be sent to notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-11471:
-
Summary: Git PR notifications should be sent to 
notifications@ofbiz.apache.org  (was: Git PR notifications should be sent 
notifications@ofbiz.apache.org)

> Git PR notifications should be sent to notifications@ofbiz.apache.org
> -
>
> Key: OFBIZ-11471
> URL: https://issues.apache.org/jira/browse/OFBIZ-11471
> Project: OFBiz
>  Issue Type: Task
>  Components: git
>Reporter: Swapnil Mane
>Priority: Minor
>
> Hello Infra team,
> The OFBiz community wants the Pull Request related notifications (like on 
> creation of PR or comment on PR) for following repositories should be sent to 
> [notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.
> [https://github.com/apache/ofbiz]
> [https://github.com/apache/ofbiz-framework]
> [https://github.com/apache/ofbiz-plugins]
> [https://github.com/apache/ofbiz-tools]
>  
> Here is the thread for community consensus on this 
> [https://s.apache.org/zcjc6]
> Please let me know if you need any further information or assistance.
> Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OFBIZ-11471) Git PR notifications should be sent notifications@ofbiz.apache.org

2020-03-22 Thread Swapnil Mane (Jira)
Swapnil Mane created OFBIZ-11471:


 Summary: Git PR notifications should be sent 
notifications@ofbiz.apache.org
 Key: OFBIZ-11471
 URL: https://issues.apache.org/jira/browse/OFBIZ-11471
 Project: OFBiz
  Issue Type: Task
  Components: git
Reporter: Swapnil Mane


Hello Infra team,

The OFBiz community wants the Pull Request related notifications (like on 
creation of PR or comment on PR) for following repositories should be sent to 
[notifications@ofbiz.apache.org|mailto:notifications@ofbiz.apache.org]  list.


[https://github.com/apache/ofbiz]
[https://github.com/apache/ofbiz-framework]
[https://github.com/apache/ofbiz-plugins]
[https://github.com/apache/ofbiz-tools]

 

Here is the thread for community consensus on this 
[https://s.apache.org/zcjc6]

Please let me know if you need any further information or assistance.

Thanks!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-11244) Remove the user login security question

2020-03-13 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058682#comment-17058682
 ] 

Swapnil Mane commented on OFBIZ-11244:
--

Thank you [~wpaetzold] for your contribution.
The patch looks good to me.
Thanks!

 

> Remove the user login security question
> ---
>
> Key: OFBIZ-11244
> URL: https://issues.apache.org/jira/browse/OFBIZ-11244
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ecommerce, framework, party
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Michael Brohl
>Priority: Major
> Attachments: OFBIZ-11244-framework.patch, OFBIZ-11244-plugins.patch
>
>
> After our discussion in dev ML at 
> https://markmail.org/message/2dhc4al4adwgvl7z we will remove this feature. 
> This [~paulfoxworthy]'s remark is notably important:
> bq. Security is only as good as its weakest link ( 
> https://www.schneier.com/essays/archives/2005/02/the_curse_of_the_sec.html) , 
> and security questions can be a real weakness. Any organisation using OFBiz 
> that really hates passwords could look at security keys from Yubico or the 
> like.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10834) Uploading image to data resource

2020-03-07 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054300#comment-17054300
 ] 

Swapnil Mane commented on OFBIZ-10834:
--

Thank you [~jleroux] for validating and sharing the details.

> Uploading image to data resource
> 
>
> Key: OFBIZ-10834
> URL: https://issues.apache.org/jira/browse/OFBIZ-10834
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Release Branch 18.12, Release Branch 17.12, Trunk
>Reporter: Ingo Wolfmayr
>Priority: Major
>
> Content --> DataResource --> "Create new" 
>  * Data Resource Id: some Id
>  * Data Resource Type Id: local file
> --> "create"
> --> Upload --> "select local file" --> upload
> The result is no file uploaded. No error message.
> It works fine in ofbiz 16.11
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-7704) 'original page' field is partially visible in create 'New Portal Page' screen

2020-02-18 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-7704:

Sprint: OFBiz Community Day (Feb 2020)

> 'original page' field is partially visible in create 'New Portal Page' screen
> -
>
> Key: OFBIZ-7704
> URL: https://issues.apache.org/jira/browse/OFBIZ-7704
> Project: OFBiz
>  Issue Type: Bug
>  Components: myportal
>Affects Versions: Trunk
>Reporter: Swapnil Mane
>Assignee: Swapnil Mane
>Priority: Minor
> Attachments: new_portal_page.png
>
>
> In the screen of new portal page creation, the 'original page' is partially 
> visible and going out of the screen.
> Steps to regenerate
> #1) Go to My Portal
> #2) select Preferences sub-menu
> #3) Select the option 'New Portal Page'
> (https://localhost:8443/myportal/control/NewPortalPage?parentPortalPageId=MYPORTAL_EMPLOYEE)
> Please find the attachment for more details.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10833) CMS add content not working

2020-02-18 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039691#comment-17039691
 ] 

Swapnil Mane commented on OFBIZ-10833:
--

Thank you [~mbrohl] and [~sberg]!

> CMS add content not working
> ---
>
> Key: OFBIZ-10833
> URL: https://issues.apache.org/jira/browse/OFBIZ-10833
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, 17.12.01
>Reporter: Ingo Wolfmayr
>Assignee: Michael Brohl
>Priority: Major
> Fix For: 17.12.01, 18.12.01
>
> Attachments: LogCreateContent.txt, OFBIZ-10833.patch, 
> OFBIZ-10833.patch, OFBIZ-10833.patch, cms_addImage.patch
>
>
> On demo: content --> "CmsSite" --> CMS:
> Right click on one of the items to add "New Long Text" or "Image".
> After saving the new content:
> Edit WebSite CMS For: []
> "There is no Content PUBLISH_POINT for this WebSite!"
> Having the same problem on a  17.12 local installation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OFBIZ-10833) CMS add content not working

2020-02-02 Thread Swapnil Mane (Jira)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028326#comment-17028326
 ] 

Swapnil Mane commented on OFBIZ-10833:
--

Hi [~mbrohl],
Thank you for showing kind interest, please feel free to go ahead.
Thank you!

 

> CMS add content not working
> ---
>
> Key: OFBIZ-10833
> URL: https://issues.apache.org/jira/browse/OFBIZ-10833
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, 17.12.01
>Reporter: Ingo Wolfmayr
>Assignee: Swapnil Mane
>Priority: Major
> Fix For: 17.12.01, 18.12.01
>
> Attachments: LogCreateContent.txt, OFBIZ-10833.patch, 
> cms_addImage.patch
>
>
> On demo: content --> "CmsSite" --> CMS:
> Right click on one of the items to add "New Long Text" or "Image".
> After saving the new content:
> Edit WebSite CMS For: []
> "There is no Content PUBLISH_POINT for this WebSite!"
> Having the same problem on a  17.12 local installation.
> h1.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OFBIZ-10833) CMS add content not working

2020-02-02 Thread Swapnil Mane (Jira)


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

Swapnil Mane reassigned OFBIZ-10833:


Assignee: (was: Swapnil Mane)

> CMS add content not working
> ---
>
> Key: OFBIZ-10833
> URL: https://issues.apache.org/jira/browse/OFBIZ-10833
> Project: OFBiz
>  Issue Type: Bug
>  Components: content
>Affects Versions: Trunk, 17.12.01
>Reporter: Ingo Wolfmayr
>Priority: Major
> Fix For: 17.12.01, 18.12.01
>
> Attachments: LogCreateContent.txt, OFBIZ-10833.patch, 
> cms_addImage.patch
>
>
> On demo: content --> "CmsSite" --> CMS:
> Right click on one of the items to add "New Long Text" or "Image".
> After saving the new content:
> Edit WebSite CMS For: []
> "There is no Content PUBLISH_POINT for this WebSite!"
> Having the same problem on a  17.12 local installation.
> h1.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (OFBIZ-10237) The leads which are converted is displayed on the Find lead page.

2020-01-24 Thread Swapnil Mane (Jira)


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

Swapnil Mane reassigned OFBIZ-10237:


Assignee: (was: Swapnil Mane)

> The leads which are converted is displayed on the Find lead page.
> -
>
> Key: OFBIZ-10237
> URL: https://issues.apache.org/jira/browse/OFBIZ-10237
> Project: OFBiz
>  Issue Type: Bug
>  Components: marketing
>Affects Versions: Trunk
>Reporter: Rubia Elza Joshep
>Priority: Major
> Attachments: OFBIZ-10237.patch
>
>
> Steps to regenerate:
> 1) Open URL 
> [https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads|http://example.com/]
> 2) Create a lead. Check for the lead in Find lead page.
> 3) Convert the lead by clicking on "Create Lead" button. The lead is 
> successfully converted to contact/ Account.
> Actual: The lead which is converted is displayed on the Find lead page.
> Expected: Since the lead is converted to contact/Account it should not be 
> displayed on the Find lead page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-10237) The leads which are converted is displayed on the Find lead page.

2019-11-21 Thread Swapnil Mane (Jira)


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

Swapnil Mane updated OFBIZ-10237:
-
Sprint: OFBiz Community Day (Nov 2019)

> The leads which are converted is displayed on the Find lead page.
> -
>
> Key: OFBIZ-10237
> URL: https://issues.apache.org/jira/browse/OFBIZ-10237
> Project: OFBiz
>  Issue Type: Bug
>Reporter: Rubia Elza Joshep
>Assignee: Swapnil Mane
>Priority: Major
> Attachments: OFBIZ-10237.patch
>
>
> Steps to regenerate:
> 1) Open URL 
> [https://demo-trunk.ofbiz.apache.org/sfa/control/FindLeads|http://example.com/]
> 2) Create a lead. Check for the lead in Find lead page.
> 3) Convert the lead by clicking on "Create Lead" button. The lead is 
> successfully converted to contact/ Account.
> Actual: The lead which is converted is displayed on the Find lead page.
> Expected: Since the lead is converted to contact/Account it should not be 
> displayed on the Find lead page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)