Long long time ago I dissected the IDisposable interface (simple enough as it is) and made a "correct" implementation example essentially by commenting out MSDN code for better understanding what for and why you should do as it says:
class DisposableExample: IDisposable {
#region Absolute minimum of the code required for correct implementation of IDisposable
///
/// Field that will be set to true if attempt to destroy the object was already made.
///
private bool isDisposed = false;
///
Drupal will respond to any random subdomain like http://dfkasdf.giraffesdoexist.com/ with your normal site. Sometimes spammers and scammers use this feature for whatever reasons they might have and Google (or Yandex along with other search engines) will index these causing confusion, page duplicates and other nasty SEO-unfriendly effects.
This can be fixed by modifying robots.txt file on the fly to include Disallow directive as follows:
Security is all the hype with Google threatening to mark all sites not using SSL protocol as "insecure" or "unsecure" or whatever "non-secure" message it's going to show. Something like this:
So let's make it this site great secure again. Don't buy the certificate from your hoster just yet, if you are a small(-ish) website, you don't have to spend a penny. The things you'll need:
Your site is under attack. May be not right now, but several times a day. Password guessing, security vulnerabilities - that kind of stuff. In the error log it looks like this:
I hate voicemail. It's usually a total waste of time and money as the message itself tends to be "call me back at the number you already have" so I usually disable voicemail as a feature. This actually means that incoming calls are not forwarded to your voicemail. Seems like a problem solved only until I got a smartphone that has voicemail button right next to call button:
While experimenting with hosting options I tried an Amazon Cloud virtual machine among others to test hosting performance and ease of setting up Drupal on Windows compared to Linux shared hosting I use usually. Familiar Windows environment was pleasantly easy to configure, but failed to impress with server performance. After thorough disk space cleanup and uninstalling of extra applications I stumbled upon Event Log records of Brute Force attack attempts (Event Id 4625) that look similar to:
Internal links are important part of Search Engine Optimization. A common use of automatic internal links is "Similar articles" section suggesting pages with the same tags as the current one. For Drupal there's a module that does just that called Similar by Terms. Unfortunately the version for Drupal 7 is not in working state at the moment and I could not manage to utilize it.
If you get this message: :Sorry, there have been more than 5 failed login attempts for this account. It is temporarily blocked. Try again later or request a new password."
after some failed login attempts and want to recover access to your site then you can do this via SQL using phpMyAdmin for example.
