[ https://issues.apache.org/jira/browse/SOLR-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976154#action_12976154 ]
Edward Rudd commented on SOLR-975: ---------------------------------- >From looking at the diff it looks like it could fix it.. But it needs to be >verified that it is indeed fixed. I'll at to my TODO list to pull down a >nightly build next week and test. > admin-extra.html not currectly display when using multicore configuration > ------------------------------------------------------------------------- > > Key: SOLR-975 > URL: https://issues.apache.org/jira/browse/SOLR-975 > Project: Solr > Issue Type: Bug > Components: web gui > Affects Versions: 1.4 > Environment: Jetty openjdk 1.6.0 1.0.b12 (EPEL package for EL5) > Reporter: Edward Rudd > > I'm having "cross-talk" issues with using the Solr nightlies (and probably w/ > 1.3.0 release but have not tested as I needed newer features of the > DataImportHandler in the nightlies) > Basic scenario for this bug is as follows > I have two cores configured and BOTH have a customized "admin-extra.html", > however going to the admin pages uses the SAME admin-extra.html for all > cores. the one used is whichever core is browsed first.. This looks like > a caching bug where the cache is not taking into account the Core. > Basically my admin-extra.html has a link to the data importer script and a > link to reload the core (which has to have the core name explicitly in the > per-core admin-extra.html). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org