Do you use Auction2Post [A2P]? If you don’t its a wordpress plugin which automatically implants listings from ebay as wordpress posts, including affiliate links through the ebay partner network from which you earn a commission. Its quite useful. Read my post about it here. Anyhow if you don’t use the plugin you can pretty much skip this post, unless you use a similar thing which is generating all kinds of nasty strings you don’t want in your posts

This post will show you how to sanitise your auction2post posts for annoying (and contract breaking) ebay auction strings, it even has 125 rules already in a file for import!

The problem

Auction2Post is great in lots of respects, its well written and does a prescribed job. Where it caused irritation for me is arguably after its done its job, after the wordpress plugin had created its posts. You see you can create posts via templates, which is great, it allows enough customisation for most, however I wanted a bit of text processing as often you are left with irritating auction footers and garbage text which make the user hit back or close at a displeasing rate (some of these ebay strings might actually make your Auction 2 posts sites break ebay partner network terms of service, its really worth sanitising your posts as I describe below!)

The Solution

This problem with Auction 2 Post and wordpress is one of the reasons Automated Editor was born, to give a bit more freedom in text processing, wordpress filters are great but I don’t think filtering hundreds of ebay phrases like that is effective.

If you want to cleanse your Auction2post posts of dirty ebay auction footers and the like here is how I currently do it:

1. Install Automated Editor plugin on the blog in question. (Get it here and install like a normal plugin.)
2. Go to the plugin (Auto Editor on its plugin menu) and read the disclaimer (big red box) and THEN accept it.
3. Download the rules file I have created (Get it at the bottom of this post) and unzip it somewhere.
   
4. Go to “Import/Export” on the Automated Editor plugin menu.
   
5. Choose the aforementioned rules file and hit import.
   
6. You should now have 125 or so rules in your rules list
7. Now go to Schedules on the plugin menu and then click Add New.
8. Scroll down and hit Select All (under the long list of rule checkboxes ebay1, ebay2 etc.)
   
9. Scroll down again and select Most Recent Post from the Target dropdown.
10. Make sure run option is on “After a post is published”.
    
11. Save it.
12. Turn on schedules.
    
13. Post a test post, either via A2P or manually, it should remove any of the 125 annoying (common) ebay auction strings it finds! Sorted.

Notes on this method:

• You will need the Full version (Ultra Pro) of Automated Editor, the free version is limited to 3 rules and this rules file alone has 125 ebay-string removing rules. It’s cheap though here.
• If you already have Auction2Post auction posts in the system you will have to setup a different schedule to operate on those, I usually set this up before I set any automation (it’s quite easy, just do the same thing and switch out “Most Recent post” for “all posts”, run it once then disable the schedule – you don’t want it operating on them all every time!)
• Currently this removes 125 strings I have found previously, mostly from uk auctions, I am considering writing a simplified version of this whole setup, an “Auction2Post Post Cleaner” which you can just activate and leave, perhaps with cloud rules, so watch this space. Good thing about the above setup though is you can continually improve your own rules file by adding your own strings.

Rules File

The link below offers a RAR’d version of my Automated Editor rules file which contains 125 x ebay string removal rules, yours for free Please however do use carefully, as with all automated-editor situations if you don’t understand what you are doing then don’t use it, this is for the people that understand the above problem and have the full version of the plugin.

Download Rules File
[Right click-Save as]

If you want to read more about the plugin you can check out this post on, What is the point in Automated Editor or go right ahead and get it from wordpress.org or buy the professional version at AutomatedEditor.com.

Watch this space for a few posts on how I use the plugin, (it works fantastically well when rigged up with Auction2Post.)

function get_tag_name( $tag_id ) {

     $tag_id = (int) $tag_id;
     $tag = get_term( $tag_id, 'post_tag'; );

     if ( ! $tag || is_wp_error( $tag ) )

          return '';

     return $tag->name;

}

I am writing Automated Editor, a wordpress plugin which will give you a bunch of pro automation possibilities, in case you were wondering.

Website hacker entrance vectors (have any security holes?)

Common CMS, E-Commerce systems and forums (out of date or zero day, they all have or have had vulnerabilities) – WordPress, Drupal, OSCommerce, Gallery, PHPBB, VBulletin etc. etc. Particularly relevant here are the open source systems, but they are all susceptible – how many of these do you have installed where? For me these could of been answered with “a lot” and “some places”, clarity has now been restored but more on that later.

