Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 95C41200C56 for ; Fri, 31 Mar 2017 06:33:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 944FB160B9A; Fri, 31 Mar 2017 04:33:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D7119160B8B for ; Fri, 31 Mar 2017 06:33:46 +0200 (CEST) Received: (qmail 27942 invoked by uid 500); 31 Mar 2017 04:33:45 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 27925 invoked by uid 99); 31 Mar 2017 04:33:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Mar 2017 04:33:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 00EEA1A0375 for ; Fri, 31 Mar 2017 04:33:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wSAFVjpG7db0 for ; Fri, 31 Mar 2017 04:33:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 160D25FC4A for ; Fri, 31 Mar 2017 04:33:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 98793E0BD2 for ; Fri, 31 Mar 2017 04:33:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 748DC21DDA for ; Fri, 31 Mar 2017 04:33:42 +0000 (UTC) Date: Fri, 31 Mar 2017 04:33:42 +0000 (UTC) From: "Aditya Sharma (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OFBIZ-7759) Link in LookupContent causes unwanted behaviour MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 31 Mar 2017 04:33:47 -0000 [ https://issues.apache.org/jira/browse/OFBIZ-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Sharma updated OFBIZ-7759: --------------------------------- Attachment: OFBIZ-7759.patch > Link in LookupContent causes unwanted behaviour > ----------------------------------------------- > > Key: OFBIZ-7759 > URL: https://issues.apache.org/jira/browse/OFBIZ-7759 > Project: OFBiz > Issue Type: Bug > Components: content > Affects Versions: Trunk > Reporter: Montalbano Florian > Assignee: Aditya Sharma > Priority: Minor > Labels: content, locale, lookup > Attachments: OFBIZ-7759.patch, OFBIZ-7759.patch > > > How to reproduce : > - Log in the Content component > - Go to the Content tab > - In the search form, open the lookup of the field ' Owner Content Id ' > - Click on the search button > - In the result list, click on a button link in the column 'Data Resource Id' > - The form to edit the Content will be displayed (a whole OFBiz seems to be accessible from this new page) > - Close the lookup. > - Try to reopen it, it doesn't show anything anymore. > The only hint I've found for explaining this problem is that the request to open the lookup is somehow changed. > At first it is : > https://localhost:8443/content/control/LookupContent > But then it becomes : > https://localhost:8443/content/control/LookupLocale > The other lookup seems unusable too after that. > Did you already encounter this kind of problem before ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)