X-Cart forums

[GlasPak]

So most of my module is working now (except my new database column data got erased when I upgraded my dev site from 5.2 to 5.3)

The only part that isn't working is

Creating interface for editing this field

Now we need to be able to specify value of this property on product details page in admin area. We decorate \XLite\View\Model\Product class and create <X-Cart>/classes/XLite/Module/Tony/ProductFieldDemo/View/Model/Product.php file with the following content: 

<?php
// vim: set ts=4 sw=4 sts=4 et:

namespace XLite\Module\Tony\ProductFieldDemo\View\Model;

class Product extends \XLite\View\Model\Product implements \XLite\Base\IDecorator
{
	public function __construct(array $params = array(), array $sections = array())
    {
        parent::__construct($params, $sections);

        $this->schemaDefault += array (
        	'testField' => array(
            	self::SCHEMA_CLASS    => 'XLite\View\FormField\Input\Text',
            	self::SCHEMA_LABEL    => 'Test field',
            	self::SCHEMA_REQUIRED => false,
            	),
        	);
    }
}
Such code will add a new field to the product details page in admin area. This field will be named Test field and its value will be saved into testField field of xc_products MySQL table. The FormField class that defines an input field in the interface is default \XLite\View\FormField\Input\Text one.

Note: see an example of creating model editing form with more detailed explanation here: Model editing page.

I tried using the kb for upgrading modules to 5.3 from 5.2 but it doesn't seem to work. Any help on the changes needed here?

[qualiteam]

\XLite\View\Model\Product is not used anymore since the 5.3.0 version.

You should look into decorating the following two classes:
- \XLite\View\FormModel\Product\Info - defines form fields (for examples search in the soruce code for defineFields() method and how it uses static::compose() to combine existing and custom fields into groups)
- \XLite\Model\DTO\Product\Info - translates model properties/methods to form fields and back (look into init() and populateTo() methods and how these use static::compose() and static::deCompose() methods when fields are to be grouped into lines).

You don't need compose() and deCompose() methods if your custom fields appear as new lines (you use these methods only when your custom fields should appear along with other field in a single line, next to each other).

[GlasPak]

Originally Posted by qualiteam

\XLite\View\Model\Product is not used anymore since the 5.3.0 version.

You should look into decorating the following two classes:
- \XLite\View\FormModel\Product\Info - defines form fields (for examples search in the soruce code for defineFields() method and how it uses static::compose() to combine existing and custom fields into groups)
- \XLite\Model\DTO\Product\Info - translates model properties/methods to form fields and back (look into init() and populateTo() methods and how these use static::compose() and static::deCompose() methods when fields are to be grouped into lines).

You don't need compose() and deCompose() methods if your custom fields appear as new lines (you use these methods only when your custom fields should appear along with other field in a single line, next to each other).

I am at a complete loss...

I have looked over the areas you mentioned and looked at other modules and this should be working

<?php
// vim: set ts=4 sw=4 sts=4 et:

/**
 * Copyright (c) 2011-present Qualiteam software Ltd. All rights reserved.
 * See https://www.x-cart.com/license-agreement.html for license details.
 */

namespace XLite\Module\EBLIEB\GlasPak\View\FormModel\Product;

class Info extends \XLite\View\FormModel\Product\Info implements \XLite\Base\IDecorator
{
    /**
     * @return array
     */
    protected function defineFields()
    {
         $schema = parent::defineFields();

         $schema = static::compose(
             $schema,
            [
                'PPCField'               => [
                    'label'       => static::t('Pieces Per Case'),
                    'required'    => false,
                     ],
                    'position'    => 900,
                ]
         );

        return $schema;
    }
}

But it isn't adding it to the self::SECTION_DEFAULT or anywhere for that matter...

[GlasPak]

Originally Posted by qualiteam

\XLite\View\Model\Product is not used anymore since the 5.3.0 version.

You should look into decorating the following two classes:
- \XLite\View\FormModel\Product\Info - defines form fields (for examples search in the soruce code for defineFields() method and how it uses static::compose() to combine existing and custom fields into groups)
- \XLite\Model\DTO\Product\Info - translates model properties/methods to form fields and back (look into init() and populateTo() methods and how these use static::compose() and static::deCompose() methods when fields are to be grouped into lines).

You don't need compose() and deCompose() methods if your custom fields appear as new lines (you use these methods only when your custom fields should appear along with other field in a single line, next to each other).

http://devs.x-cart.com/en/basics/adding_new_property_to_a_product/ - Is this KB ever going to be updated? Was told all of them would be updated by the time 5.3 went out of beta.


Nevermind.. After a week or so of headaches I finally got it working (can't figure out how to do it with compose but atleast it is working).

[qualiteam]

The mentioned article is for X-Cart 5.2.x only.
For X-Cart 5.3.x you should check this one: http://devs.x-cart.com/en/basics/adding_new_property_to_a_product/adding_product_property_via_formmodel_api.html

"Compose" methods are used to "group" multiple fields into a single line. For example, you want to add a custom field and display it to the right of the existing Price field. In this case you "compose" your custom field with the Price field.

If your custom field should be displayed alone on a new form line, you don't need "compose" methods.