Useful to develop a module to add fields?

[__fabrice]

Hi all,

I posted two messages that were left unanswered, here and here. We would say that it's too complicated ...

Is it possible in this case, to do a module that manages a date (field) in the management of extra shopping cart and orders.

This is just to manage a date in the order. Not the date of the order, but a date related to the product (eg a trip).

Thank you for your help.
Fabrice

[yodapt]

It is possible, but I think a hook would be more suitable than a module.

[__fabrice]

Hi,

Thanks, but can you explain the differences between a hook and a module, please. ?

Fabrice

[yodapt]

A hook is an overrider for the default system behaviour. In other words, it's changing the core functionallity of Prestashop.

A module is something that works kind of standalone, given the Prestashop API or basic funcionality.

Be aware that a hook, if not well done, would make it hard to upgrade Prestashop in the future.

[__fabrice]

ok, thank you to explain.

I my case; i don't think it's appropriate to create a module. I just want to add a field in the product table, a date field, that i could retreive in the shopping cart and in the order.

Regards,
Fabrice

[UK-Canuck-in-Paris]

Anyone solve this?

I think what is needed is the list of files and tables that need modified to add a new product field of type date.

Or the possibility of changing a current product field which is not being used from a text field to a date field and then changing the display name.

[Paul C]

In 1.4 you would override the Product class to add fields to it, for example. Then you get all the joy of the standard object facilities without the pain of hacking around with adding hooks or modules etc.

For example to add a mandatory "Title" field to use instead of radio buttons for gender you could do:

class Customer extends CustomerCore
{
 /** @var string Title */
 public         $title;

 public function __construct($id = NULL, $id_lang = NULL)
 {
   $this->fieldsRequired[] = 'title';

   parent::__construct();
 }

 public function getFields()
{
  parent::validateFields();

  $fields = parent::getFields();
  $fields['title'] = pSQL(Tools::strtoupper($this->title));

  return $fields;
}

}

You would then probably write some member functions to manipulate/query the value. Simple

Paul

[UK-Canuck-in-Paris]

Thank you! That sounds amazing. But... when is 1.4 official? I need to deploy it with the next week or two.

I am busy coding on 1.3.6 but these things about 1.4 sound like even starting from scratch it may save me more time and less hacks as you say.

[Paul C]

Well it will be ready when it's ready, so why not start working on it and contributing to the bug tracker and it will get there that little bit quicker

Paul