Summary

1. Make sure the computer sending the email has a Reverse PTR record. Your ISP has to do it, not your DNS provider or web host.
2. Sign your messages using DomainKeys Identified Mail. Requires DNS and code changes.
3. Set up a SenderID DNS record. Far less critical than the first two, but still nice to have.

Did it work?

1. Send a message to a GMail account–they provide excellent diagnostic headers. Look for Received-SPF and Authentication-Results.
2. Use the Port25 diagnostic service (check-auth@verifier.port25.com). You can ignore a DomainKeys check fail if the DKIM check passes.

<a href="#" onclick="aFunction();return false;">Link</a>

d’bug has a great writeup on why this works and the other doesn’t.

1) Add these lines into ~/.bash_profile

export PYTHONPATH="$HOME/lib/python2.3/site-packages"
export LD_LIBRARY_PATH="$HOME/lib"

2) Download the subversion source code

mkdir ~/src
cd ~/src
wget http://subversion.tigris.org/downloads/subversion-1.4.6.tar.gz
wget http://subversion.tigris.org/downloads/subversion-deps-1.4.6.tar.gz
tar -xzvf subversion-1.4.6.tar.gz
tar -xzvf subversion-deps-1.4.6.tar.gz
cd subversion-1.4.6

3) Compile dependencies

cd apr
./configure --enable-shared --prefix=$HOME
make && make install

cd ../apr-util
./configure --enable-shared --prefix=$HOME --with-expat=builtin --with-apr=$HOME --without-berlekey-db
make && make install

cd ../neon
EXTRA_CFLAGS="-L/usr/lib64 -fPIC"
CFLAGS="-L/usr/lib64 -fPIC"
./configure --prefix=/home/zzzzz/system --enable-shared --with-ssl
make && make install

Note: replace zzzzz with your user directory.

4) Compile subversion

cd ..
./configure --prefix=/home/zzzzz/system --with-expat=builtin --with-ssl --with-neon=/usr/lib64
make && make install

Note: replace zzzzz with your user directory.

5) Edit ~/.bash_profile to add ~/system/bin to your path

vim ~/.bash_profile

replace:

PATH=$PATH:$HOME/bin

with:

PATH=$PATH:$HOME/bin:$HOME/system/bin

6) Logout of your session and then log back in again. Subversion should now be working.

Normally this would be a filesystem permission error. You have to make sure the wp-content/plugins folder is owned by the user apache is running as. However, that didn’t change a thing.

Further googling revealed that I needed to add this constant in my wp-config.php file:

define('FS_METHOD', 'direct');

tbl = $('#primaryColumn table');
loading = $('#primaryColumn .loading');

tbl.fadeTo(300, 0.0, function() {
    loading.show();
        tbl.load('/contacts/{pagination:page}/' + page_num + '?ajax&search={pagination:search}', function() {
        loading.hide();
        tbl.stop().fadeTo(300, 1.0, function() {
            tbl.css('opacity', 'auto');  // removing the CSS opacity rule restores the ClearType anti-aliasing in IE
        });
    });
});

For some reason, the fadeIn(), fadeOut(), and fadeTo() effects do not work on <table> elements in IE, although they work great in Firefox and Opera. This also applies when using animate() to alter the CSS opacity rule (yeah, I tried them all).

As usual, the solution proved to be very easy: don’t animate the <table>, rather, wrap the <table> in a <div> and animate that. The only change required is the first line:

tbl = $('#primaryColumn div#table_div');

Bingo! Another three-hour bug-swatting episode reinforcing my hatred for Microsoft browsers of all versions just concluded.

This also goes for HTML form element names:

<form name="aform">
    <input type="text" name="name" />
</form>

Then accessing document.aform.name.value would throw an error since name is a reserved word.

Javascript Reserved Words

• abstract
• alert
• Anchor
• Area
• arguments
• Array
• assign
• blur
• boolean or Boolean
• break
• Button
• byte
• callee
• caller
• captureEvents
• case
• catch
• char
• Checkbox
• class
• clearInterval
• clearTimeout
• close
• closed
• comment
• confirm
• const
• constructor
• continue
• Date
• debugger
• default
• defaultStatus
• delete
• do
• document
• Document
• double
• Element
• else
• enum
• escape
• eval
• export
• extends
• false
• FileUpload
• final
• finally
• find
• float
• focus
• for
• Form
• Frame
• frames
• function
• Function
• getClass
• goto
• Hidden
• history or History
• home
• if
• Image
• implements
• import
• in
• Infinity
• innerHeight
• innerWidth
• instanceOf
• int
• interface
• isFinite
• isNan
• java
• JavaArray
• JavaClass
• JavaObject
• JavaPackage
• label
• length
• Link
• location or Location
• locationbar
• long
• Math
• menubar
• MimeType
• moveBy
• moveTo
• name
• NaN
• native
• navigate
• navigator or Navigator
• netscape
• new
• null
• Number
• Object
• onBlur
• onError
• onFocus
• onLoad
• onUnload
• open
• opener
• Option
• outerHeight
• outerWidth
• package
• Packages
• pageXoffset
• pageYoffset
• parent
• parseFloat
• parseInt
• Password
• personalbar
• Plugin
• print
• private
• prompt
• protected
• prototype
• public
• Radio
• ref
• RegExp
• releaseEvents
• Reset
• resizeBy
• resizeTo
• return
• routeEvent
• scroll
• scrollbars
• scrollBy
• scrollTo
• Select
• self
• setInterval
• setTimeout
• short
• static
• status
• statusbar
• stop
• String
• Submit
• sun
• super
• switch
• synchronized
• taint
• Text
• Textarea
• this
• throw
• throws
• toolbar
• top
• toString
• transient
• true
• try
• typeof
• unescape
• untaint
• unwatch
• valueOf
• var
• void
• watch
• while
• window
• Window
• with

