Sure you can install a module like the Custom Login Page Customizer but if you have a little CSS know-how why not do it yourself?

This is how I have been doing it, first open your functions.php file and add the following lines of code;

function custom_login_css() {
wp_enqueue_style( 'theme_login_css', get_template_directory_uri() . '/css/login.css', false );
}

This simply calls a custom CSS file to the login page allowing you to style it.

Next we need to add a pair of functions which will update the logo URL and alt text to use your sites URL and Name.

function custom_login_url() { return home_url(); }
function custom_login_title() { return get_option('blogname'); }

Finally set a call so they are only loaded on the login page.

add_action( 'login_enqueue_scripts', 'theme_login_css', 10 );
add_filter('login_headerurl', 'theme_login_url');
add_filter('login_headertitle', 'theme_login_title');

Now all you need to do is create your custom login.css file and drop it into the location you set in step one, I will leave this bit up to you.

The post Fancy a Custom WordPress Login Page? Heres How first appeared on Chris Walton.

add_theme_support( 'post-thumbnails' );

Violla you can now upload Featured Images to your pages through the CMS. You will obviously need to then extend your themes page templates to call in the images. This can differ slightly from theme to theme so my advice is to checkout how it is applied within files such as index.php and single.php being a good place to start, you will be looking for the code which looks something like this;

<?php the_post_thumbnail('post-image'); ?>

Remember if you are using a theme sourced off of the WordPress Theme Directory you will need to remember that any updates from WordPress may remove any additions you make. For more information on this feature why not check out the WordPress Codex page on Post Thumbnails.

The post Adding Featured Image Support to a WordPress Page first appeared on Chris Walton.

Up until recently the agency I work for used a combination of mainly Bitbucket but with some held with Github and decided to consolidate them under Gitlab instead.

The process I followed to update my local copies of these Dev sites was pretty simple;

1. Open Terminal and navigate to the sites working directory, for example

   $ /Applications/MAMP/htdocs/myproject

2. Then I listed the existing remote URLs to check where they are currently pointed, and so whether they need to be updated (good to check that I hadn’t already updated it)

   $ git remote -v
   origin  git@bitbucket.org:USERNAME/REPOSITORY.git (fetch)
   origin  git@bitbucket.org:USERNAME/REPOSITORY.git (push)
   

3. Now change the remote’s URL from Bitbucket to Gitlab with the git remote set-url command.

   $ git remote set-url origin git@gitlab.com:USERNAME/REPOSITORY.git.git

4. I then verified that the remote URL had been updated.

   $ git remote -v
   origin  git@gitlab.com:USERNAME/REPOSITORY.git (fetch)
   origin  git@gitlab.com:USERNAME/REPOSITORY.git (push)
   

That wasn’t such a chore now was it? Finally you can grab any updates which may have been made to the repository since the last time you grabbed a copy by using git fetch

The post Changing a Local Git Repo Origin first appeared on Chris Walton.

After over 3 years working in an agency building fully responsive Foundation based websites its finally time to start considering pulling this site down and replacing it with something a little bit more modern!

Oh and Happy New Year! Hope 2017 is great for all!

The post I really need to do something about this website first appeared on Chris Walton.

Now you can use a Git GUI like Gitkraken to manage this easily however I think it is important to also know how to do it through Command Line.

To list your currently available tags in Git perform the following’

$ git tag
1.0.0
1.1.0
1.1.1
2.0.0

The general reasoning behind the version number format is to state a MAJOR.MINOR.PATCH or BUGFIX so in the example above version 1.1.0 introduced minor but substantial changes to the project in hand, version 1.1.1 fixed some minor bugs or applied a security patch (for example) and version 2.0.0 introduced some major updates to that project.

To create a new new tag do the following

$ git tag -a 2.1.0 -m 'v2.1.0

And then you can push to your remote repository

$ git push --tags origin master

If you need to removed the current tag version for whatever reason

$ git tag -d 2.1.0

Deleted tag '2.1.0' (was 074205)

Remove the current tag version remotely

$ git push origin :refs/tags/2.1.0

To git@bitbucket.org:webtise/sagepaysuitepro.git

- [deleted] 2.1.0

There is alot more to tagging but this covers the day to day basics.

The post Working with GIT Tags (the basics) first appeared on Chris Walton.

Open the page you want to update and add the following code to the Update XML Layout option

<reference name="root">
 <action method="addBodyClass"><classname>my-body-class</classname></action>
</reference> 

And there you go, your page now has thi

The post Magento, add your own body class through XML injection first appeared on Chris Walton.

1. Find the attribute_id of the your custom attribute from the eav_attribute table
2. Open the table catalog_eav_attribute and search for the matching attribute_id from step 1
3. Update the field is_wysiwyg_enabled to 1

Happy coding!

The post Updating a Magento Custom Category Attribute to have a WYSIWYG editor first appeared on Chris Walton.

This can be accomplished by creating a symbolic link, also known as a symlink, between the location you want your directory to be stored and the spot where it should be.

I am going to use the example of a Magento media folder which I am going to moved outside of the http directory and will create a symlink for it.

cd path/to/magento/root/http
ln -s ../media media

Simple, all we do is first put the location of the folder (or file) and then name it in this location.

In doing this we could have renamed the directory in the external location to say ___media but it doesn’t matter as long as the symlink itself is still called media

The post Symbolic links… first appeared on Chris Walton.

Import a database

Importing Databases to your local server is a common activity which is easiest to perform through command line, especially when dealing with larger databases common with platforms like Magento.

So the first thing to do is to pop open a terminal window
/Applications/MAMP/library/bin/mysql -u user_name -p database_name < /Users/user/Documents/database_import.sql
You will then be prompted for your mysql server password and after a short (to lengthy) delay your database will have been imported.

Delete Databases

In the instance you need to delete a database for whatever reason open up your preferred method of editing your database (PHP MyAdmin, Sequel Pro or Terminal being 3 options) and perform the following

DROP DATABASE database_name;

The post Working with MAMP and Terminal, import and delete a local database first appeared on Chris Walton.

Magento is no exception, be it an issue with a module install/upgrade or an order which hasn’t progressed for any number of reasons… Luckily changing a Magento order status is pretty easy a task;

1. First we need to find the entity ID for particular order, this is different from the Order ID we see in the Sales Grid but isn’t at all difficult to find. Simply open the order in your browser and examine the page URL, this will contain the ID
2. Open following tables and search for the ID we found in Step 1
   • sales_flat_order
   • sales_flat_order_grid
3. Update status’ from processing to complete (for example, you may be wishing to cancel the order)

And thats it, pretty easy!

The post Updating an Order Status in the Magento Database first appeared on Chris Walton.