On an ARM macOS I ran tail -f /opt/homebrew/var/log/nginx/error.log and could see the following error.

2023/08/11 09:53:43 [crit] 29890#0: *9 open() "/opt/homebrew/var/run/nginx/client_body_temp/0000000002" failed (13: Permission denied), client: 127.0.0.1, server: local.test, request: "POST /livewire/upload-file?expires=1691769523&signature=61f7f20ef5a9047cec174fc9fa5dbb2b729b0f91394f75b23d41c0f358318463 HTTP/1.1", host: "local.test", referrer: "http://local.test/admin/inspections/5/submit"

🤨 WTF!

I resolved the issue by by running sudo chown -R $USER:_developer client_body_temp/

I am unclear why nobody was assigned to the folders, I also think that maybe my work laptop has the _developer group which I don’t think is standard.

You won’t need to restart Nginx but retry the file upload.

Hopefully you found this helpful!

The post How to fix Nginx client_body_temp Permission denied on macOS appeared first on Adam Patterson.

To fix this error, you can try increasing the client_max_body_size setting in your Nginx configuration. Here’s how:

1) Open your Nginx configuration file. This is typically located at /etc/nginx/nginx.conf on a Linux server.

2) Find the http block in the configuration file and add the following line:

http {
    ...
    client_max_body_size [size];
}

Replace [size] with the maximum size of the request body you want to allow, in bytes. For example, to set the maximum size to 10 megabytes, you would use client_max_body_size 10m;.

3) Save the configuration file, test and restart Nginx using the following command:

sudo nginx -t
# nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
# nginx: configuration file /etc/nginx/nginx.conf test is successful

sudo systemctl restart nginx

After increasing the client_max_body_size setting and restarting Nginx, you should be able to upload larger images to your WordPress website or blog without encountering the “server cannot process image” error.

However, if you are still experiencing this error after updating the client_max_body_size setting, there may be other factors at play. Here are a few additional things you can try:

• Update the upload_max_filesize setting in PHP. This setting specifies the maximum size of a file that can be uploaded to your server. If you are trying to upload an image that is larger than this size, you may receive the “server cannot process image” error. To fix this, you can increase the upload_max_filesize setting in your PHP configuration. This is typically located at /etc/php/php.ini or /etc/php/8.2/fpm/php.ini on a Linux server. Find the upload_max_filesize setting and increase it to a larger value, then save the file and restart your web server.
• Reduce the size of the image you’re trying to upload. The suggested maximum size for images in WordPress is 2560 pixels. If your image is larger than this, you’ll need to resize it before uploading. You can use a free image editing tool like GIMP or Adobe Photoshop to resize your image.
• Check your server’s resource usage. If the server is busy or has a high load, it may not have enough resources available to process your image. You can check your server’s resource usage by contacting your web host or using a tool like top. If the server’s resources are maxed out, you may need to upgrade to a more powerful hosting plan or consider moving to a different web host.

The post Fixing the ‘server busy or not enough resources’ error in WordPress appeared first on Adam Patterson.

Combined with PHP having a quicker release cycle PHP 8, 8.1, and 8.2 are on their way.

I have to work with a couple of versions regularly in the CLI, and the best way I found to do this was to create an alias.

Let’s assume that you installed your versions of PHP using brew, or already know where your version of PHP is.

Add the following to your bash profile.

alias php7='/usr/local/opt/php@7.4/bin/php'
alias php8='/usr/local/opt/php@8.0/bin/php'

If you want you can install PHP 8.1 and 8.2 as well with brew install php@8.X and add another alias.

This will allow you to run php8 composer, you can do a quick test by creating an index.php file and adding phpinfo() to it.

php7 index.php | grep "PHP Version"
php8 index.php | grep "PHP Version"

If you have an M1 mac, your system paths will be different. You can replace:

/usr/local/opt/

with

/System/Volumes/Data/opt/homebrew/opt

If you were to run php -v and see v7.4 then you can now run php8 composer install in most cases, this has worked perfectly, but if you need something a bit more permanent it’s still best to change your system environment.

Alternatively, if you want to change your version of PHP in the command line more permanently you can add this function to your .bash_profile

function phpv() {
    brew unlink php
    brew link --overwrite --force "php@$1"
    php -v
}

And then run with phpv 8.2

I can’t take credit for the above shell script, but I also can’t find the original post that I discovered it on.

