The electric doors simply failed to close correctly on regular occasions. This fault would manifest itself in a number of ways:

1. On attempting to close the door from either the fob, handle or internal controls it would slide to a closed position and then open up fully immediately of it’s own accord. Sometimes it would take up to 18 attempts to get the door to close. So much for the convenience of an electric sliding door (one of the features that attracted us to the car in the first place).
2. On attempting to close the door (as above) it would close fully but then open by about 1 inch of it’s own accord some 5 or 6 seconds later. Giving you just enough time to get in the car and drive off with the children in the seats. The door then ‘flinging’ fully open once in motion.

We reported the problems to the Evans Halshaw Kia dealership and arranged for the vehicle to go back in for repair. The fit of the dashboard panels was rectified but the dealership claimed that they could not reproduce the problem with the doors yet for us it persisted.

The car was booked in again, again returned without a solution and booked back in again and again and again… we even provided the dealership with video footage of the fault since we felt they simply did not beleive us.

On one particular occasion we drove to the dealership to drop the car off and collect a courtesy vehicle with all 3 kids in tow only to discover that the courtesy car had no petrol and a faulty petrol cap, making it impossible for us to fill the vehicle.

Again and again we were fobbed off by the Evans Halshaw Kia dealership in Reading. We then discovered upon trying to book the car in one day that they had lost their franchise and that they would no longer be able to deal with the issues we had with the vehicle (Great!).

It took us some time to find a new local dealership that could provide a courtesy car. West London Motor Group Kia in High Wycombe in this case.

We booked the car in with them to see if perhaps they could resolve the issues with the electric sliding doors. Initially we encountered the same problems, they were unable to reproduce the problem with the doors but did replace a number of parts. Another visit later and still no joy. By now as you can well imagine the situation was no longer in any way amusing. We were having to ferry our children about in a car which we simply no longer felt safe in and were well and truly fed up with the frequent visits to and from the dealership.

We decided to contact Kia customer services in the vein hope that they might be able to sort things out for us and let us enjoy the car which we had paid good money for.

After applying a fair degree of pressure we eventually convinced Kia customer services to provide us with a like for like replacement vehicle for a period of a week while they had our vehicle in to resolve the issues with the doors.

Alas nothing with Kia is simple (or enjoyable)…

On dropping our car of at the dealership we realised that the replacement vehicle that they had provided would not accommodate 3 children in car seats. We called Kia and informed them, they claimed that the rental company had contacted us to ask if the car was ok and I had confirmed that it would be fine (a complete lie). I requested that they provide us with a new rental car that would accommodate the children such that we could actually go out as a family in one car (not an unreasonable request when we have purchased a £20k family car from them). They claimed that they could not provide a suitable vehicle (not what I had been told when they promised a like for like replacement in the first place) so I suggested that I could find a suitable rental vehicle myself and they could reimburse us the cost of said vehicle.

Whilst this seems like a reasonable suggestion and a logical solution which would leave them with a happy customer they initially refused to cover the costs. A couple of heated phone conversations later they finally did the right thing and agreed to pay for the rental vehicle that we had located. The rental firm that provided us with the unsuitable vehicle (via Kia) tried to sting us for damage to the rental car totaling £150 but that’s another story.

By now I’ve spent a considerable amount of time and energy trying to resolve the issues with the car and have had to take time off work on numerous occasions to deliver the car to the dealership and collect it again. By perhaps what can only be described as a stroke of luck, after having the car for a full week, the dealership managed to fix the problems with the door. Ironically this was the result of following instructions from a technical bulletin that had been issued by Kia regarding the lot from which our car was born… something which we suggested that both dealerships investigate a number of times.

You might think that this is the end of the story, alas it is not. Since collecting the car we have discovered that during icy weather the rear sliding doors now often refuse to open at all (again an intermittent issue) and the air conditioning has stopped working completely so we have the car booked in with the garage for ‘another’ visit on the 2nd of January.

Today (1st of January) whilst out with the whole family in the car I realised that the engine was not responding as it should, the car was loosing power on hills and struggling to maintain motorway speed. We managed to get off the motorway (not a great place to stop with 3 small children) and pulled up. With a burning smell and smoke emanating from the engine bay we decided not to proceed any further. Thank god we were following friends so they helped us to ferry the children back home and the very nice man from the AA came out to tow the car to the Kia dealership.

So the question now is what next… can we really ‘endure’ this car any more. We seem to have a lemon… a car built on a Friday perhaps? In any case the stress associated with this car has us considering our options… even if that means selling the car at a huge loss just to get into something reliable and safe for our family.

Kia are unwilling to even consider replacing the vehicle or making any kind of good will payment to alleviate the trouble we have had… apparently all we can expect from them is a free service and I simply don’t think that’s good enough.

Whilst dropping the car off at the dealership today with the nice man from the AA I happened across a chap eying some of the cars on the forecourt, he was looking to buy a new Kia Sorento. I advised him strongly against purchasing a Kia and relayed the story of how reliable and well built our Sedona is, he seemed convinced… so that’s about £20,000 I’ve just lost Kia.