CMS Plugins (^^) – Often overlooked (especially by me), installed plugins can in themselves be entry vectors, often CMS’s push their communities to develop additional functionality for their system, which is a good thing, however if the system itself doesn’t deal particularly well with the security of folder structures or indeed how plugins are accessed they can offer ways in. Be careful with plugins which deal with file management and code execution (e.g. file attachers/uploaders etc.) Try to use late version highly rated plugins from reputable sources, with things like WordPress, plugins are low risk though as it has an excellent security model.

Bespoke server-side code and CMS’s – in my experience these is often LESS likely to get hacked, firstly “hackers” in this case are more likely to be script kiddies sitting in web cafes in some of the poorer world nations, they often use known exploits on common systems rather than trawl the web, searching for one off programmer mistakes. If you are behind the bespoke stuff leave out as many foot prints as possible and triple check everything. For bespoke stuff the most likely point of entry is simple SQL Injection, use SQL parameters.

FTP/WebDav – This really comes down to passwords as next indicated.

Passwords – Acquired by trojans or traffic sniffers, it becomes irrelevant what security you have in place across the whole setup if you don’t look after them properly. Avoid connecting to anything unencrypted (or at all if possible) on any network you don’t 100% trust, WIFI and wired, even if it’s a friends they could have a network sniffing Trojan on an idle machine. Install good anti-virus and protection software. Use Avast (free for private use) and Spybot Search and Destroy (these two are plenty.) Be careful with providing access to other users, whether it FTP, CMS, SSH, whatever – you may trust them but do you trust their computers?

Detection and Fixing – Realising you’ve been hit and fixing it

So after they gain entry, what would a hacker really do? Often with web hacking the motivation is kudos, money or sabotage – all are achieved through defacing, deleting or modifying web pages/logic and/or altering/downloading databases. A nightmare from the point of view of shared hosting users.

Depending on how they gain entry a hacker (or their automated executing code) may search through all of the files they can access, through ftp or server-side scripts, built to identify possible files to manipulate. They may download copies of things (e.g. databases!) but will likely set about cycling through all available webpage files and doing things such as:

• Inserting code within the page (iframes to bad websites, links to their websites – designed to improve their search engine rankings, redirect code which just shuttles people on to their sites)
• Replacing the file with a predesigned page (kudos fronts ‘this website was hacked by…’)
• Replacing common server-side functions and variables (e.g. replacing all the send values on email scripts to forward emails to an account other than the owners)

If you have a single site, or 10 or something the chances are you personally check them all every now and again, getting a little facetime at least once a week say. In this case your opportunity for hosting a hacked site is 7 days, not awful, not great – Google and browsers will start blocking your site if the hacker has inserted any code going to malware or similar, and otherwise may start to drop you down the rankings if your site now displays a ‘hacked by..’ page instead of your wholesome site.

In the case of a lot more sites on the host this can mean no detection for a longer time, if no system is in place, often first recognised through a drop in statistics/earnings (more likely earnings as in the case of iframed malware a change in the number of hits can be not hugely obvious.)

To add confusion to the mix it’s not unknown for hackers to mask their changes to you, it’s very easy with .htaccess files and php/asp headers (for example) to show content relative to its viewer. E.g. the hacker could shuttle people coming in from Google to a hacked page but people that access the site directly (typing it in) get shown the normal site. Furthermore they may not hit every site you have, perhaps a handful of random choices, some folders not others, a smokescreen like attack which could change each time.

Chances are once you get all your pages fixed and get around to looking at where the security hole is that when you recheck your sites they would have been hit again. This tells you two things, 1. The hacker is relentless (or more likely has a relentless automated program, exploiting 24/7) and 2. You have not plugged the security hole. Or if you are really unlucky you are being hacker tag teamed.

So anyway, detection. How do you go about knowing the integrity of your web portfolio? What if it spans 10 shared hosting accounts or 4 servers? Well likely if you own your own server you have spent the time/cash in locking everything down, what I suggest here would be useful to you guys but you may already have a better solution in place.

Currently there are a bunch of services which will do this for you, of which I have tried zero. “Monitoring” services are available worldwide ranging in prices drastically, for me though even the high end services didn’t offer a full set of features and were mostly hugely overpriced but for the top 50% of the portfolio, not effective for me.

The good things about using external monitoring services are obvious but none seemed to be able to offer realistic change monitoring (e.g. WordPress blogs may change content between <div id=”whatever”> and </div> every hour but the rest of the page should stay almost the same.) It is important they see the addition of malicious code to good pages and not throw constant false alarms. For ‘this website was hacked by..’ pages though they probably do a good job (as well as malware detection.) Uptime monitoring is also common as part of the packages, useful without doubt.

I suggest another way though of monitoring an established portfolio, that is the way I have resolved my recent hacker attacks, a realistic option for shared host/anywhere-in-the-world-with-a-laptop client based use. Ultimately an extension of a few older applications I wrote to manage a growing portfolio, weathered by several hacks across accounts within the past 6 months – Hard checks of every important file.

