1. The website was to be a bartering site and the idea was that users would add their details to the website as a means of offering their services and/or products. How I made it and what software I used was totally up to me, although knowing I was a ‘WordPress Pimp’ for most of my site creations, my friend did ask that it was not to look or work like a blog and that people could not easily see that it was a WordPress site. It needed to look professional and yet be very user friendly as well. He wanted it to run as a CMS.

2. There needed to be a login access point available via all pages throughout the site which contained username and password textboxes. Further to this, it was necessary that once the user logged in they were taken directly to a specific front-end page within the site. There was no need for users to access the admin area or backend at all.

3. Once the user logged in the login textbox would be replaced with a ‘Welcome [username]‘ and the option to logout as well. It also needed to be made perfectly clear that they were now logged in and were accessing as a member, as opposed to a guest.

4. Each user’s details needed to be set out in specific format which was consistent throughout the site. A mock PSD file was given to me showing the overall site ‘look’, including the front page, user details page [profile], search page and information pages. Each page had its own set of functions to include and each users details would be a page that could be read by other members. It was to contain all the details of what they offered and what they wanted, plus contact details, an image, and it needed to have keywords specific to each profile

5.  Guest were to be allowed access to a few pages throughout the site but members could access 99% of the site. Admins needed full access to everything but they were not overtly website savvy so it needed to be user-friendly for them to manage – without having to read lots of tutorials etc.

6.  The details the users provided had 2 distinct parts. a] Details of what they offered in terms of bartering and b] details of what they wanted to barter for in return.

7.  The search functions needed to be good enough to cater for complete searches, searches for what was offered and searches for what was wanted.

8. The site had to be quick loading and able to cater for upwards of thousands of users within the database, with possibly hundreds+ online at any given moment.

9. Each page required different set of functions, and in addition the sidebars also needed to have their own set of different functions, on different pages and posts too.

10. SEO was an important consideration and had to be dealt with in the best possible way.

And that was the basic starting point.

Now I have to admit, a few of these specifications had me thinking quite a bit as to whether or not WordPress was a good option for this particular project. But I like a challenge and so I did a quick bit of research, sat down and thought about the best way to go about a few of the major  requirements and then I dug my boots in and went for it.

Of course, the great aspect of opting for using WordPress is the sheer amount of plugins that are available, mainly because of the large volume of people using this product.

In all honesty, I would have to say that this has not been an easy project and at times, I was pulling my hair out wondering how I was going to accomplish some of the elements needed, but I am happy to report that as of now, it is all completed.

I have learned quite a bit about some parts of WordPress that I have never really touched upon before, had to find and then ‘hack’ some of the plugins I decided to use for the varying areas, and perhaps most significantly, had to do all of this within a very short time frame.

If nothing else, this project really has proven to me that WordPress certainly is a very flexible product and that it can be used in many different ways.

For those of you who think that some of the elements involved within this project would be useful to you, just let me know via the comment section and I will help out where I can.

I am also considering packaging the whole thing and making it available for others too, but still not sure as to whether this is a good idea or not.

Now, I am all for giving credit where credit is due and in 99% of cases I do leave the link to the theme designer in place. Obviously, some clients specifically ask to have this removed, however in this instance, it was not so much that it was linking back to the theme author, but rather, that it was full of links and references which were dubiously ‘spam’ focussed.

So, into the footer file I dived, expecting to find the normal layout and a href”s which could be easily changed. And this is where the trouble started. Instead of the file displaying PHP and HTML code, it simply contained a long string of letters and numbers all wrapped very neatly inside one set of PHP tags, such as this example below.

