Comments on: Module Manager Update, now on Google Code!

By: Jason Williams

Jason Williams — Sat, 05 Mar 2011 12: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

By: Colin Mollenhour

Colin Mollenhour — Thu, 03 Mar 2011 01: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!

By: Franklin Strube

Franklin Strube — Wed, 02 Mar 2011 13: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/...

By: Colin Mollenhour

Colin Mollenhour — Wed, 02 Mar 2011 01: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.

By: Jason Williams

Jason Williams — Tue, 01 Mar 2011 22: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.

By: Jason Williams

Jason Williams — Wed, 19 Jan 2011 16: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.

By: Colin Mollenhour

Colin Mollenhour — Mon, 17 Jan 2011 20: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.

By: Jason Williams

Jason Williams — Mon, 17 Jan 2011 15: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.

By: Colin Mollenhour

Colin Mollenhour — Tue, 04 Jan 2011 21:01:15 +0000

Yes, that is correct, 1.4.2 requires a modification be made for modman
to work due to the new template "security".. See more info here:
http://www.magentocommerce.com...

By: john k

john k — Tue, 04 Jan 2011 04:11:01 +0000

Have you tried this in Magento 1.4.2 (or in my case EE 1.9.1.1)?

I found I had to hack the core “template.php” file because it was no longer allowing template files to be included if it was in symlink outside of the actual “design” directory.