I've raised https://issues.apache.org/jira/browse/SOLR-13522 - feel free to
update the description as you like
Cheers
On Wed, 5 Jun 2019 at 21:48, Shawn Heisey wrote:
> On 6/5/2019 2:40 PM, Gus Heck wrote:
> > Experiences that force the user to think about the browser cache are
> > sub-par :).
On 6/5/2019 2:40 PM, Gus Heck wrote:
Experiences that force the user to think about the browser cache are
sub-par :). Anything that changes the URL will interrupt caching so just
adding a query parameter &_v=8.1.1 (or whatever) to every request would
probably do the trick, there's no need to
Experiences that force the user to think about the browser cache are
sub-par :). Anything that changes the URL will interrupt caching so just
adding a query parameter &_v=8.1.1 (or whatever) to every request would
probably do the trick, there's no need to mess with file names or file
locations IF
Could perhaps the UI have a version hard coded, and when the dashboard fetches
/admin/info/system it compares the version, and if newer than what is in the
JS, it will pop up a dialogue to ask user to reload and clear caches for the
site in browser?
Jan Høydahl
> 5. jun. 2019 kl. 20:47 skrev
On 6/5/2019 11:10 AM, Colvin Cowie wrote:
Upon opening the Admin UI I got some nasty behaviour, which appears to be a
result of some the Solr 6 Admin UI pages being cached.
In general I would consider this a bug, and a good reason to raise an
issue in Jira.
The admin UI should tell the
Hello,
I have just hit this and wondered if anyone has seen similar before since
the login page was added to the Admin UI?
I'm using Solr 6.6.6 currently, but I'm in the process of moving to 8.1.x.
That means I've been accessing the UI from 6 and had it cached. I switched
off 6 and run the 8.1.x
