Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

ORM Issue with Component Search Filter 17 May 2017 09:22 #15134

  • liubov
  • liubov's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
  • (=) 10 mn and it's ready!
  • Posts: 279
  • Thank you received: 36
I found a bug when using the component Search Filter in Backend (Build 3.0.10 & 3.1.5).

P: Jday Program
T: Les Conférences
L: Back / Les Conférences

In the SandBox, if you filter the collection (ex: "3.7"), the result impact the 2 Lists Filter values (both emptied).

last bug that i would like to correct before publishing the program for the Jday Users ...

Please Log in or Create an account to join the conversation.

Last edit: by liubov.

ORM Issue with Component Search Filter 17 May 2017 21:40 #15135

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
It is a context problem.

Gonna check that
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

ORM Issue with Component Search Filter 17 May 2017 22:39 #15136

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
But... you are not using ORM...

It was a problem in the model
classes/model/list.php
getUserStateFromRequest()

Very good catch.
Fixed.
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

ORM Issue with Component Search Filter 18 May 2017 08:14 #15138

  • liubov
  • liubov's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
  • (=) 10 mn and it's ready!
  • Posts: 279
  • Thank you received: 36
Ho yes I see, it's because i have also tested 3.0.10 yesterday ...
And I 've checked the bug was also present with this version.

But I promise that the download program is from the lastest Build... with great ORM Queries :) :) :)

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.082 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started