My Technical Blog - Latest Comments

Re: Benchmarking Zend_Cache backends for Magento

Colin Mollenhour — Fri, 30 Dec 2011 17:08:40 -0000

Hi Sanjay, this sounds like an issue with the driver and corrupt cache records. Are
you using the phpredis (compiled) mode or the standalone mode? Please open an issue on the github project to continue discussion. -Thanks

Re: Benchmarking Zend_Cache backends for Magento

Sanjay — Fri, 30 Dec 2011 13:04:06 -0000

Hi Colin, a little bit of background first - our Magento installation is split into Admin and Frontend being on different servers. We installed your tool on the frontend and it works really good. The redis server had been setup on the frontend server, we then configured the Admin to talk to frontend Redis but when we access the admin url, we get the error "invalid server response: e_1>0Alt_Image", is there any direction you can recommend for solving this?

Cheers
Sanjay

Re: Benchmarking Zend_Cache backends for Magento

gwillem — Tue, 11 Oct 2011 20:18:09 -0000

Hi Colin, it looks like a promising tool, thanks for sharing! I'm really looking forward to your post about Redis as I want to convince my customers to switch over from memcache. Keep up the good work.

Re: Benchmarking Zend_Cache backends for Magento

Colin Mollenhour — Mon, 10 Oct 2011 19:42:30 -0000

Yes, absolutely.

Re: Benchmarking Zend_Cache backends for Magento

Anonim — Sat, 08 Oct 2011 12:33:37 -0000

Can your backend be used without magento? Like normal Zend_Cache backends ?

Re: About

Colin Mollenhour — Sat, 01 Oct 2011 17:17:12 -0000

Hi Justin. If you don't want to check third-party code into your repo then you can just check in a list of extension keys (extensions.txt) then use a shell command to make sure they are installed:

@shell \
cd $PROJECT; \
mkdir -f .installed \
for ext in `cat $MODULE/extensions.txt`; do \
if [ ! -f .installed/$ext ]; then
./pear install $ext && touch .installed/$ext; \
fi \
done

Re: About

Justin — Sat, 01 Oct 2011 16:55:49 -0000

Hi Collin, I'm looking forward to using Modman, which seems like a great utility. I just have a question about best practices when it comes to 3rd party Magento extensions. This must be a simple or obvious question as I haven't been able to find anyone addressing it online, but in a nutshell: is there a best practice for dealing with 3rd party extensions when developing a Magento store, using source control and modman? I'd rather not check 3rd party extensions in, so are they something that wouldn't even typically be handled by modman? Just install the extensions I want by hand in my production, staging and dev environments individually? Thanks for any thoughts you may have

Re: About

Colin Mollenhour — Sun, 11 Sep 2011 22:57:03 -0000

Re: About

Alex — Sun, 11 Sep 2011 18:51:37 -0000

Hi Collin,
I have a quick question about Magento config for Zend_Cache_Backend_Redis.
For APC cache, in case of multiple websites/per server you need to use '<prefix>..</prefix>' . Do you need to do anything like that if you are using Zend_Cache_Backend_Redis ?
Thank you!

Re: About

Colin Mollenhour — Fri, 26 Aug 2011 23:01:05 -0000

Yep: @colinmollenhour

----------------------------------------

Re: About

Vinai — Fri, 26 Aug 2011 17:39:23 -0000

Hi Collin, do you twitter?

Re: Hiding “Out of Stock” Items in Magento

Tanay Jha — Wed, 24 Aug 2011 00:19:05 -0000

Thanks a lot! After wasting almost 5 hours here and there I found this and it helped to get what I was looking for. I wanted to display the no. of in Stock products in front of each category and subcategory menu items.

Thanks again!

Re: About

Stefan Hållén — Sun, 29 May 2011 12:11:05 -0000

So this is probably totally the wrong place to ask this question, but how would one go about to execute a query like:
{ $or : [ { start : { $gt : 100}, start : { $lt : 200} }, { end : { $gt : 100}, end : { $lt : 200} } ] }
In the mongodb odm wrapper? :)

nevermind!

find(array(
'_calendar' => new MongoId($this->chosenCalendarId)))->find(array(
'$or' => array('start' => array('$gte' => $startTimestamp, '$lt' => $endTimestamp))))->find(array(
'$or' => array('end' => array('$gte' => $startTimestamp, '$lt' => $endTimestamp))));