?php $E7dab924f505e1bffgh8a0292fa5883a9746=’dZDBasMwDIbP81OIPEB82Wm4Lmwt7Lw6jdelZiJRY
4trHVQMoefs4oZQymi2RJ/2fxH636iSfjeAV2h25KSah0Vpls1ec1UxneUxWOcx9JIJe0sqMKOE2pOBwCwYI
RZ3JgaLGOHI8o7VWprFSMbk2oKVyFU6y9UgbBF5oOnRfJL1o7Cp4btv0kW4+VsbMXqgKnfQAfhAHOVRrT
aLTwBX8BHB0jx7VpForyQI1p6ewrxhlDKvQbBG8Fq/8Hh7fnXar3K4bKbfvEhUZJZdsVyuhmTDNMN8dacc+
PNCS3WaO9LOHurTlmn9U3′;echo(gzinflate(base64_decode($E7dab924f505ed4j1bf8a0292fa5883a9
746))); ?

Removing the code does nothing more than destroy the footer completely and trying to leave it in place and work around it, also has it’s fair share of other issues, so what to do to make this a working footer file? Now I would imagine there may be several methods of choice at this point, with the dissection of the theme functions php file  – in unison with hacking the footer file – probably sitting at the top of the ladder. The trouble with this, was I did not have the time to spend going down this road, so I opted for something else.

What if I was to bypass the footer call completely, I thought to myself? And that is exactly what I did. In typical fashion the footer was being called from all of the major post and page files by using the standard code:  <? php get_footer(); ? >

So, in order to by bypass it I created a new footer file, named it footer_new.php and then simply dropped in a new call using the following code instead: < ? php include(‘templates/footer_new.php’); ? >

I prefer to keep additional customised pages in a templates folder, so that is why you see the reference to ‘templates’ in the code, but this can work just as well using any other named folder or you can place it straight into the theme root directory just as easily too.

Note too: That solved the problem of the footer being uneditable, but as I do not like to leave code sitting on a site that I have no real idea as to what it is doing, I also opened the functions.php and removed the same lengthy string of code as was found in the footer, and just to be safe, also deleted the original footer.php file.

If you know of an easier method, then please do let me know, but for now, at least this appears to have resolved the problem and given me full control over the site as it should have been in the first place. Another factor that may need to be considered here, especially in light of the fact we do not know exactly what this code is doing in its entirety, is that your site could well be compromised. Again, just to be safe, I changed the login passwords  [after removing the code] in order to prevent any further problems.

One option you may not be aware of though, is to use two plugins combined that run on the LightBox display structure.

Here are 6 images that I have uploaded to demonstrate how this gallery looks on the page, and then we will take a look at what is involved in setting up a gallery such as this.

Keyword: EASY

Personally, I am not a huge fan of the Media Uploader, [I much prefer to use ftp and my own-named image directory] however, for this exercise, I have used what WordPress specifically provides for this task.

So, what did I need to make this simple gallery?

