What controller is used to display SHORT DESCRIPTION ?

[sooly]

Hello,

im trying to make some changes in short description but i can't find which files should i edit.

In long description its ProductController.php but i have no idea how short description is being processed.

Anyone has idea?

Thanks

[tdsoft]

It is field description_short in classes\Product.php

[sooly]

Thanks for help but thats probably not what im looking for.

In ProductController.php im able to use code for displaying product features:

if (isset($this->product)){
$features = $this->product->getFrontFeatures($this->context->language->id);
$vypis = $features[0]['name']; 
$this->product->description=str_replace("{FEATURE_VAR}","{$vypis}","{$this->product->description}");
}

but in Product.php this doesnt work.

 

[NemoPS]

Where are you doing it in product.php?

[sooly]

On 2/7/2019 at 2:39 PM, NemoPS said:

Where are you doing it in product.php?

In "public function validateField".

Should I place it anywhere else ?

[NemoPS]

Can you describe what you need that for?
That function is not the one you want to use, but the best one really depends on where and how you need the information to be retrieved/displayed

[sooly]

We have eshop with batteries. We have stored informations like capacity or voltage in features.

I would like to take these features and put them in short description so customer can see it.

[sooly]

On 2/13/2019 at 2:49 PM, NemoPS said:

Can you describe what you need that for?
That function is not the one you want to use, but the best one really depends on where and how you need the information to be retrieved/displayed

Would like to put features right as it is on picture .

[NemoPS]

You don't need anything extra, why not using the standard block prestashop has? You can style it to a table and just move it around product.tpl

[sooly]

We need it in short description because we are exporting XML to google merchant and we have short description blank. So we want to have product featrues there.

Any ideas ? 😕

[NemoPS]

I would re-think the strategy. Eventually what you can do is populate the xml on export by editing the module directly, grabbing the features and writing them to the description field it exports, only. That's how I would go about it.