Nuke 'em or something. This is one of the most annoying "errors" I see. I'm
not a new user, but every time that flashes by I have to look to see what
happened and think "Oh, it's that thing again".

I added a comment to the JIRA that amounts to "nuke 'em 'til they glow and
shoot 'em in the dark". I don't think we should be taking pains to insure
that user-facing UI conveniences are available, the admin UI is a dev tool
after all.

FWIW,
Erick


On Tue, Dec 18, 2012 at 8:47 PM, Alexandre Rafalovitch
<arafa...@gmail.com>wrote:

> I would like to - gently - disagree that creating empty files is a
> workaround. The issue as I see it is that a beginner would not even get to
> the point of the 'create empty files', he/she would see the exception and
> get all worried.
>
> This is also problematic when writing an instruction, you tell someone to
> look for exception as a way to recognizing that they have gotten something
> wrong. At the same time, currently, you have to also tell them to ignore
> some other specific exceptions. Makes no sense and makes instructions much
> longer.
>
> Regards,
>    Alex
>
> Personal blog: http://blog.outerthoughts.com/
> LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
> - Time is the quality of nature that keeps events from happening all at
> once. Lately, it doesn't seem to be working.  (Anonymous  - via GTD book)
>
>
>
> On Wed, Dec 19, 2012 at 2:15 AM, Shawn Heisey <s...@elyograg.org> wrote:
>
> > On 12/18/2012 4:57 AM, Upayavira wrote:
> >
> >> The new UI includes them as ways to customise the interface merely
> >> because they were there in the old one.
> >>
> >> I'm questioning whether anyone actually creates/edits those files to
> >> customise their own admin UI, or whether that is a superfluous piece of
> >> functionality that causes more problems (exception angst for admins)
> >> than benefit.
> >>
> >
> > These extra html files are not mentioned anywhere in my config, but I got
> > the SEVERE errors anyway.  I just created zero byte files with those
> names
> > (touch command on Linux), and no more errors.  It's possible that I may
> end
> > up with a use for them later, and then it'll be a nice feature to have.
> >  I'd be OK with one line in the log at the WARN level at startup for each
> > file that it can't find.  I agree with the original poster about viewing
> > any exceptions (especially those logged at SEVERE) as a huge problem.
> >
> > I have added the workaround to the comments on SOLR-3972.
> >
> > Thanks,
> > Shawn
> >
> >
>

Reply via email to