Faster replication heartbeat (old default is 3600 seconds = 1 hour):

slave_net_timeout 10

Disable DNS hostname lookups:

skip-name-resolve

Sane connection timeout (may need to be raised if your network is flaky):

connect_timeout 5

Disable host blacklisting after x number of failed connections:

max_connect_errors 1844674407370954751

Download nameparse.php

nameparse.php can recognize names in “[title]first[middles]last[,][suffix]” and “last,first[middles][,][suffix]” forms, which, when you think about it, cover most if not all well-formed name input formats. nameparse.php handles last names of arbitrary complexity, such as “bin Laden”, “van der Vort”, and “Garcia y Vega”, as well as middle names of arbitrary size and complexity, differentiating between most last names and the first or middle names or initials preceding them.

An example of names correctly parse by nameparse.php:

• Doe, John. A. Kenneth III
• Velasquez y Garcia, Dr. Juan, Jr.
• Dr. Juan Q. Xavier de la Vega, Jr.

To use, simple include() or require() nameparse.php and call parse_name($string) on any name. parse_name() returns an associative array of all name segments found of “title”,”first”,”middle”,”last”, and “suffix”. Do note that no spelling, capitalization, or punctuation of titles, prefixes, or suffixes is normalized. That is, every token remains as entered: nameparse.php is a semantic parser only. If you want orthographic or other normalization, you’ll have to postprocess the output. However, since the name is now semantically parsed, such postprocessing is (for applications which require it) simple.

print_r(parse_name('Velasquez y Garcia, Dr. Juan Q. Xavier III'));

yields . . .

Array
(
    [title] => Dr.
    [first] => Juan
    [middle] => Q. Xavier
    [suffix] => III
    [last] => Velasquez y Garcia
)

function gmp_not($n) {

	# convert to binary string
	$n = gmp_strval($n, 2);

	# invert each bit, one at a time
	for($i = 0; $i < strlen($n); $i++) {
		$n[$i] = ~$n[$i];
	}

	# convert back to decimal
	return gmp_strval(gmp_init($n, 2), 10);
}

return gmp_strval(gmp_init($n, 2), 10);

This will convert a large base 2 (binary) number to base 10 (decimal).

Hi Jonathon,

I really like some of your solutions to making things simpler when using CodeIgniter. On the subject, I was wondering if you had a preference for a simple way to include headers and footers in your views. I know you can either do views within views, but that just doesn’t feel right to me. Although the advantage is only having to use one line to call your views within a controller. The method of building your views within an action by calling each view seperately also doesn’t interest me, because I’m trying to adhere to the DRY principle. I’ve also seen a solution where you create your own MY_controller and build the view that way then inherit from all your other controllers.

Do you have a recommended way to include your common views that’s simple and doesn’t require you add multiple lines of code to each controller action? I’m trying to keep my view calling to one line within each action of the controller.

Thanks,

Lee

My preference on that is simply calling views within views. It just makes sense to do it that way. If there is data that must be passed to the header and footer globally, then I would extend the Loader class with a global data function like this:

class MY_Loader extends CI_Loader {

	function MY_Loader() {
		parent::CI_Loader();
	}

	function global_view_data($key, $val) {
		# normalize the data array
		$data = (is_array($key))? $key : array($key => $val);

		# merge into the view data array
		$this->_ci_cached_vars = array_merge($this->_ci_cached_vars, $data);
	}

}

Copy that to a file called MY_Loader.php and save it in your libraries folder as described in the user guide. Once that is done you can load data which will be passed to all views globally:

$this->load->global_view_data($stuff);

Note: I have found that including views within views is aggravating without a helper function, so I wrote the Modularity plugin to help with that.

@reboot /path/to/my/program

The command will be executed on every (re)boot. Crontab can be modified by running:

sudo crontab -e

1. If it worked 10, 20, 30 years ago, it is worth considering.
2. If a crisis makes you come alive, you have your priorities wrong.
3. If you are working on urgent system problems, it’s not a boring architecture.
4. You should be working on exciting new things that serve your customers and are otherwise unimportant.