The post How to execute multiple versions of PHP on macOS using the CLI appeared first on Adam Patterson.

Previously I used OpenSSL locally on my Mac, and it was… OK, but it was sort of complicated and involved a lot of copy and paste.

To get started let’s start off by installing mkCert using HomeBrew. Create a new folder in your Sites directory called SSL, and navigate your way there in the terminal.

brew install mkcert
brew install nss # if you use Firefox

mkcert -install

mkcert site.local '*.site.local'

That was it! Your certificate is is ready to go, but now what?

Configure MAMP

Open /Applications/MAMP/conf/apache/httpd.conf and search for # Virtual hosts.

Add a line under httpd-vhosts.conf called httpd-secure-vhosts.conf.

Open /Applications/MAMP/conf/apache/httpd-secure-vhosts.conf and add the following, changing the names and paths to reflect your needs.

NameVirtualHost *:443

<VirtualHost *:443>
	ServerName site.local
    ServerAlias *.site.local
    ServerAlias dev.smi
    ServerAlias *.dev.smi

	DocumentRoot "/Users/{username}}/Sites/web_path/"

    <IfModule xsendfile_module>
        XSendFilePath "/Users/{username}}/Sites/web_path/"
    </IfModule>

    SSLEngine on

    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

    ErrorLog "/Applications/MAMP/logs/apache_ssl_error.log"
    TransferLog "/Applications/MAMP/logs/apache_ssl_access.log"
    CustomLog "/Applications/MAMP/logs/apache_ssl_request.log" "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

    SSLCertificateFile "/Users/{username}}/Sites/ssl/site.local+1.pem"
    SSLCertificateKeyFile "/Users/{username}}/Sites/ssl/site.local+1-key.pem"

    SSLSessionTickets on

    <FilesMatch "\.(cgi|shtml|phtml|php)$">
        SSLOptions +StdEnvVars
    </FilesMatch>

    <Directory "/Applications/MAMP/Library/cgi-bin">
        SSLOptions +StdEnvVars
    </Directory>

    BrowserMatch ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

	<Directory "/Users/{username}}/Sites/web_path/">
		Options Includes FollowSymLinks ExecCGI
		AllowOverride All
		Order allow,deny
        Allow from all

	</Directory>

</VirtualHost>

Open /Applications/MAMP/conf/apache/httpd.conf again and look for Include /Applications/MAMP/conf/apache/extra/httpd-ssl.conf and uncomment that line.

I personally remove the VirtualHost from this file and leave it the httpd-secure-vhosts.conf file that we previously created.

By creating a wild card certificate you can simply add every new local site under that subdomain if you so choose.

The post Super simple local wildcard SSL! appeared first on Adam Patterson.

In my free time I like to make stuff and post it on YouTube, and my “other” blog called Hey I’m A Maker. A lot of content creators will use affiliate links in order to make some extra income from their content. There are plenty of services out there to help you do this.

At the moment I have an Amazon Affiliate store that I tossed a few interesting items into. The issue is that I live in Canada and many of my viewers also live in Canada. The Amazon stores are not transferable between .com and .ca.

I began looking into ways of routing the link based on Geography. I discovered a few paid services for $10-20 a month which was far more than I wanted to spend.

After some exploring, I learned that Cloudflare is able to add Geolocation headers to their responses. If you are interested you can read more on how to set that up here.

Modify your WordPress theme

Once I had enabled the IP Geolocation feature I was able to see my region as CA using the following code as a test.

echo $_SERVER["HTTP_CF_IPCOUNTRY"];

The goal I want to achieve here is to modify a nav item based on our geographical location. In my case, Canadian visitors should see my Canadian affiliate store.

In the following code snippets, I will assume that your menu location is called primary and that the link you want to modify was added as a custom link.

To get this started I want to modify the WordPress menu items before the HTML has been created. To do this I will use the filter wp_nav_menu_objects.

Create a function called update_shop_link which will accept two parameters, $items and $args.

By now you should have something that looks like this located in your functions.php.

add_filter( 'wp_nav_menu_objects', 'update_shop_link', 10, 2 );
function update_shop_link( $items, $args ) {
    // Code here
}

Next up, we want to only modify a link that is in our primary menu and to make sure that HTTP_CF_IPCOUNTRY is set.

Once those are true we can set a variable $region, and then loop through the $items looking for a link that is of the type custom, and whose title is equal to Shop.

