From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Trashed wiki pages
Date: Thu, 10 Oct 2019 10:00:25 +0100 [thread overview]
Message-ID: <DE3F673C-96D2-45B3-9E85-7CC30FDFE4CD@ipfire.org> (raw)
In-Reply-To: <55EF3F33-96F9-420A-8EF5-50AC4CA5900A@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Hi,
I saw this as well. I am not sure if it is intentional or not. Definitely not great.
I have added a restore feature to the wiki, so that going back to the latest correct version of the page is one click now. You will see a small icon on the revisions list and can do it as well.
I have rolled out more changes to the wiki right now and will send you guys an extra email.
Best,
-Michael
P.S. I have restored all pages that this user has messed up
> On 9 Oct 2019, at 18:01, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
> Also, the breadcrumbs are missing from many pages. I’m note sure if this was caused after the mess or something else.
>
> If this belongs in BZ, please let me know and I will add.
>
>
> Jon
>
>> From: Jon Murphy
>> Sent: Wednesday, October 9, 2019, 11:52 AM
>> To: Michael Tremer
>> Subject: Trashed wiki pages
>>
>>
>> Michael - there is a user named Ryan Paolello that made a mess of a few wiki pages. I am not sure if this is someone lacking experience (unlikely) or someone intentionally messing thing up.
>>
>>
>> https://wiki.ipfire.org/wiki was https://wiki.ipfire.org/wiki?revision=2019-07-30T15:46:52.669434
>>
>>
>> https://wiki.ipfire.org/configuration/login was https://wiki.ipfire.org/configuration/login?revision=2018-09-02T22:50:31
>>
>>
>>
>> Jon
>>
>>
>> <Screen Shot 2019-10-09 at 11.44.12 AM.png>
>
parent reply other threads:[~2019-10-10 9:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <55EF3F33-96F9-420A-8EF5-50AC4CA5900A@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DE3F673C-96D2-45B3-9E85-7CC30FDFE4CD@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox