[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3633:
---------------------------
Attachment: SOLR-3633.patch
I have just enough javascript knowledge to be dangerous....
Here's my meger attempt at trying to deal with this.
This patch now:
* prefers the default core for loading /admin/system
* includes the URL that failed to load in the error msg if /admin/system
couldn't load
* distinguishes between there not being any cores, and not being able to load
/admin/system.
Un fortunatley, the result is still that the admin UI is virtually useless --
my hope was to at least have the "Add Core" button working, but the way/place
the core admin buttons are generated is down deep in code for binding to
loading the page for a specific core -- which in this patch never gets called
since there are no cores.
I've reached the limit of how much i understand this stuff ... maybe someone
will find this patch useful and be able to keep going along these lines so that
the CoreAdmin stuff at least works, and then the other tabs will start to work
once a core is added (allthough i'm not sure how to force all that other data
to reload if/when a core is added)
---
If we can't make progress on this soon, then it would be best to commit a
simpler error check for no cores that hides all the navigation (much like hte
current "you need the /admin/ handler") with a clear message that there are no
cores
> web UI reports and error if CoreAdminHandler says there are no SolrCores
> ------------------------------------------------------------------------
>
> Key: SOLR-3633
> URL: https://issues.apache.org/jira/browse/SOLR-3633
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 4.0-ALPHA
> Reporter: Hoss Man
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3633.patch
>
>
> Spun off from SOLR-3591...
> * having no SolrCores is a valid situation
> * independent of what may happen in SOLR-3591, the web UI should cleanly deal
> with there being no SolrCores, and just hide/grey out any tabs that can't be
> supported w/o at least one core
> * even if there are no SolrCores the core admin features (ie: creating a new
> core) should be accessible in the UI
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