1. Two plugins: Lightbox 2 [basic Lightbox which provides Ligtbox functionality] and Add Lightbox [automatically adds the rel="lightbox[ID-OF-THE-POST]” to images linked in a post. The ID-OF-THE-POST is unique per post so all images per post are grouped in one lightbox set.]

2. A few assorted images – I deliberately chose a mix of varying sizes for this example.

3. 5 minutes of your time.

And that’s it! What could be easier for a simple little gallery?

via [Source]

However, there are many other things you can do, including the following:

1.  Make sure you do not give unnecessary ‘Write’ permissions to directories and files that do not need it [done via FTP].

2. Moderate your registrations for users on your site.

3. Use secure passwords.

All very simplistic and not very hard to implement and yet in doing so, you will make your site so much more secure.

I am constantly amazed at how many sites I work on for people, that have such simple passwords in place. If your name is John, it is probably not the best idea to use ‘john‘ as your password. And yes, this would seem obvious, but as I say, I see this kind of thing all the time. Look at it this way: no amount of secuirty will keep out unwanted visits to your files, if you are silly enough to leave the key on display at the front door.

Of course, one of your best safeguards if you are hacked and you are at risk of losing all of your site content, is to make sure you do regular backups of your database. This will be covered in a more in-depth article to come soon, but for now, let me highly recommend that you do at least a ‘weekly’ backup of your database. It really does give you peace of mind.

A few excellent articles on WordPress security:

Is your WordPress blog hacked?

Hardening WordPress

WordPress Hacked

So, how do we get this result? Well, it is quite simple to be honest. All you need to do is copy your archives.php code into a text editor and then set about making any changes you wish. You can make as many structural and CSS changes as like and is only limited by your imagination. To make each one display differently on your site, you need to save each with a different name. This is the important bit and is controlled by something known as the WordPress Template Hierarchy, which without going into too much detail here, runs something like this [as applied to categories]:

Category Templates:
1. category-id.php – If the category’s ID were 6, WordPress would look for category-6.php
2. category.php
3. archive.php
4. index.php

So, what you need to do with each individually structured/styled category archive is simply name it appropriately, i.e as in the example above: category-id.php

In my instance on this site, the Post Its category is ID:24, so my category archive template is named category-24.php. My Themes category archive is based on it being category ID:14, so it becomes category-14.php and so on.

It is then just a simple matter of uploading your new files into the relevant theme directory and hey presto, you have individually styled category archives on your site.

http://jamesict.com/wp-admin/post.php?action=edit&post=96&message=7

The important bit we need is the post=96 [just take note of the number].

And all we have to do is then apply a bit of styling via some quick CSS.

To do this we apply some style tags and throw in whatever CSS changes we choose. I have made a simple background colour change to this post by applying:

#post-96 .entry {background:#BEC3B3;text-align:justify;}

In my CSS, the posts also fall under a class of .entry too, so I have included this in the CSS change.

So that explains what a permalink is and what it does. The next step is to work out how to actually set them in motion.

Unfortunately, this is where it takes a twist and turn and things get a little bit more tricky. Setting the permalinks structure via the admin panel – Settings – Permalinks, is easy enough, but when you first attempt to do this, it will not work. And yes, there is a perfectly good reason as to why not. You see, when you make this adjustment, the structure change tries to write some code to a particular file and the problem is [especially if you have a new WordPress default install], it is most likely you do not have this file at all. It is called .htaccess and is nothing more than a simple txt file with it’s only purpose being that it will include little bits of code that will be server specific and make such things as permalinks work. it’s to do with something called mod_rewrite, but I’ll let you read all about that in the Codex if it really interests you that much.

The point here is that it is very easy to make a .htaccess file. It can be done in virtually any text editor by opening a new file and then saving it as .htaccess. Notice there is nothing in front of ‘.’ and don’t worry, this is not a typo. and no, no need to write anything whatsoever in the file. Trust me – it’s not necessary.

So you make this file and the next step is to get it online. Again, tricky if you have never used something called FTP, but remarkably easy if you have. All you need to do is upload your .htaccess file to where your WordPress root files reside on your server. If you are not sure where this may be, just look for the location where there are lots of files all beginning with ‘wp-’ and drop in the same directory on your server. That’s that then? No, not quite, but almost.

This particular file needs to be written to when you make the changes via your admin panel, as mentioned above, and in order for this to happen, you need to give the file some special permissions. Again, this can be server specific, but more often than not, you can give it a permission of 777 [using your FTP program will accomplish this task] and then make the changes to your permalink structure in your admin panel. This is a security risk though, so as soon as you have made the changes, you should go back into your FTP and set the permissions back to something like 644. This will keep it safe enough from anyone doing any damage should they be of a ‘hacking’ character and inclined to be nasty to your and all your family.

In conclusion then, making the changes required to set your site to permalinks, is easy enough, but does require a few steps. The good news is that once it is done, you will probably not have to touch them again for as long as you wish to keep your site this way.

If you decide this is all too hard, just get in touch and I will give you a hand…

FTP also provides much more flexibility in how you choose to keep your file structures on your site. By default, WordPress will upload files to a directory structure such as /wp-content/uploads/year/month/filename which is fine, but if you are like me, you may prefer to keep all of your audio files in one location and all of your images in another. FTP enables this choice – WordPresss does not.
So, if you would like to have more control of how you set up your themes, and upload your files and plugins, then FTP is an obvious need.

And luckily, there are many free FTP clients available for you to choose – even in the form of addons in browsers such as Firefox.

Three free FTP clients that I highly recommend:

FireFTP [a Firefox addon] ~ AL FTP ~ Filezilla