At first I wrote my system to simply allow me to take stock of the sites and CMS’s I have in place, to work out possible security holes from behind the scenes – but it turns out it works surprisingly well in identifying breaches. By checking your actual live file structure (.htaccess, index.php, default.aspx, index.html etc.) against a known correct file structure snapshot, you take the whole http part of the checking out of the loop, effectively making it a higher level integrity check than external services can ever offer.

By making Checksums of every critical file (often hackers just hit index.php, index.html, default.aspx etc.) within a given ftp/file structure and then automatically rechecking at scheduled points it becomes easy to minimise your window for financial fallout from hackers. This may seem like a time/bandwidth/processor consuming task but in actuality 100 websites with WordPress installed could be checked in a few Mb of download – in terms of modern data use that’s a few browses of a facebook photo gallery. What’s more it can run in the background, only prompting you on changes to files, as frequently as you want.

The side benefit of producing complete hosting account checksum snapshots is you are also able to accurately backup a working copy of your hosting account. Built into the checking process this means that you can then correct hackers’ malicious changes with a click of a button.

This of course does not take into account more hard-file based websites, database changes or regularly altered sites. I recommend automated screenshots to cover these or the combination of external monitoring services and integrity checking.

I have written an alpha release of this system (named Website Integrity Checker for now) and will gladly distribute/discuss it if you drop me a comment below. A beta copy might make its way out sometime.

The question then comes after you have 30 wordpress blogs on the go, various niche market’s blogged too or personal sites about cats or what have you, what then? Updates then. WordPress do update fairly regularly, they aren’t the slow moving behemoths some other companies are because they are open source, and that’s a good thing. Anyway maintaining 30 copies of wordpress is actually a lot easier than it sounds, an update is usually nothing more than 10 minutes uploading the new wordpress files over the old ones via FTP. But say you had a little project where you wanted to create a few more wordpress blogs. For the sake of this post lets say you wanted 90 blogs. 90 WordPress blogs installed on an average web host (I suggest 1and1) is not a big deal. It can be as big a deal as you make of it but in your pursuits and interests online its potentially likely to crop up.

You can run 90 wordpress blogs (or 1000 etc.) from 1 instance of wordpress. That is 1 wordpress folder on your host serving to 90 blogs at blogsite1.co.uk, blogsite2.com etc. thats nothing new – I am sure the quicker off the mark or longer in the tooth of wordpress users have been doing it for a while, but somehow I missed this up until I got past the 30 blog mark and so I thought its about time I looked at the option of hundreds of wordpress-blogs running from 1 folder, a project has come up. The reason this works by the way is the wonderful way (take not web developers) that wordpress splits its config files and its database. The only file in the wordpress files you upload to your blog that contains any site specific data is the config file, which pulls everything from the database.

On the preface there are both good and bad things about doing this with word press, here are the pro’s and con’s as I see them pre-project.

Pros

• Single central wordpress folder  – 1 wordpress folder to update periodically
• File size – rather than using up 4mb per wordpress install, this method uses 4mb per x number of wordpress installs, although space isn’t an issue really in current web hosting
• Plugins and themes only need to be copied once – they can effectively be shared
• Easier to backup – backing up files of wordpress blogs is pretty pointless apart from wp-content (uploaded images, themes, etc) – putting all your blogs in one basket means backing up the whole lot is a breeze, 1 folder not 90!
• WordPress database is seperate – you could potentially run all the blogs from 1 database too – (capacity dependant) – as wordpress allows table prefix’s
• Adding a blog can be automated – replicating the first wp database from an install can mean tons less setup work

Cons

• Permalink structure may have to be the same? *not 100% on this one and havent tested but there may be issues with permalink setups across multiple blogs as htaccess is shared*
• Other .htaccess differences – because you will effectively only have 1 .htaccess file for all domains pointing to this folder, this puts all that custom .htaccess code out of the window
• Flip side of themes being easy to install is that editing one theme will lead to all blogs using that theme to notice the change, fine if your blogs are stable in design but multiple versions of the same theme will be required if you want to tweak these on a blog specific level, which could make for a messy confusing setup if not through through
• If you are running a network of blogs and want to stay under the radar or just want the sites to be as different as possible – by nature of single resource they will leave footprints unless you are aware and make sure you do things like rename folders for themes non-sequentially etc ( or maybe don’t be paranoid :p )
• Centralising the files for all domains/sites/blogs does mean this folder on this box does then become a single point of failure, loose/break this and the whole of your blog network/project is down. Probably not such an issue with stable hosts these days
• As previous point if you do update, change a file or accidentally delete anything it does effect every site – its a risk but not a big one just be careful!