I’ll continue to relay my story to every person I know and meet until I’ve lost Kia at least £1,000,000 in sales. With 5,000 unique visitors to this blog every month and an extensive social networking contacts list I’m pretty confident in my quest.

Update: Join the I promise to never buy a Kia Facebook group to show your support!

Just as we exported our article data from Textpattern we ‘could’ also export our Link data and then use the same import process to pull it into ExpressionEngine.

However this is not the route I’m going to take. Personally I would much rather maintain my ‘noteworthy’ links using a tool like Delicious so I’m going to show you how we can migrate our Textpattern links to Delicious and then have them displayed inline within an ExpressionEngine template.

Luckily for us there’s a fantastic Textpattern Extension called ajw_bookmarks that provides us with a quick and easy way to export our Links to a ‘Bookmarks’ file which most bookmark services and browsers can import.

Download and install the Extension within Textpattern and then navigate to the Bookmarks tab within Extensions and select the first option ‘Export bookmarks’.

Now that we have our locally saved Bookmarks file navigate to the Import Bookmarks tool on the Delicious website (obviously you will need to log-in first) and then choose the ‘Custom import’ option.

Now we want our bookmarks to be visible to the public so check ‘make all my imported bookmarks public’. If you wish to use Delicious to record bookmarks for personal use and also for display on your website you may want to tag all the bookmarks you are going to import with a keyword such as ‘noteworthy’ or similar. This is the approach I took. By adding this tag I can identify which bookmarks should be pulled out of Delicious for display on my website. Now click ‘Import Now’.

Delicious should have a bit of a think, depending on the size of your links collection and then display your imported bookmarks.

We’re going to use the ExpressionEngine ‘Magpie’ plug-in to pull our Delicious links into our template and display them inline. The plug-in will also cache the data so if Delicious should go down our site won’t fall apart. The Magpie plug-in is a part of the default ExpressionEngine install so just open up a template file and drop in the following code:

{exp:magpie url="http://feeds.delicious.com/v2/rss/nathanpitman?count=10&tag=noteworthy" limit="10" refresh="60"} <ul> {items} <li><a href="{link}" title="{title}">{title}</a><br /> {description}</li> {/items} </ul> {/exp:magpie}

Obviously you’ll have to replace ‘nathanpitman’ in the feed URL with your own Delicious username and if you want to pull back bookmarks with a particular tag then include the ‘&tag=’ parameter and variable in the querystring as I have above.

You should now have a nice unordered list displaying your 10 most recent Delicious bookmarks or my 10 most recent Delicious bookmarks if you forgot to change the username in the URL.

If you need to you can also tweak the number of minutes that the plug-in waits before it refreshes the feed display, I’d opt for 60 minutes. The Magpie plug-in defaults to 3 hours if you don’t specify a refresh value.

Next job on our list is to fix up any links to file assets which we have in our entries. Textpattern uses a file download manager which records total file downloads and obfuscates the actual file path in the URL which you place in your entry. ExpressionEngine, whilst being a fantastic CMS, does not provide support for file download counts or obfuscation (here’s hoping for EE2!) which is a shame but hey ho… let’s soldier on.

We’re going to have to repair any links to files in our entries because the two systems link to file assets in different ways. So within the ExpressionEngine control panel navigate to the ‘Edit’ tab and use the search tool at the top of the screen to search for the string ‘/file_download/’ in ‘titles and entries’. This should give you a list of all the entries that you will need to fix up.

Unfortunately we’re going to have to do this manually (unless you can think of a better way!) so download all your file assets from your Textpattern install and then upload them to your file upload destination in ExpressionEngine (Prob best done via FTP).

Now we just need to amend the file paths in our entries so work through the list of entries that contain the ‘/file_download/’ string and replace the old Textpattern file path references with the new ExpressionEngine file path references.

Now, you can either use the ‘copy and paste info’ that the ‘File Manager Module’ provides you with (a standard href link) or hand craft a Textile based equivalent. The choice is yours.

Ok so I ran out of time a little today and didn’t have a chance to explain how we can migrate out Textpattern Links but I promise I’ll cover that in my next post!

First off we will need to upload the text file that we generated in our export from Textpattern in Step 2. I just dropped my file into the web root of my server so I could get at it easily from ExpressionEngine.

Once your file has uploaded log-in to your ExpressionEngine control panel and navigate to the ‘Admin’ tab and then ‘Utilities’ and ‘Import Utilities’. We’re going to use the ‘Movable Type Import Utility’.

Complete all the fields on the import screen, your file path should be something like ‘../txpexport.txt’. Everything here should be pretty obvious, I just made sure I un-ticked the ‘Create members from commenters?’ option but obviously you might want to do things differently.

I’d suggest you do a few dry runs first of all with a small export from your Textpattern install to verify that everything is working as expected. I did an export of 10 entries from Textpattern initially just to test and then deleted all the entries and categories before performing my final import.

Ok so we have all our articles imported now but we’re not quite done yet. We need to set up a ‘File Upload’ location for our Textpattern Images. I decided to just use the default ‘Main Upload Directory’ which is already configured in ExpressionEngine.

