However, as your models get more complex, you may find yourself needing different events. Imagine you have a content model which has statuses, for example draft, pending review, and published. If you want to perform different actions based on the model status then you can attach an observer to the model, and listed for the created / updated events.

You can then check the new status and fire off the relevant code. This can get messy though, and also doesn’t reflect what happened to the model to move it into it’s current status. For example, is the content in “pending review” because it’s a draft that someone wants to publish, or an article that was published but has been bumped back down for review? The current model status doesn’t tell you that.

Now, you can create your own events in Laravel, and fire them off, however that would mean you have some event listeners in your model observer, and some in a bespoke event listener. Messy.

It’s nicer to be able to handle everything the same way. Fortunately Eloquent’s model event system can be extended to support custom events which you can fire at the appropriate point.

To add a new event, simply set the $observables property on your model.

<?php

use Illuminate\Database\Eloquent\Model;

class MyContentModel extends Model
{
  /**
   * Additional observable events.
   */
  protected $observables = [
    'sentforreview',
    'rejected',
  ];
}

This tells Laravel that there are two new model events that an observer can listen for. In our observer, we can listed to these by defining the appropriate function as we would with any of the standard events:

<?php

namespace App\Observers;

class MyContentObserver
{

  public function sentforreview(MyContent $myContent)
  {
    // Your logic here.
  }

  public function rejected(MyContent $myContent)
  {
    // Your logic here.
  }

}

So far, so good. We have defined our custom observables, and built a method to listed for them. However – the event will never be fired. After all, Laravel doesn’t know when it should be fired. Firing the event is simple though. Within your model you simply call fireModelEvent() and tell it the event you are firing, for example:

<?php

use Illuminate\Database\Eloquent\Model;

class MyContentModel extends Model
{
  public function sendForReview()
  {
     // Do any other updates to the model here.
     // Then fire the event.
     $this->fireModelEvent('sentforreview', false);
  }

  public function reject()
  {
     // Do any other updates to the model here.
     // Then fire the event.
     $this->fireModelEvent('rejected', false);
  }
}

Now, you can have a single model observer that handles standard, and custom events keeping everything nice and tidy.

The post Custom model events with Laravel 5.4 appeared first on Lee Willis.

If you do want it to default to the cheapest option, try this simple plugin:

The post Default Lowest Shipping Choice on WP e-Commerce appeared first on Lee Willis.

Fortunately, it’s pretty easy to change this order – simply paste the following function into your theme’s functions.php file, or use a functionality plugin. Just change the $gateway_order array to the gateways you have enabled, in the order you want them, and you’re good to go.

function lw_edd_enabled_payment_gateways($gateways) {
	$gateway_order = array(
		'stripe',
		'paypal',
		'manual',
	);
	$new_gateways = array();
	foreach ( $gateway_order as $gateway ) {
		if ( ! empty( $gateways[$gateway] ) ) {
			$new_gateways[$gateway] = $gateways[$gateway];
		}
	}
	return $new_gateways;
}
add_filter(
	'edd_enabled_payment_gateways',
	'lw_edd_enabled_payment_gateways',
	10,
	1
);

Here’s what our revised default checkout looks like – much neater.

The post Change order of payment gateways in Easy Digital Downloads appeared first on Lee Willis.

/* Set feeds importer to import in chunks of 500, rather than 50
 * Ref: http://drupalcode.org/project/feeds.git/blob/b39b547768abbda3b0d7b5425593c0e7c05800f2:/README.txt#l185
 */
$conf['feeds_process_limit'] = 500;

The post Processing feed imports in bigger chunks appeared first on Lee Willis.

Thanks to the great work that’s been going on in WP e-Commerce core – there are now a bunch of useful hooks and filters that allow the content to be changed by filters rather than by editing the plugin direct.

So – if you want to add the SKU to your order emails you can just install and enable the plugin below to add it for you.

The post Adding SKU to email notifications in WP e-Commerce appeared first on Lee Willis.

Before:
<body class=”html not-front logged-in no-sidebars page-dashboard toolbar toolbar-drawer”>

After:
<body class=”html not-front logged-in no-sidebars page-dashboard role-id-2 role-authenticated-user role-id-8 role-site-administrator user-uid-10 toolbar toolbar-drawer”>

Handy if for example you want to style things differently based on the user’s role. Just drop it into your module, and replace MODULE with your module name.

The code:

function MODULE_preprocess_html ( &$variables ) {

  global $user;

  foreach ( $user->roles as $role_id => $role ) {
    $variables['classes_array'][] = "role-id-".$role_id;
    $variables['classes_array'][] = "role-".strtolower(drupal_clean_css_identifier($role));
  }

  $variables['classes_array'][] = "user-uid-".$user->uid;

}

The post Adding body classes based on Drupal role / user ID appeared first on Lee Willis.

Some of that codes extend existing projects, and include external projects in subfolders. SVN has a great piece of functionality that allows you to embed other SVN repositories in sub-folders in a project, and have them automatically updated.

Unfortunately – while I’m using SVN locally, the code I’m including is hosted in GIT repositories.

Natch.

Fortunately, the Internet is a wonderful place, and after a woeful tweet, the ever-helpful @tarendai came up with the spectacularly useful observation:

Turns out that github implemented SVN access to their repos. So – you can include github² projects into SVN repositories as SVN externals – hurrah!

To get it set up, it’s just the same as a standard SVN external, e.g.

$ svn propedit svn:externals .

and then give the folder you want it put in, and the github SVN url, e.g. to include the Campaign Monitor PHP API:

createsend-php https://github.com/campaignmonitor/createsend-php/

#win

1. Note: I’ll probably move to git shortly, tempted by the fact I use it at work, and by the awesomeness that is git-flow
2. Yes, I know that doesn’t solve it for the general git case, but seriously – how cool anyway