Limitations

• Unsure about .htaccess but presume custom rewriting becomes a pain as all sites share a file
• There will be a limit as to how many blogs you can run off a single install. It’s probably thousands though – if you had 30,000 sites for example – the file which points the install to the right database tables would become bloated

How to run tens, hundreds or thousands of wordpress blogs from 1 instance – install wordpress once for hundreds of blogs – without MU.

1. Install wordpress into a folder on you hosting (download latest from wordpress.org and then upload via FTP/copy across network)
2. Get your database details together, you will need Database Name, Database Username, Database Password and the Database host for each of the databases you are going to host wordpress tables in
3. Install a single blog using the normal method – point a domain at the folder, go to that domain and follow the wordpress wizard, entering your database connection details and this blogs title.
   1. Go through this newly installed blog and commit any changes that you will want duplicated throughout the new installs – delete the “hello world” post/default wp links for example.
   2. Imagine this like creating a ghost image for a network of pc’s – you want to make a bare bones default wordpress setup so you can replicate this onwards without having to redo it.
4. Happy with  your ghost blog setup? go to your phpmyadmin (assuming you have it) and export all the tables for this blog into SQL.
5. Open that SQL into your favourite text editor, in this case I am using Dreamweaver because I like its find+replace.
6. You will need to do several find + replaces here, but by doing this you can literally clone a wordpress installation – (works as at 2.9.1 anyway) – this is great for mass distribution (This is quicker than installing and can be automated)
7. For example if your site was “harrysblog1.co.uk” with a title of  “Harrys Blog 1″ then do a find and replace for “harrysblog1.co.uk”, switching out the new domain to be added, same with title’s, users, post’s etc. This way you could clone a wordpress site and switch out words…you can change the table prefix this way too.
8. Run this newly modified SQL on whatever mysql database you want to run the blog from (could be same one if you mass replaced the table prefix’s)
9. Alter your wp-config.php file very simply:
   1. Open it up and put a bit of logic which basically says “what domain am I loading from, ah this one – use this DB and this table prefix” – This logic can be as simple or as complex as you want it to be – I kept mine short and sweet with literally:

*note this is just how I did it, there are other ways – the code works but was just to test the theory – when upscaled to a network of xxx or x,xxx sites this is automated quite easily

*note2 I am having to cut this post short but if anyone has any questions or wants to know more/help on replicating wordpress or multi blog – 1 wordpress instance installs let me know in the comments

References

Striderweb – this post pretty much explains the theory, a bit like this post – but I actually happened across it after writing the post – well worth reading if your going to do this – Stephen Rider has made a great plugin that will do everything you want it to do as above, I winged it and just modified the wp-config which simply worked in my case so personally I didn’t use it, but no doubt its probably worth a try if  you want a more deep solution.

But irrelevant of the selling gumpf I had heard good things. In the uk it worked out as £68 or so with currency conversion to buy Auction 2 Post and a pack of 20 themes and it is, worth it. Worth it that is if you intend to use it to satisfy a need. I wouldn’t buy it if you are just looking for some new “get rich quick scheme” to burn your money into, get it if you know wordpress, get it if you already have some ebay sites (php bay, bans, bespoke – please say you have bespoke!) or a good use within an established site network/blog context.

There are lots of ways  you can use Auction 2 post, essentially it just posts ebay auctions as posts’ and offers you a host of ways of doing that, within templates, automatically etc. and you can stay within the ebay partner network rules as long as you invest a bit of time in reading them (you should do this when you sign up, by the way!) A word of caution at this point though, EbayPartnerNetwork is apparently getting hotter on the unscrupulous affiliate and if you were not careful you could probably tear their Terms of Service to shreds with this plugin, not that I would know about doing that! EPN (Ebay Partner Network) is lucrative and worth investing time if your a natural SEO developer, auction 2 post is a nice implementation of a wordpress plugin that helps you into this – but its all about how you use it!

I won’t go into how I am using this WordPress plugin, or how you should – there are a lot of great ways this can work for you. I have set up several experimental sites and am using it in xx other blogs, I will perhaps release some results, experiences and stats in the near future, although we don’t want A2p to get too big do we The forum’s and support for Auction 2 Post are great, zizby/radio is quick to respond to your questions about the plugin – the member area is simple but I have found a few dead links – nothing important and I am sure they’ll fix this. In essence if you know what your doing with the web and wordpress you need this plugin in your affiliate arsenal!

Get Auction 2 Post
(Just skip through the blurb and click order now)