if ( $args->theme_location == 'primary' && array_key_exists( 'HTTP_CF_IPCOUNTRY', $_SERVER ) ) {
    $region = $_SERVER["HTTP_CF_IPCOUNTRY"];

    foreach ( $items as $key => $item ) {
        if ( $region === 'CA' && $item->type === 'custom' && $item->title === 'Shop' ) {
            // Code here
        }
    }
}

Now we have found out shop link you can modify the URL by overwriting it.

$item->url = 'https://www.amazon.ca/shop/adampatterson';

Wrapping it up

That’s all there is to it, now let’s roll it all together.

add_filter( 'wp_nav_menu_objects', 'update_shop_link', 10, 2 );
function update_shop_link( $items, $args ) {
	if ( $args->theme_location == 'primary' && array_key_exists( 'HTTP_CF_IPCOUNTRY', $_SERVER ) ) {
		$region = $_SERVER["HTTP_CF_IPCOUNTRY"];

		foreach ( $items as $key => $item ) {
			if ( $region === 'CA' && $item->type === 'custom' && $item->title === 'Shop' ) {
				$item->url = 'https://www.amazon.ca/shop/adampatterson';
			}
		}
	}

	return $items;
}

This method was specific to WordPress, but as long as you are using a server-side language you can intercept the region and do whatever you like.

You could even create a page like domain.com/shop that would automatically redirect to your Amazon store. If you really wanted that URL could redirect to a tiny URL that would allow you to collect some basic analytics.

If you enjoyed this then I would love it if you subscribed to my YouTube channel or had a look at my site Hey I’m A Maker.

The post Customize WordPress menu items based on Geographic Location appeared first on Adam Patterson.

add_image_size('square', 150, 150, true);

Now any time an new image is uploaded WordPress will generate a file something like image-150×150.jpg.

If you want to be able to insert these images in your posts then you will need to register the size with the Media moda.

add_filter('image_size_names_choose', 'add_image_sizes_editor');

function add_image_sizes_editor($sizes)
{
    return array_merge($sizes, [
        'square'   => __('Square', 'axe'),
    ]);
}

Now when you create a post and want to add an image your custom sizes will be available to you.

The post How to add and Use WordPress Custom Image sizes appeared first on Adam Patterson.

In both scenarios, you might be maintaining a couple of feature branches and would want to be able to check your work in your staging environment, at the very least not impact your team.

Luckily Composer makes this super simple.

Take the branch name and prepend dev- to it as in the example below.

{
  "require": {
    "app/core": "dev-branch-name"
  },
  "repositories": [
    {
      "type": "package",
      "package": {
        "name": "app/core",
        "version": "dev-branch-name",
        "source": {
          "url": "git@github.com:repo/app-core.git",
          "type": "git",
          "reference": "branch-name"
        }
      }
    }
  ]
}

Maybe you want to check a specific commit, then try using a commit hash instead dev-master#99226c9

Thats it, and I hope this helps. I know it has come in handy when deploying a docker container to a staging server.

The post Working with branches in Composer appeared first on Adam Patterson.

Geolocation is a method used to find the location of your internet device on earth. Imagine you lost your cell phone, and use the find my phone option. The location of your phone will be your device’s last known location.

How does Geolocation work?

There are two main types of data collection.

The first is Device-Based

You have probably visited a website that prompted you for permission to access your location. This request has to be made from a secure site using SSL and if you are on a mobile device will require location services to be enabled.

The second is Server-Based.

Every request made to a server will include your device IP, that IP is typically stored in a Database where a physical location is matched. This isn’t always accurate as IP addresses are released and renewed frequently. Depending on your network, or your companies network these results can be very different.

Why would I want to use Geolocation?

• Any time you have multiple locations like a food chain
• E-commerce site where you have products across the country
• You operate in multiple countries and want to redirect the customer to the proper website
• Present visitors with relevant content

Geolocation is a quick and simple way to present information that is relevant to the customer and to make improvements to their websites.

How do I use Geolocation then?

Login to your Google Cloud Account

Then Enable the API by heading to the API’s Library. Next, search for and enable Geolocation API.

NOTE: There could be a cost associated with this, Make sure to read and understand your Google cloud account and how their billing works.

Under your API & Services, click on Credentials, then Add a new API restriction and check Geolocation API.

If you don’t add the restriction you will likely see the following error.

{
   "error_message" : "This API project is not authorized to use this API. Please ensure that this API is activated in the APIs Console: Learn more: https://code.google.com/apis/console",
   "results" : [],
   "status" : "REQUEST_DENIED"
}

