Hi Guys,

Just giving this a little follow-up: the issue hasn't been solved, and
although we managed to fix it on the server by rolling back the extractors,
it now happens seemingly random (location/contenttype) on my local machine,
which kind of worries me...
Any information on when Slide starts throwing these 406's? Is it some kind
of index corruption? If so, is there a force-rebuild for the indexes?


On Tue, Feb 26, 2008 at 5:04 PM, Rogier Peters <[EMAIL PROTECTED]>
wrote:

> Right now i'm also getting 406 on another content type, but only on my
> local machine. It goes away if I disable the instructions inside the
> nl.hippo.slide.extractor.HippoSimpleXmlExtractor i.e.
> <extractor...
>   <configuration
>     <!-- instruction
> but it returns if I enable _any one_ of them.
>
>
>
> > I'm sending you the file, the extractors.xml and some stacktraces from
> > > the
> > > > logs. Please have a look
> > > So you are trying to create a new sitemenu.xml?
> >
> > yes
> >
> >
>
>
> > Which extractor gives
> > > the error?
> >
> > I don't know yet -- still investigating
> >
> > >
>
> >
> > >
> > > Regards,
> > > Bart
> > >
> > > >
> > > > Rogier
> > > >
> > > > Att:
> > > > sitemenu.xml -- the template (from types) for file that cannot be
> > > created
> > > > extractors.xml -- you know...
> > > > log.txt -- the errors
> > > >
> > > >
> > > >
> > > ------------------------------------------------------------------------
> > > >
> > > > ********************************************
> > > > Hippocms-dev: Hippo CMS development public mailinglist
> > >
> > >
> > > --
> > >
> > > Hippo
> > > Oosteinde 11
> > > 1017WT Amsterdam
> > > The Netherlands
> > > Tel  +31 (0)20 5224466
> > > -------------------------------------------------------------
> > > [EMAIL PROTECTED] / http://www.hippo.nl
> > > --------------------------------------------------------------
> > > ********************************************
> > > Hippocms-dev: Hippo CMS development public mailinglist
> > >
> >
> >
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to