A collection of free repeatable SVG background patterns

If you need a repeatable SVG background pattern to spruce up your site’s background or callout a box, check out Hero Patterns.

Hero Patterns provides over 80 free SVG background patterns and the CSS code you need to add them to your site. Additionally, they have provided a color picker for the foreground and background so that you can customize each pattern to fit your needs.

This post’s background contains my favorite background pattern: Topography

Convert your raw SQL statements to a Laravel Query Builder query

If you have some legacy SQL or some raw test SQL code that you want converted into a Laravel’s Query Builder statement, check out Orator.

Orator can convert raw SQL into a Laravel Query Builder statement.

For example, Orator will convert this SQL query…

SELECT * FROM users;

… into this Query Builder statement:


I decided to test Orator on a much more complex query generated by WooCommerce, a WordPress ecommerce plugin.

Here’s the query I plugged into Orator. It contains a subquery and an OR statement.

FROM posts 
WHERE 1=1 
	posts.ID NOT IN 
		SELECT object_id 
		FROM term_relationships 
		WHERE term_taxonomy_id IN (7) 
AND posts.post_type = 'product'
	posts.post_status = 'publish'
	posts.post_status = 'private'
ORDER BY posts.menu_order ASC, posts.post_title ASC
LIMIT 0, 10

Orator handled the subquery and OR statement perfectly:

	->where(1, `=`, 1)
	->where(DB::raw(`( posts.ID NOT IN ( SELECT object_id FROM term_relationships WHERE term_taxonomy_id IN (7) ) )` ))
	->where(`posts.post_type`, `=`, `product`)
	->where(DB::raw(`( posts.post_status = 'publish' OR posts.post_status = 'private' )` ))
	->orderBy(`posts.menu_order`, `ASC`)
	->orderBy(`posts.post_title`, `ASC`)

The last test I performed contained 2 INNER JOINs. Here’s the query I started with:

SELECT t.*, tt.*, tr.object_id
FROM terms AS t 
	INNER JOIN term_taxonomy AS tt
		ON t.term_id = tt.term_id
	INNER JOIN term_relationships AS tr
		ON tr.term_taxonomy_id = tt.term_taxonomy_id
WHERE tt.taxonomy IN ('category', 'post_tag', 'post_format')
AND tr.object_id IN (1)

And Orator returned the following:

	->from(`terms as t`)
	->join(`term_taxonomy as tt`, function($join) {
		$join->on(`t.term_id`, `=`, `tt.term_id`);
	->join(`term_relationships as tr`, function($join) {
		$join->on(`tr.term_taxonomy_id`, `=`, `tt.term_taxonomy_id`);
	->whereIn(`tt.taxonomy`, `('category', 'post_tag', 'post_format')`)
	->whereIn(`tr.object_id`, `(1)`)
	->orderBy(`t.name`, `ASC`)

Not only does Orator save you a ton of time converting test or raw SQL into Laravel specific queries, it’s also a great learning tool if you are more comfortable with SQL than you are with Laravel’s Query Builder.

Properly display line breaks from a <textarea> using Blade

If you have a <textarea name="content"> field in your form and you use {{ $post->content }} in your Blade template to display the $post->content field, you’ll notice that none of the line breaks are retained when the field is rendered on the page.

For example, text entered into a <textarea> like this:

The plants and flowers
I raised about my hut
I now surrender
To the will
Of the wind

Will be displayed on your page like this:

The plants and flowersI raised about my hutI now surrenderTo the willOf the wind

That does not do the Ryokan poem justice.

To fix our line break issue, replace {{ $post->content }} with {!! nl2br(e($post->content)) !!}

Let’s break that down working from the most inner function out to the wrapping Blade statements.

We first wrap $post->content with the escape function e(). The Laravel e() function runs PHP’s htmlspecialchars function with the double_encode option set to false. Laravel Documentation

Next we have nl2br() which inserts HTML line breaks (ie. <br> tags) before all newlines in a string. PHP Documentation

Lastly, we change our Blade statement from {{ ... }} to {!! ... !!} which disables the escaping of data between the curly braces. But we’ve already escaped the data using the e() function.

Important – If you choose to prevent escaping by using the {!! ... !!} statement, be sure to escape your data before rendering it on the page… or else.

Now your line breaks are retained.

Call the_content filter once and only once

If you hook into the the_content filter to modify a blog post’s content, you may notice that the hook gets executed more than one time. This can cause your page load time to increase. The code below is an example of how to ensure your the_content filter function is called once and only once during the page load of a single WordPress Post|Page|Product|etc…