On 11/25/2012 18:10, TJ Frazier wrote:
Jan,
FYI, I just deleted / blocked two spammers. The rate was only one per
hour, so we can handle that. The ID's were already created, so please
run that "delete recent accounts" script as soon as it's ready.
/tj/
Doing a little homework on the wiki logs, I see that we were being hit
by spam account creation as long ago as May (2012-05), but those
spammers never posted any spam. I suggest that you run your "delete
unused accounts" script with dates all the way to 2012-10-23. The
provision for "older than 6 months" can be for regular maintenance. The
"new account" log shows thousands of these spam accounts.
/tj/
On 11/25/2012 11:58, janI wrote:
Ok, got it (I just want to be sure, it is better asking than doing too
much
wrong), I will add the key change to my list, and do it as I go along.
jan I.
On 25 November 2012 17:47, Rob Weir <rabas...@gmail.com> wrote:
On Nov 25, 2012, at 11:34 AM, janI <j...@apache.org> wrote:
Where to insert is simple, but when I copied the ooo-site settings to
l10n,
I was told that was wrong...so what I need is the correct google key to
use.
If I recall the issue in that case was that we were moving that logic
into the site template so it did not need to be in the page itself.
With the wiki the logic is already there, but the key is wrong.
-Rob
Jan.
On 25 November 2012 17:24, C <smau...@gmail.com> wrote:
On Sun, Nov 25, 2012 at 5:12 PM, janI <j...@apache.org> wrote:
Not as urgent as the spam-related issues, but perhaps you could
include this bit of deferred maintenance as well:
https://issues.apache.org/ooo/show_bug.cgi?id=120301
I will do, if you can help me, how it should look (I remember when I
copied
it for l10n from ooo-site, you told me it was wrong).
It should be simple.... open the ooowikiskin.php file, search for the
existing UA-1087265-7. It should be right at the bottom of the file
just before the </body> tag (if I remember correctly). Replace the UA
code, and add the missing setDomainName line. Save and check by
reloading a Wiki page... look at the page source, and you should see
the corrected footer.
Clayton
