[
https://issues.apache.org/jira/browse/OFBIZ-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427368#comment-13427368
]
Tom Burns commented on OFBIZ-4752:
----------------------------------
Sascha,
I am sorry but I did not see your prior post on this issue so I'm a bit late
with a response.
I think there is still an issue here.
In the FE the "indexTree" service is invoked from the index tab where there are
two options:
1. AdminIndex and 2. AdminIndexAll.
1. AdminIndex does nothing even though the label says "Content ids to index
(separate ids with a space)" (fooled you again user)!
The controller only refreshes the view when with target="AdminIndex", form code
follows.
<form name="AdminIndex" target="AdminIndex" title="" type="single"
header-row-style="header-row" default-table-style="basic-table">
<field name="indexContentIds" position="1"><text size="50"/></field>
<field name="submitButton" title="${uiLabelMap.ContentIndexEnteredIds}"
widget-style="smallSubmit" position="2"><submit button-type="button"/></field>
</form>
2. AdminIndexAll runs the "indexTree" service but generates an error when sent
the default value WebStoreCONTENT (see screen shot). You no longer get an
error when you click the Find button in the Find tab but you do not get any
data either.
OOB the Find tab could handle the OOB case of no index more gracefully (present
a meaningful message) and I would expect that the default value in the Index
tab would result in some records being returned in find.
Also in the Find tab the drop-down list Select Category is empty - what's that
about?
Tom
> Error in Content > CMS click Find
> ---------------------------------
>
> Key: OFBIZ-4752
> URL: https://issues.apache.org/jira/browse/OFBIZ-4752
> Project: OFBiz
> Issue Type: Bug
> Components: content
> Affects Versions: SVN trunk
> Environment: demo-trunk
> Reporter: Tom Burns
> Assignee: Sascha Rodekamp
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: index_error.jpg
>
>
> To reproduce:
> In Content Manager
> (https://demo-trunk.ofbiz.apache.org/content/control/CMSContentFind)
> select CMS then click "Find" button located above the title "CMS Content
> Find"
> Expected: ?
> Actual: Error message
> org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen
> [component://content/widget/cms/CMSScreens.xml#AdminSearch]:
> java.lang.IllegalArgumentException: Error running script at location
> [component://content/webapp/content/WEB-INF/actions/cms/Search.groovy]:
> javax.script.ScriptException: org.apache.lucene.index.IndexNotFoundException:
> no segments* file found in
> org.apache.lucene.store.MMapDirectory@/home/ofbiz/trunk/applications/content/index
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@4bbbf4ee: files:
> [indexhere.txt] (Error running script at location
> [component://content/webapp/content/WEB-INF/actions/cms/Search.groovy]:
> javax.script.ScriptException: org.apache.lucene.index.IndexNotFoundException:
> no segments* file found in
> org.apache.lucene.store.MMapDirectory@/home/ofbiz/trunk/applications/content/index
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@4bbbf4ee: files:
> [indexhere.txt])
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
