www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2270) wiki.apache.org/solr removes data on saves
Date Thu, 15 Oct 2009 19:19:31 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766186#action_12766186

Hoss Man commented on INFRA-2270:

>> <joes4> page restored

...i assume that comment refers to the SolrJetty page yonik noticed was missing.  I also see
some commit emails generated by Joe from http://wiki.apache.org/solr/TestCreatePage suggesting
that creating new pages now works, and trivial updates should be sending email (although i
can't confirm that: my trivial update of that test page - r27 - didn't generate an email to

I've also tested that reverting seems to work again.

what about the initial bug report of pages getting corrupted (large sections being deleted)
on save.  Has the cause been fixed (or at least identified so we can try to work around it)

> wiki.apache.org/solr removes data on saves
> ------------------------------------------
>                 Key: INFRA-2270
>                 URL: https://issues.apache.org/jira/browse/INFRA-2270
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: MoinMoin
>            Reporter: Noble Paul
>            Priority: Blocker
> After the recent update of http://wiki.apache.org/solr/ wiki When I save data it removes
some extra stuff too (not always) . A case in point is the edit on the page http://wiki.apache.org/solr/DataImportHandler
. after rev=212. It removed some extra content too.
> What makes this worse is the revert functionality does not work it gives a 500 error
> I am keeping this as a blocker because it is removing valuable documentation from the
site and there is no way to restore it. We are going to release Solr soon and we cannot have
a release with this broken documentation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message