“LDAP-module cannot connect to any servers: Server: ‘ldap://domaincontroller1.beyondlogical.net/’, Connection: ‘Resource id #2′, Bind result: ””

In my case, the user account Moodle uses to bind to AD had been moved and simply needed updating, which is simple enough to edit through the database once you know where to look. Here is the SQL query to return the value to be edited:

SELECT value FROM moodle.config_plugins WHERE plugin = 'auth/ldap' AND name = 'bind_dn'

Check the returned value against your AD tree and figure out what needs to change. It should look something like this:

CN=Bind AD Query,OU=IT Department,OU=Users,OU=Beyond Logical Enterprises,DC=beyondlogical,DC=net

Compare this with AD and figure out what needs to change. If you aren’t familiar with AD, this string specifies an account (CN means “Common Name”, OU means “Organizational Unit”, DC means “Domain Controller”) and, if you read it from right to left, provides a path down the AD tree to specify how to locate that account.

Here is the SQL to update this value, make sure you replace the value I provide with whatever is appropriate for your AD:

UPDATE moodle.config_plugins SET value = 'CN=Bind AD Query,OU=IT Department,OU=Users,OU=Beyond Logical Enterprises,DC=beyondlogical,DC=net' WHERE plugin = 'auth/ldap' AND name = 'bind_dn'

You may also see this error if the password on the account has changed. The current password is stored in this value:

SELECT value FROM moodle.config_plugins WHERE plugin = 'auth/ldap' AND name = 'bind_pw'

and can be updated using this query:

UPDATE moodle.config_plugins SET value = 'your_password_goes_here' WHERE plugin = 'auth/ldap' AND name = 'bind_pw'

It’s that simple… usually. For some reason some program output going to STDOUT doesn’t end up there. There is a simple fix, that being to pipe it through cat first:

echo “This goes to the clipboard” | cat > /dev/clipboard

For some reason, inaccurate info ended up in your vdi file. VB is now more strict, and this inaccurate information just needs to be expunged to prevent VB from panicing. See this ticket for details:

http://www.virtualbox.org/ticket/7289

The short of it is: You download the tool for your host platform:

http://www.virtualbox.org/download/VBoxFixHdd/

“Identify the affected images. You can either use the VirtualBox GUI and check which base images are inaccessible, but shouldn’t be. The same can be done with “VBoxManage list hdds”, in this case make sure you only look at images which say “Parent UUID: base”.
Run the repair tool:
VBoxFixHdd –filename /path/to/image.vdi –zeroparentuuid
Repeat for all affected images.”

Worked like a charm.

Click your Windows “Start” button and select “Run”, or hold down the “Windows Key” and press “R”.
Enter “regedit” in the “Open:” dialogue box and press OK.
Press “Ctrl” and “F” to open the Find dialogue.
Enter “Blizzard Entertainment”. It should display a folder on the left entitled “Blizzard Entertainment”. Expand this folder by clicking the “+” to the left of it. You should see a “Downloader” folder. Expand this too. There should be a key with some random string of alphanumerics. Click on that.
In the right pane you should see a key that titled “Path”. Right click on that and click “Modify.”
Change the “Value data” to set the location for the download folder and press “OK”. Close RegEdit.
Enjoy!

Standard disclaimer: when mucking about in your registry, be careful, as you can bork Windows.

Does the directionality of a person’s primary writing system (left-to-right, top-to-bottom for English) affect the way in which they take in other compositions, such as a photo or painting, creating a “perceptual directionality”? If so, should visual composition be informed by knowledge of the target audience’s perception directionality? After a brief search I came up with this paper, which seems to indicate that I’m not too far off the mark.

Writing Direction Influences Spatial Cognition

Now that doesn’t exactly answer the original question, although it does inform the decision of how to compose the shot.

In that case, mb_strlen() becomes strlen(). mb_strlen() is strlen() with support for different charsets, which may use different byte lengths for a single character. By default, it will use your internal encoding. However, it supports an explicit character encoding as its second parameter. Knowing that latin1 uses a single byte, mb_strlen($string,’ISO-8859-1′) will do what we want and count the bytes in $string regardless of your current internal encoding or the string’s apparent encoding.
Let’s wrap this in a function for clarity, and in case we need to change our counting method because of a change in PHP or some such helpfullness:

function bytelength ($string) {
// Returns: (int) number of bytes in string
// Use latin1 as a alias for "1 byte"
return mb_strlen($string,'ISO-8859-1');
}