Re: Yet Another “Hiding Out-Of-Stock Products” Update

magento themes — Thu, 14 Apr 2011 07:47:13 -0000

Bug fixing is a very important aspect in programming.It also caused several sleepless nights for me.Coding may be different i can get the idea.Thanks for sharing.

Re: About

Colin Mollenhour — Wed, 13 Apr 2011 16:16:20 -0000

The problems that come along with using hardlinks are that detecting and repairing situations where files were moved/renamed/deleted becomes very difficult. Also to uninstall a module becomes potentially much more problematic. I.e. with symlinks I can remove a module by deleting it and running modman repair (thanks to the easy detection of broken symlinks). Also other problems such as having the root of your site as a repository would cause weird repository conflicts, etc..

Re: About

Your Name — Wed, 13 Apr 2011 03:03:15 -0000

Hi Colin,

I notice in your modman script you have a facility for using hard links instead of soft links but it is "not recommended". Why is that? Was there a specific problem the hard links introduced?

It seems to me that hard links might even be a better option as it means this will work independent of whether FollowSymlinks is enabled or not.

Re: Module Manager Update, now on Google Code!

Jason Williams — Sat, 05 Mar 2011 02:57:22 -0000

Colin,
Thanks for the quick response. I now have it working with modman managing the symlink to my version Template.php which fixes the problem with Magento and sym links. Sweetly ironic. J

Re: Module Manager Update, now on Google Code!

Colin Mollenhour — Wed, 02 Mar 2011 15:40:42 -0000

Excellent! I was just looking at implementing bash completion for modman
a couple days ago but did not have any time to spare for it. Thanks for
sharing!

Re: Module Manager Update, now on Google Code!

Franklin Strube — Wed, 02 Mar 2011 03:37:29 -0000

Colin,

I've been using modman for a month or so now, and it has made my Magento workspace much cleaner. However, one thing that got me down was not having my Linux terminal auto-complete my modman commands.

The following bash_completion script will provide auto-completion functionality for modman. Just throw it in /etc/bash_completion.d/modman or append it to ~/.bash_completion and you are good to go.

http://www.franklinstrube.com/...

Re: Module Manager Update, now on Google Code!

Colin Mollenhour — Tue, 01 Mar 2011 15:40:01 -0000

Jason, Magento uses PHP's include path when loading class files. The
app/code/local and app/code/community both come before app/core/core in
the include path so you can symlink an edited Template.php to
app/code/local/Mage/Core/Block/Template.php and Magento will load your
copy instead of the original copy.

Re: Module Manager Update, now on Google Code!

Jason Williams — Tue, 01 Mar 2011 12:33:21 -0000

Hi Colin,

I could be being daft here (strong possibility as am sleep deprived by having very young baby at home) but how did you implement your override of Mage_Core_Block_Template class? In most cases this class is extended by other classes and as far as I can see Magento doesn't perform any overridden when a class is itself extended. I think I'm missing something simple here - any pointers would be much appreciated. Thanks.

Re: Module Manager Update, now on Google Code!

Jason Williams — Wed, 19 Jan 2011 06:03:46 -0000

Yes, I had read the support issue but you've reminded me to add a comment to support a better fix that this silly developer mode approach Varien are planning to take.

I have just hit that point where I need to add a simple override Module to fix the Template class as am just working with a new project which is the first (of many) that I plan to use modman.

Re: Hiding “Out of Stock” Items in Magento

Arne — Tue, 18 Jan 2011 09:12:30 -0000

works great, thanks!

Re: Module Manager Update, now on Google Code!

Colin Mollenhour — Mon, 17 Jan 2011 10:41:32 -0000

Jason, there is an issue reported to hopefully get this fixed in a
future release.
http://www.magentocommerce.com...
From what I can tell so far the "fix" requires developer mode which is
no fix at all. Please show your support for a better fix in the comments
on that issue.

Fortunately, overriding the Mage_Core_Block_Template class to remove the
rather lame security enhancement is quite easy.

Re: Module Manager Update, now on Google Code!

Jason Williams — Mon, 17 Jan 2011 05:09:35 -0000

Thanks Colin. I stumbled across the repair option a little while after I'd posted my comment. The only issue I see now is Magento's darn 1.4.2.0 security 'fix' update, which I've just discovered. Joy.