I downloaded all my image assets from my Textpattern image upload folder and uploaded them all to my ExpressionEngine image upload folder. Now in my case the file paths are different (though you could always mimic the folder location which Textpattern uses in ExpressionEngine. If like me you didn’t you can quickly and easily do a find and replace on all your article image file paths.

Navigate to ‘Admin’ and then ‘Utilities’ and select ‘Find and Replace’. In my case I entered ‘/images/’ in the ‘Search for this text’ field and ‘/images/uploads/’ in the ‘replace with this text’ field. Select the entry field that you want to affect and the click submit.

All of your article entries should now include any inline images or media. Next we’ll be looking at how to deal with Textpattern ‘links’ and ‘file assets’.

During a bit of a forum tennis match almost 3 years back(!) Jon Hicks and I managed to refine an export method which had been used for Textpattern previously to incorporate clean Textile and entry comments. I’ve summarised the steps you will need to take and the code you will need to use in your Textpattern templates below.

Before you start you will need to install a couple of Textpattern plug-ins to ensure that we can get our data out in just the right format.

First is a Textpattern plug-in called msv_show_article_field which is written by Martin Švihla. This plug-in allows us to return the Textile formatted content for the articles instead of the HTML equivalent. This means that our articles will maintain their nice clean Textile formatting once imported into ExpressionEngine. Bonus!

Next is a plug-in called glx_thiscomment which is written by Johan Nilsson. This plug-in allows us to pull out the plain text name value for comments rather than the name wrapped in a ‘href’ linking to the comment authors website URL or email (the default behavior for the built in Textpattern comment tag). This is essential if we want to maintain article comments.

Now create 2 new Textpattern forms, one called ‘export’ and one called ‘exportcomments’. Add the following code to your ‘export’ form:

TITLE: <txp:title /> AUTHOR: <txp:author /> DATE: <txp:posted format="%m/%d/%G %I:%M:%S %p" /> PRIMARY CATEGORY: <txp:category1 /> CATEGORY: <txp:category2 /> <txp:php>echo "-----"."\n";</txp:php> BODY: <txp:msv_show_article_field name="Body" /> <txp:php>echo "-----"."\n";</txp:php> <txp:if_excerpt> EXCERPT:<txp:msv_show_article_field name="Excerpt" /></txp:if_excerpt> <txp:php>echo "-----"."\n";</txp:php> <txp:if_comments> <txp:comments form="exportcomments" break="" /> </txp:if_comments> <txp:php>echo "--------"."\n";</txp:php>

…and the following code to your ‘exportcomments’ form:

COMMENT: AUTHOR: <txp:glx_thiscomment key="name" /> EMAIL: <txp:comment_email /> URL: <txp:comment_web /> DATE: <txp:posted format="%m/%d/%G %I:%M:%S %p" /> <txp:message /> -----

Finally we need to call our ‘export’ form from a page template. Create a new page template called export and add the following code:

<txp:article_custom section="name-of-your-txp-section-here" form="export" limit="500" offset="0" />

Obviously you will need to tweak the parameters in your page template to suit the number of blog entries you have and the section from which you wish to export entries.

With all of the above done we should now be able to visit the public URL for this page template in our web browser (http://yourdomainname.com/export/) and see the output. I had over 400 entries to export so the page took a while to load. Once fully loaded view source and save a copy to a plain text file on your local machine (txpexport.txt for example).

I know I promised to cover how we import this data into ExpressionEngine but I’ve been rambling on for a while now so I’ll leave that until my next post.

First step quite obviously is to install ExpressionEngine Core (The free version of the CMS). I won’t explain how to do this, it’s dead easy and there are a ton of useful resources out there for you to look at if you’ve never used EE before.

First thing to do after you’ve completed the install is to modify the default custom field group for the default weblog to match the fields which you have in Textpattern. Textpattern has a ‘Body’ and ‘Excerpt’ field so you could simply rename the default ‘extended’ field if you want to feel at home.

As we’re migrating from Textpattern all our posts that we will be importing will be formatted with Textile or XHTML so we’re going to need to mimic that environment in ExpressionEngine. To do so we’ll need to install a handy little 3rd party plug-in called ‘Textile’! You can download the Textile Plug-in from the ExpressionEngine website. Once installed you will need to log-in to your ExpressionEngine control panel again and change the default formatting for the custom fields (body and excerpt) to use ‘Textile’ rather than XHTML. Don’t worry if some of your Textpattern blog posts have XHTML in them, Textile will still render these just right.

Finally, before we move on to exporting our blog entries from Textpattern we need to install a module that will allow us to more easily upload and manage files as we are used to doing so with the Textpattern ‘Files’ tab. The nearest equivalent that I have found over the years is the Low File Manager Module. It doesn’t provide download counts but it does pretty much everything else you could want and ties in beautifully with the ExpressionEngine File Upload preference settings.

Next we’ll be looking at how to export all our blog entries from Textpattern and pull them into ExpressionEngine.

So, this is the first of a number of posts which will explain the how, why when and what in as much detail as I can muster. If you’re looking to do the same then perhaps you’d like to follow me…

http://ee.nathanpitman.com

Update: Step 1, Step 2, Step 3, Step 4, Step 5