Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi Jay,

the spam / captcha extension is still on my to-do-list (see also https://redmine.documentfoundation.org/issues/172 ) and I think I should give it a bit more priority as this seems to be a bigger issue than I thought. I hadn't any problems ages ago (when I was a normal user and not an admin).

I will try if I can find any configurations which improves the situation as described in your email. Thanks for the suggestion

Regards,

Dennis Roczek

Am 04.06.2014 14:56, schrieb Jay Philips:
Hi Dennis,

Hopefully that would be an improvement, but if i already checked the
'This is a minor edit' checkbox, maybe that should have auto filled the
summary. It would be alot better if the captcha was there on the initial
edit page as i'm assuming it already knows that its going to be put on
the second page. And why is the captcha there on every single edit, it
gets ridiculous. If i give the captcha once, some cookie should be set
for maybe that session or maybe even an hour, so i dont have to deal
with it now that it knows i'm a human. :) Ultimately, there needs to be
some type of privileges set for users, so they dont have to deal with
this at all. I'm only guess about the privileges part as i dont know how
the wiki backend functions. :)

Regards,
Jay Philips

On 06/04/2014 12:56 PM, Dennis Roczek wrote:
Hi *,
OK, at least a bit improvement: I have highlight the message about the
missing edit summary with a red border and a gray colored background.

Hope this message isn't overseen then (I missed it a few times in the
beginning, too).


Regards,

Dennis Roczek

Am 03.06.2014 17:15, schrieb Jay Philips:
Hi Alex,

Yep i've been having similar problems with the wiki, where in order to
make a minor change, i have to click the 'save page' button 3 times.
First time editing the page, second time dealing with captcha, third
time dealing with 'Reminder: You have not provided an edit summary. If
you click "Save page" again, your edit will be saved without one.'. It
is quite a pain.

Regards,
Jay Philips

On 06/03/2014 05:34 PM, Alexander Thurgood wrote:
Le 03/06/2014 15:28, Dennis Roczek a écrit :

Hi Dennis,

Hi,
no that is not normal. Can you give me your user name (I want to check
if you run in any existing abuse/spam filter) and maybe if you still
know a) which page you wanted to edit (I remeber that there are
multiple QA member pages) and b) what you wanted to change...
I finally managed to get it to do what I wanted, but phew, arduous
or what !
My handle is iplaw67, I created a new account yesterday, as the wiki
couldn't seem to remember any of the older ones that I had, even when I
asked it to reset my password, it came back as "user unknown", hence
the
new account, linked to a different e-mail address.

I have experienced the problems with my own Profile page (the one that
you get when you click on your alias), and also with :

https://wiki.documentfoundation.org/QA_Team


As I mention above, I got there in the end, but I'm afraid I won't be
going anywhere near the wiki again in future if that is how it is
supposed to function.

Alex







--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.