cURL extension required

25. 09. 2013 at 11:17

I’m installing OpenCart on a localhost WAMP server.

I came across an error at Step 2 of the Pre-Installation stage

opencart-installThe status for Extensions showed a red – against cURL.

After a bit of Google research several options were found.

One was to enable cURL extension by going to the php.ini file and removing the semi colon in front of the line


In my case that was already removed so the extension was supposedly enabled

Next check the the localhost index/menu page for loaded extensions.  I noticed that curl was not listed

After checking the page (accessed from localhost index/menu page) details of curl were missing

I then read that I may have the curl extension. Apparently you need the one to match your php install. So I checked my version of php (found on the localhost index/menu page) 5.4.3 and downloaded the equivalent Fixed curl extension from here:
Once unzipped the php_curl.dll file needs to be placed in the ext folder of php. C/wamp/bin/php/php5.4.3/ext

That worked and replaced the red error with the necessary green tick.

Logitech Duet – player not found

12. 09. 2013 at 10:53

Why not I can see it!!!!!!

Have you been struggling to connect your Logitech Media player to your network so you can play music from your computer on your hifi – I have too. No matter how much you search all you find is more and more people with the same problem and an endless stream of answers and you try all the suggested things and it still doesn’t connect? Yes me too.

A seven step switch off and on routine with a rest to factory default didn’t work

Changing WAP to WEP didn’t work

Rebooting Router didn’t work

Taking out controller battery and checking MAC no didn’t work

Setting Router to different settings didn’t work

Moving Router / controller / player didn’t work

Going back / or forward on the operating system didn’t work

So here’s the definite answer to get the Logitech DUET working.

1 Unplug the Logitech Reciever

2 Switch off the Logitech controller

3 Hold the controller in the left hand and place you right hand on your left shoulder

4 Raise your left leg and place your foot in a yoga position on you right knee

5 Do not lose balance!!!!

6 Close your eyes and think of a nice place

7 Stay in the position  for 23 minutes

8 hopefully when you switch back on and try to connect it will now work – it has as much chance as any of the other suggestions!!!!

9  If not, go and search some more forums for another solution feeling far more relaxed


Seriously Logitech really need to sort this out. I have a TV with an internet USB dongle. The Logitech player was picked up on that and I didn’t have to do anything. I can play music on my TV so why not on my HIFI?!!!

Illogitech! That’s why

There’s a saying RTFM (read the f***ing manual) And I would certainly advice that with this product. Most of what’s repeated in the forums is what’s already in the manual…and on one occasion doing what was suggested in there did get me back up and running, but the correct procedure doesn’t work every time.

double quotes replaced by backslash on mysql update

06. 09. 2013 at 23:01

I had a situation where I had to export a set of records from a MYSQL database on a live site into a copy database on a localhost site. After successfully making the export / import I found all the picture and url links on the WordPress posts broken. Closer inspection relieved that the import had replaced all the necessary double quotes around links, styles, etc had been replaced with backslashes.


If you’re in the same position there’s a quick remedy. the following myqsl statement will find and replace

copy it and change the italic parts to match your set up

UPDATE your table name SET your field name = replace(your field name, ‘\\’, ‘\”‘);


 appearing in WordPress posts following mysql database import

04. 09. 2013 at 15:08

If you experience the problem of an  appearing in seemingly random places throughout you WordPress posts following a database import you may be able to solved it like I did by commenting out the encoding line in your site’s wp-config file:

Search for

define(‘DB_CHARSET’, ‘utf8?);

and add // to the front:

// define(‘DB_CHARSET’, ‘utf8?);

This should make the Âs disappear.