product features not displayed after 1.3?

[Beeta]

I recently updated to 1.3 and I noticed that all the products are not displaying product features in the backend.
(I'm not 100% this happened after 1.3 update)

I can see product values in the DB and in the front end.

edit1: For example the screenshot below you can see what happened after I saved the item simply changing the quantity, and the same happen also if I try to set a value in the feature too!

Previusly the features was set:

id_feature	id_product	id_feature_value
8	289	somevalue
10	289	somevalue
11	289	somevalue
12	289	somevalue
13	289	somevalue
14	289	somevalue

After saving a item the features in the DB are ALL resetted to value 1 even if some of them was not set before:

		edit2: this issue is similar but not identical to this old issue: https://www.prestashop.com/forums/topic/252700-product-features-suddenly-missing-please-help/ edit3: right now I'm spinning a new instance loading a snepshot "pre-1.3" to be sure that the issue come up with the upgrade. edit4: in the mean time I noticed another thing, before trying to set a features value from the backhand the feature page is like this: once I try to set a value change like this:

Edited December 8, 2021 by Beeta
added information

[datakick]

There you go.

9 hours ago, Beeta said:

WOW!! I was sure to have only the ones from Panda Theme and instead I have many unknown overrides!!

As far I remember I don't added "manual" ovverrides, any idea on what happended?
Excluding the Panda Theme ones what can I do to see to what these ovverrides belong to?

There you go. Looks like you have copied AdminProductsController.php to override/controllers/admin directory sometimes in the past, modified it slightly, and forgot about it.

I suggest you delete this file.

You should also investigate what it was that you modified, but I don't see many changes in the file.

[veganline]

I had this just now.
Oddly, they showed in a different browser, at least at first.
On the far right of the catalog screen - maybe off the screen - is a search button.
If you search for anything, an orange "reset" button should appear under the button. Press the reset and with luck your backend stock appears.

Edited December 5, 2021 by veganline
screenshot attached

[Beeta]

Thank you @veganline but it’s not my issue. In each products page if I go to the features tab I’m seeing that are not set. But instead in the db I see them correctly.

 

[toplakd]

In my 1.3 everything is working 100%.

Do you use any overrides for admin section?

Have you checked Database schema With core updater?

[Beeta]

On 12/5/2021 at 2:25 PM, toplakd said:

In my 1.3 everything is working 100%.

Do you use any overrides for admin section?

Have you checked Database schema With core updater?

I checked the DB with coreupdater and I fix all the occurrence but three that I think are not related for this issue.

I didn't fixed because are labelled as dangeorus here's the screenshot:

The thing is that if I save any item the features got reset with value 1, even if I choose different value for the features.

 

I now added information in the original question post above.

Edited December 8, 2021 by Beeta

[datakick]

Overrides? 

[Beeta]

On 12/8/2021 at 10:01 PM, datakick said:

Overrides? 

WOW!! I was sure to have only the ones from Panda Theme and instead I have many unknown overrides!!

As far I remember I don't added "manual" ovverrides, any idea on what happended?
Excluding the Panda Theme ones what can I do to see to what these ovverrides belong to?

I also attathed the archive from my override directory.

thirtybees_overrides.tar.gz

[Beeta]

7 hours ago, datakick said:

There you go.

There you go. Looks like you have copied AdminProductsController.php to override/controllers/admin directory sometimes in the past, modified it slightly, and forgot about it.

I suggest you delete this file.

You should also investigate what it was that you modified, but I don't see many changes in the file.

I took a look and I think I modified with this:

The thing is that now in 1.3 that mod is included in the AdminProductsController.php core file and dind't figured out until now.

So the solution is as you said delete that override file.