After a quick google, all the email attachment examples were crap, using antiquated versions of the library and even PHP v4 code!

Here’s my working example for taking a registration form with a file upload INPUT element that get’s directly attached to an email and sent.

	require_once('swift/lib/swift_required.php');
	$transport = Swift_SendmailTransport::newInstance('/usr/sbin/sendmail -n -t');
	$mailer = Swift_Mailer::newInstance($transport);

	$message = Swift_Message::newInstance('EMAIL SUBJECT')->setFrom('FROM EMAIL ADDRESS')->setTo('TO EMAIL ADDRESS');

	$body = "*** REGISTRATION FORM ***\n\n";
	$body .= 'First Name: ' . \WIC\Core::c()->qs('fname') . "\n";
	$body .= 'Last Name: ' . \WIC\Core::c()->qs('lname') . "\n";
	$body .= 'Address: ' . \WIC\Core::c()->qs('address') . "\n";
	$body .= 'Suburb: ' . \WIC\Core::c()->qs('suburb') . "\n";
	$body .= 'Postcode: ' . \WIC\Core::c()->qs('postcode') . "\n";
	$body .= 'Mobile: ' . \WIC\Core::c()->qs('mobile') . "\n";
	$body .= 'Home: ' . \WIC\Core::c()->qs('home') . "\n";
	$body .= 'Email: ' . \WIC\Core::c()->qs('email') . "\n";
	$body .= 'Keyboard Data Entry Operator: ' . \WIC\Core::c()->qs('data') . "\n";
	$body .= 'Clerical/Administrative: ' . \WIC\Core::c()->qs('administrative') . "\n";
	$body .= 'Additional Skills: ' . \WIC\Core::c()->qs('additional') . "\n";

	if (file_exists('/tmp/' . $_FILES['resume']['name'])) {
		unlink('/tmp/' . $_FILES['resume']['name']);
	}

	move_uploaded_file($_FILES['resume']['tmp_name'], '/tmp/' . $_FILES['resume']['name']);

	$message->setBody($body)->attach(Swift_Attachment::fromPath('/tmp/' . $_FILES['resume']['name']));
	$mailer->send($message);

This simply takes the form fields and dumps them to an email (not pretty I know), but then takes the uploaded file from /tmp/ and then attaches the file contents directly to the email and sends it :)

MSSQL has a restriction on by default which prevents using another SqlDataReader within a SqlDataReader without modification of the Connection String.

For example, say you want to get Table A, then for each record in Table A you want all records linked to Table A in Table B, a pretty normal request, one would typically get each record from SqlDataReader 1, then make a request to another SqlDataReader 2 and grab the child data there.

Doing this off the bat will fail unless you add the following parameter to your Connection String:

SqlConnection con = new SqlConnection("Data Source=[server];Initial Catalog=[dbName];User Id=[user];Password=[pass];MultipleActiveResultSets=true;");

Notice the MultipleActiveResultSets=true; value at the end? Enable this and you’ll be able to create secondary SqlDataReaders within a parent :)

I frequently have junior staff members who give me “clean” copies of new projects and upon the initial commit to SVN we find that the commit dies horribly for one reason or another.

Typically the new project will need to be scoured, folder by folder, to rid us of .svn folders from other repo’s which usually is a massive pain in the ass.

So here’s a command (to be used sparingly) “for NEW projects only“, that will wipe your entire project folder clean of all .svn (well, you can change the .svn to anything else such as “_notes”, etc.) in one fell swoop.

find . -name '.svn' | xargs rm -fr

Like I said, this is for new projects only as existing projects with VALID .svn folders will also be destroyed (FUBAR) by it.

Just recently we had a dev in my team restore a customers’ site from our backup repo which had images that our customer had since modified and so, our restore process overwrote those images the customer modified. Not a very happy customer ;)

In order to avoid this we simply needed to ignore the folder where our system uploads customer images to, since this folder truly is of no concern to our source management and typically binaries shouldn’t be committed unless they are to be versioned!

Enter SVN:IGNORE

I instructed the dev to add the svn:ignore property to the upload directory but the files still continued to be added to the repo.

svn propset svn:ignore uploads .

Explanation of this command

In order to understand WHAT the dev executed I had to explain what this command was doing. First, svn propset asks SVN to set a property for a working copy.

Second, the property being set is svn:ignore. The value of WHAT is being ignored is “uploads” (ie. we want to ignore the uploads directory).

Lastly, “where” does this directory exist? Well that’s what the period (.) at the end says (ie. it’s the uploads directory in the CURRENT path).

SVN ADD still adds the ignored directory

The dev then issues a standard add command and presto, the uploads directory is added, regardless of the svn:ignore. WTF?!

It turns out that the command being used to add included an asterisk (*) which, on the command line, expands all the entities within the directory, including the uploads directory which we wanted ignored.

Invalid SVN ADD command

svn add --force *

Correct SVN ADD command

svn add --force .

After executing the correct svn add command ALL the folders (and other entities) that need to ignored are correctly ignored :)