I recently had an unexpected part 3 to this tale the other day, when the display went. Again. But this time, different symptoms. This time, the backlight went. Oh sh*t, replacing LCD panels isn’t exactly cheap, and since the backlight diffusers and CCFL’s are fused to the back of the LCD panel itself, there was no way of replacing the individual unit.
Continue reading “Compaq CQ60 Display Issues – The Unexpected Part 3” »
I installed a copy of Magento 1.6.1.0 on a dev site I setup to do some testing with Varnish with (more on that later). However, in the requirement to be able to get to Magento using 2 different URL’s, I stumbled across this quite annoying bug.
a:5:{i:0;s:67:"Illegal scheme supplied, only alphanumeric characters are permitted";i:1;s:729:"#0 /home/dan/workspace/magento1610/app/code/core/Mage/Core/Model/Store.php(712): Zend_Uri::factory('{{base_url}}')
#1 /home/dan/workspace/magento1610/app/code/core/Mage/Core/Controller/Varien/Front.php(313): Mage_Core_Model_Store->isCurrentlySecure()
#2 /home/dan/workspace/magento1610/app/code/core/Mage/Core/Controller/Varien/Front.php(161): Mage_Core_Controller_Varien_Front->_checkBaseUrl(Object(Mage_Core_Controller_Request_Http))
#3 /home/dan/workspace/magento1610/app/code/core/Mage/Core/Model/App.php(349): Mage_Core_Controller_Varien_Front->dispatch()
#4 /home/dan/workspace/magento1610/app/Mage.php(640): Mage_Core_Model_App->run(Array)
#5 /home/dan/workspace/magento1610/index.php(80): Mage::run('', 'store')
#6 {main}";s:3:"url";s:85:"/index.php/admin/system_config/edit/section/web/key/41c8c3d3f4bcb72e3c267ae0b73333d7/";s:11:"script_name";s:10:"/index.php";s:4:"skin";s:7:"default";} |
Bug reports on Magento’s site here, here, here and here. Not being patient enough for Varien to fix it, I developed a small extension which resolves the problem. It’s available to download below.
Put the tarball in the Magento webroot and extract. After you install this extension, you’ll need to empty the cache manually (if it was enabled). I assume if you’re reading this, then your Magento installation is broken. To do this, simply remove the contents of var/cache in Magento’s webroot.
When you re-visit your Magento’s front or backend, the problem should vanish.
BTS_1610Fix.tar.gz (md5: 8316468f4e179cf2f512edaaf62a12db)Updated 9th January 2012: It apparent that, attempting to login before applying this update with {{base_url}} set screws up the admin login cookies somehow. When you apply this patch, you’ll probably need to empty out your chosen browser’s cookie jar before attempting to login. You can tell if you need to or not by trying to login, and Magento coming back to you with a login screen, with no failed login message.
Updated 12th January 2012: Magento 1.6.2.0 was released today. I can confirm that this problem still exists and has not yet been fixed (despite what the developers have written on one of the bug reports).
Updated 25th April 2012: I can confirm that this problem has been resolved in the latest 1.7.0.0 version, released 24th April 2012.
So in my previous post relating to this, I’d sent the machine back twice to HP to be repaired. The first visit gained a new motherboard and CPU. The second visit gained a new LCD assembly. But still the fault persisted. It sort of worked alright-ish for around a week or so, but then gave up the ghost completely. Sometimes the backlight would come on but no picture. Having had enough of it at this point, I phoned HP technical support a third time, claiming to them it would be my last call before phoning their Customer Complaints department.
So last Wednesday (July 14th 2010), it got picked up again, and was delivered back to me yesterday (Monday July 19th 2010). What did the service report say this time? I hear you ask.. “LCD cable replaced”… Are you serious? All this for a f*cking piece of wire? However annoyed I was at what their resolution was this time, so far it’s behaved exactly as it should. Resolved? Dare I say it this time? Yes…
So, third time lucky. In the meantime, I’ve found that the CQ60 isn’t on sale ANYWHERE anymore. It’s been deprecated and replaced with it’s mate, the CQ61. Casandra has one. There’s some key changes to the chassis and port placement on the unit. The power connector is on the opposite side to the CQ60. I assume that the Graphics, CPU and Power circuitry all the same corner of the board causes somewhat of a problem. I dunno. Either way..
So lately I acquired a (almost) new Compaq CQ60 laptop from the missus as she got a new one from the government (*sigh*). Anyway, we got this laptop about 6 months ago back in November ’09. When setting it up, I noticed the internal screen would take a while to switch on. I never thought anything of it as it was a first boot, then the screen came on and everything was happy. The troubles I had setting it up only become evident after more recent events. Just before she gave it up to me, opening the screen would result in a almost-white screen, one of them ‘pictures’ that show up when the LCD controller is goosed. It’s was very ‘wet’, drippy almost. But resetting the machine and the picture would come back to normal – weird.