Magento – Custom widget’s template doesn’t show up in the front-end

blockswidget

So I have a custom widget with block defined in module's config.xml:

<config>
 <modules>
    (...)
 </modules>

 <global>
    <blocks>
        <gwidgets>
            <class>Phil_Gwidgets_Block</class>
        </gwidgets>
    </blocks>
 (...)
 </global>
</config>

Block's file is under app/code/local/Phil/Gwidgets/Block/Slider.php

I believe this is where the problem starts. I insert the widget into Wysiwyg editor in back-and, refresh the front-end and it doesn't appear. I check system log and there's this error:

Warning: file_exists(): open_basedir restriction in effect. File(/usr/share/php5/Mage/Phil/Gwidgets/Block/Slider.php) is not within the allowed path(s): (/home/www/xyz/:/usr/bin/) in /home/www/xyz/html/app/code/core/Mage/Core/functions.php on line 145

So after setting up logging function in functions.php I've found out that these are the directories where autoloader attempts to find by block class:

/home/www/xyz/html/app/code/local/Mage/Phil/Gwidgets/Block/Slider.php
/home/www/xyz/html/app/code/community/Mage/Phil/Gwidgets/Block/Slider.php
/home/www/xyz/html/app/code/core/Mage/Phil/Gwidgets/Block/Slider.php
/home/www/xyz/html/lib/Mage/Phil/Gwidgets/Block/Slider.php
./Mage/Phil/Gwidgets/Block/Slider.php
/usr/share/php5/Mage/Phil/Gwidgets/Block/Slider.php

It nearly does it here:

/home/www/xyz/html/app/code/local/Mage/Phil/Gwidgets/Block/Slider.php

It would find it without '/Mage' in the path.

So the question is why Magento looks for Slider.php in ...local/Mage/... rather than ...local/....?

I'd appreciate any advice on how to fix this issue. 🙂

Best Answer

This problem appears because your php tries to access /usr/share/php5 directory but server does not allow that. Check permission of /usr/share/php5 directory.

Answering the question why this folder is in 'include_paths' - check your php.ini configuration and virtual host config maybe it is set there. Default value of include_paths is .:/usr/share/php:/usr/share/pear.

Related Solutions

Magento 1.8 Custom Block Module – How to Create

I find the whole XML thing difficult so I am sympathetic to your cause here.

It looks to me like there is a discrepancy with your class name and your block XML

class Crusader_CLHomePage_Block_Qwerty extends Mage_Core_Block_Template

and

    <block type="core/template" name="homepage" template="crusader/home.phtml">
        <block type="crusaderhome/qwerty" name="homeads" as="homeads" template="crusader/homeads.phtml" />
    </block>

Let's start with the block type and work backward. I think here I would expect to see something like

<block type="crusader_home/qwerty" ...

and that type would refer Magento to the class

Crusader_Home_Block_Qwerty extends Mage_Core_Block_Template

Continuing to work backward on this tack, the file app\code\local\Crusader\CLHomePage\etc\config.xml would need to be modified to something like

<global>
    <blocks>
        <crusader_home>
            <class>Crusader_Home_Block</class>
        </crusader_home>
    </blocks>
</global>

It points Magento to all classes starting 'Crusader_Home_Block_*'. And now I think you need to rename your module Crusader_Home instead of Crusader_CLHomePage and change the folder names accordingly...

AND / BUT I strongly recommend you change your module name. Only ever use one capital letter at the start of the module name not three and don't put capital letters in the middle of the name either.

You may want to look into some of the tools available for generating modules. I find them very useful for avoiding typing errors. I use this one by the very clever people at MGT Commerce (it has simplicity on its side) and this one is all-encompassing and an astonishing piece of coding by Silk Software.

***EDIT following comments below

Additionally based on the error log I think the problem is that Magento can't find your class file. So double-check the caches are refreshed or off, particularly XML cache, and that the compiler is off or re-enabled.

Magento – Content block not showing

The problem is resides in in you layout update xml file. You have your block defined like this.

<block type="w/yblock" name="yblock" template="z/yblock.phtml" before="-"/>

Here the template attribute is wrong. As per your template file name, it's value should beZ/Yblock.phtml instead of z/yblock.phtml. ie block attributes are case-sensitive.

The correct definition would be

<block type="w/yblock" name="yblock" template="Z/Yblock.phtml" before="-"/>

You can also resolve this problem by changing the file name to z/yblock.phtml.ie change the location of file like this : app/design/frontend/Mypackage/Mytheme/template/z/yblock.phtml

^{Note : Clear all cache after the changes made.}

Best Answer

Related Solutions

Magento 1.8 Custom Block Module – How to Create

Magento – Content block not showing

Related Topic