X-Cart forums

[xgarb]

Following the example here:

http://kb.x-cart.com/display/XDD/Flexy+Guide

I have this in my template: {if:getWidth()} width="{getWidth()}" {end:}

I want to show width="{getWidth()" in my template only if getWidth has been set.


The method looks like this:

    public function getWidth()
    {
        return \XLite\Core\Config::getInstance()->Tienda->myWidget->data_width;
    }

where data_width is a user setting in the admin area of the widget. If this setting is left blank, I don't want the text in italics above to show.

I've tried return false and NULL and the text is still shown. Is my only option to use != or <> '' in the IF statement?

[totaltec]

Is it possible that the getWidth method is pulling from somewhere else?

If you are returning false, it seems that your code above should be working.

[cflsystems]

I think you need 2 functions - one to check if the width is set and another to return actual width. The if statement works with true/false values

{if:isWidthSet()} width="{getWidth()}" {end:}

    public function isWidthSet()
    {
        return !empty(\XLite\Core\Config::getInstance()->Tienda->myWidget->data_width);
    }

    public function getWidth()
    {
        return \XLite\Core\Config::getInstance()->Tienda->myWidget->data_width;
    }

[xgarb]

I must have been doing something wrong somewhere as now a simple function like..

    public function getWidth()
    {
        return \XLite\Core\Config::getInstance()->Tienda->myWidget->data_width;
    }

with

{if:getWidth()}width="{getWidth()}"{end:}

in the template is working perfectly.

If the option is left blank in the module settings then the whole line isn't shown.

I thought I might need something a little more complex like

    public function getWidth()
    {
        $dataWidth = \XLite\Core\Config::getInstance()->Tienda->myWidget->data_width;
	return !empty($dataWidth) ? $dataWidth : false;
    }

but it doesn't seem necessary.

[qualiteam]

For simple cases like this, when you need to check if a module setting is configured, a single method should be enough.

For more complex cases it is recommended to have the second method so that it could be extended and tweaked from another module (when needed).