Using curl, or a tool like Postman, make a POST request to https://www.googleapis.com/geolocation/v1/geolocate?key={{key}}

That’s it, you should see something resembling the following results

{
  "location": {
    "lat": 53.595340799999995,
    "lng": -113.5706112
  },
  "accuracy": 2435
}

For more on Google’s Geolocation services check out their guide.

If you don’t happen to have an API key then this guide should get you on your way.

The post Simple Googe Geolocation appeared first on Adam Patterson.

Normally in the WordPress loop you would set a variable outside of the while statement and increment int. This works fine, but i felt that I was messy.

At a minimum, I wanted to know the first post in the loop so that I could alter its presentation. Naturally adding the last posts in the loop would be a sinch.

After doing some digging into how have_posts() works I realized that it was pulling from $wp_query and since $wp_query has everything that I needed it was just a matter of creating a couple of methods.

Lets start off by creating our basic class, name space it whoever you want.

class TheLoop
{
    public $index = 0;
    private $wp_query;
    public function __construct()
    {
        global $wp_query;
        $this->wp_query = $wp_query;
    }
}

To keep things clean, I also added have_posts() which is also where I incremented the post loop.

public function have_posts()
{
    $this->iterate();
    return $this->wp_query->have_posts();
}

Next up we have to increment the post loop, nothing crazy here.

private function iterate()
{
    $this->index = $this->index + 1;
}

Now that we have recreated the have_posts() method and are iterating the post index, we can modify our Loop by creating a new instance of TheLoop and replacing have_posts() with our new method.

$loop = new Axe\Core\TheLoop;

while ($loop->have_posts()) : the_post();
   // Post Stuff
endwhile;

As you can probably tell, nothing much changed here. If you were to do nothing else, your site would function exactly as it did before. But we have done two things.

We moved now have an instance of $wp_query and are iterating through the posts array tracking its current position.

Lets add two more methods first() and last().

public function first()
{
    return ($this->index == 1) ? true : false;
}

public function last()
{
    return ($this->index == count($this->wp_query->posts)) ? true : false;
}

While these should be self-explanatory, first() checks to see if the index is equal to 1. last() checks to see if the index is the same as the total posts count for the current page.

For example, if you had 95 posts and are showing 10 posts per page then the last index would be 10 on the first page while the last index on the final page would be 5.

Let’s create a very basic example.

$loop = new Axe\Core\TheLoop;

while ($loop->have_posts()) : the_post();
    if($loop->first()){
        // Do something special for the first post.
    } else {
        // The rest of the posts.
    }
endwhile;

And that’s it!

If you want to check out the entire code have a look at my starter base theme called Axe and view full code for TheLoop.

The post WordPress Loop Helpers appeared first on Adam Patterson.

The Laravel documentation for Email Verification will cover the setup by reading the documentation. But it stops just short of actually explaining how to customize the email template. I had spent a while trying to figure this out and found that I made it much harder on my self than it needed to be.

Much like customizing your Password Reset emails, we will start off by overwriting the sendEmailVerificationNotification method in our Users model.

public function sendEmailVerificationNotification()
{
    $this->notify(new VerifyEmailNotification());
}

Next create a new notification called VerifyEmailNotification.

php artisan make:notification VerifyEmailNotification

Opening up VerifyEmailNotification and rather than extending Notification, we will extend VerifyEmail.

Now toMail in our new notification will overwrite the default method allowing us to change the template.

In order for an email verification to work, we are going to need a unique URL for each user, this luckily can be returned from the parent VerifyEmail notification by calling $this->verificationUrl($notifiable);

Our completed toMail method will look like this.

public function toMail($notifiable)
{
    $verificationUrl = $this->verificationUrl($notifiable);

    return (new MailMessage)->view('emails.user.verify', ['url' => $verificationUrl]);
}

I opted to use the Blade templates for my emails, so I can output the URL on a CTA in the mail simply by writing {{ $url }}.

As I mentioned previously, I had trouble getting this to work as I expected. I wad incorrectly trying to trigger sendEmailVerificationNotification on the User model, which resulted in null values for the tokens.

The only way I found to trigger the notification was to create new test accounts.

I hope this helps you out, and if you know how to manually trigger the Verification notification then please let me know!

The post Laravel 7 Custom Email Verification Template appeared first on Adam Patterson.