PrestaSharp icon indicating copy to clipboard operation
PrestaSharp copied to clipboard

Category.position changes when updated

Open RCallejo2 opened this issue 9 years ago • 7 comments

Hi everybody, First of all, congratullations to all team for this interface you are developing. It would have been impossible for me to achieve my goals without this unvaluable tool and support.

A couple of questions: 1.- When updating a Category, Category position goes to the end of the list even when forzing value position. I would like to maintain the same position. Is it possible?

2.- I am interested in using LoggerLibrary. I know that Eduardo is the leader/author of this library. Can I have any example of how to implement an instance of it?

Thanks in advance.

RCallejo2 avatar Aug 11 '15 09:08 RCallejo2

Hello @RCallejo2 First of all, thanks to you for using PrestaSharp.

  1. Could you paste the xml request and the xml response after update the category?
  2. I´ll try to make a sample of LoggerLibrary. Regards.

EduLeonPavon avatar Aug 11 '15 10:08 EduLeonPavon

Hi Eduardo,

  1. I would do it If I knew how to do it. Could you give me some guidelines?

Thank you

RCallejo2 avatar Aug 11 '15 17:08 RCallejo2

Hello @RCallejo2 You´ll have to set a breakpoint in Bukimedia.PrestaSharp.Factories.RestSharpFactory.cs line 38. Look inside 'Request' and 'response' content. Regards.

EduLeonPavon avatar Aug 12 '15 11:08 EduLeonPavon

Sorry Edu. I do not find the way to export xml content from watch window. I am using VS2013. Could you tell me how to do it? Thanks a lot.

RCallejo2 avatar Aug 14 '15 17:08 RCallejo2

See the screenshot: image

las3r avatar Oct 01 '15 07:10 las3r

Hi friends. In Prestashop 1.7 i have the same problem. When i update a category i lost the position.

There are a solution? Thanks :-)

IcuScc avatar May 24 '18 17:05 IcuScc

Hi friends. In Prestashop 1.7 i have the same problem. When i update a category i lost the position.

There are a solution? Thanks :-)

This is a bug in Presta 1.7.5 (not PrestaSharp). Update to 1.7.6, it is fixed.

johndoe1395 avatar Jul 17 '19 00:07 johndoe1395