Archive - Old Contents
Thanks for the props. Please keep an eye on the article and fix anything that needs to be fixed. I'm a *nix novice so I might put some bad info in there without knowing it. I'm doing my best. Thanks again. Crios 09:18, 14 November 2007 (PST)
Spam protection filter
I've encountered a problem with the so-called Spam Protection Filter. It is not allowing me to use overflow:auto on <pre> elements (which wouldn't create hidden DIVs anyway), so whenever anyone edits a page that already has one of these in it, they are forced to remove it. Not very helpful when you need that horizontal scrollbar. Any ideas? -- Scjessey 08:37, 13 December 2007 (PST)
- Unfortunately, I don't know offhand how to deal with that. IIRC, that particular Spam Protection Filter uses a regex to filter certain things, and I know that it is trying to prevent certain CSS that it' author felt might be contributing to hidden DIV usage - I just don't know the details (I can't even remember right now *which* regex was used). Myabe this is something worth contacting Aaron about, if it is critical? -- Rlparker 11:34, 13 December 2007 (PST)
- It's not a big deal. It is just that we often get articles with wide <pre> sections that need that horizontal scrollbar applied. They exist all over the wiki, but each time an edit is made that involves that particular code, the spam filter rejects it. The simplest solution I can think of would be to disable the application of the filter when edits are carried out by sysops and admins. Spammers ruin everything, don't they? -- Scjessey 12:02, 13 December 2007 (PST)
Yeah, it was a fun 4.5 hours. But I think it will be worth it.
David J (Davidu255)
Thanks for the response on my page regarding the reversion. I do appreciate the open attitude among the admin group! Please note also that I just cleaned up some similar "campaigning" content that I had previously added to "ProcMail". --Jdaskew 10:36, 26 May 2008 (PDT)
I was here for that article anyway, needed to apply that to my sites again (I guess it got overwritten). Had some extra time, figured I'd clean things up a little. I'll definitely do that more often now, thanks for the note! :)
Installed extension - TitleBlacklist
Sick of the "123 buy viagra" spam? ME TOO! So I installed an extension that'll let sysops specify a list of regular expressions in MediaWiki:Titleblacklist that won't be allowed as page titles or account names. So far I've just got two in there that block a pair of really persistent spammers... if you run into anything else that needs blocking, stick it in (or ask me). Andrew F 18:14, 1 July 2009 (UTC)
- Yeah I agree that anything we can do is needed. I will talk to Andrew when I can get at him and see if I can encourage him in this. - Rlparker 15:11, 1 February 2012 (PST)
A proposed technical edit concerning "bad_httpd_conf".
I have been in touch by DreamHost chat with technician Will, and he told me something that either did not sink in, or was not documented at the page (VIP: Very Important Page): http://wiki.dreamhost.com/Bad_httpd_conf
The reason I consider the article important, is because the believable claim is made that it is an Apache error invented by DreamHost, to help troubleshoot relatively straightforward technical issues.
Here is the relevant (edited) snip of our chat:
[10:02:03] Jason M: But, here's problem 2 if you have time: Put the correct IP, 188.8.131.52 into your web browser, and lets see if we can fix the result.
[10:04:19] Will: [edit note: error id: "bad_httpd_conf" comes back] Yes, this is because the domain is hosted on a shared environment - this IP represents hosts quite a few different domains so you'd need to add a unique IP address to the domain if you'd like to access it by IP address in this way.
[10:05:13] Jason M: But, if I can fix the IP with Yahoo!, that will clear up the error?
[10:06:04] Will: That's correct.
[10:07:21] Jason M: OK. I'll go back to Yahoo!. You may want to add the above info to your wiki page on bad_httpd_conf (or maybe it's already there and I missed it last night.)
...I'm not done yet fixing my client's problems with his Yahoo! (the domain registrar) login, so I cannot verify that Will's information is correct. However, I find it highly plausible, and am hopeful that when my client can log in to Yahoo! we can fix the IP for the domain, and the "bad_httpd_conf" error will go away, either when going to the web site by name, or even by IP (hopefully, I won't have to check on the IP once the domain name starts working).
Since I cannot verify that fixing the IP address with the domain registrar will fix the error, I do not feel qualified to edit the article here, "Bad httpd conf" myself. But if any of the Apache experts at DreamHost see the point Will's way, I think an edit should be added to the article explaining this technical limitation of that error message.
- An addendum to the above (two, actually);
- There is a related section in the article, Bad httpd conf at Bad_httpd_conf#If_you.27re_not_using_DreamHost.27s_DNS, but it does not go far enough to get me out out of Will's hair.
- However DH Malia just pointed me at DNS_-_Viewing_site_before_DNS_change#Here.27s_something_that_will_not_work, which does.
- I recommend that the full text of that section (or even a link to that section as "See also for more info") be integrated into article Bad httpd conf, because the Google results for the "bad_httpd_conf" error point me straight to the article Bad httpd conf here for info on the error (do not pass go, do not collect $200).
- Jasonm (talk) 16:22, 5 March 2014 (PST)