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

TOPIC:

Using Filters with published / unpublished datas 18 Feb 2012 11:40 #1360

  • liubov
  • liubov's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
  • (=) 10 mn and it's ready!
  • Posts: 279
  • Thank you received: 36
Hello Admin,

In my jbreedm Project for j2.5, I have a data field 'Publish' at the end of each Table. Now, I try to add filters (backend side), to display only Published Items or Unpublished Items.

When I set the filter in the layout page, we can not drag and drop the publish field, becaude it's is not a foreigh key!

How can I do, what is the good method?

Thank you.

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

Re: Using Filters with published / unpublished datas 18 Feb 2012 12:19 #1363

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Not available yet.
Coding is now a piece of cake

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

Re: Using Filters with published / unpublished datas 20 Feb 2012 13:31 #1400

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Added !

You can now filter on a bool.
If you want to change 'True' and 'False' strings for 'published/unpublished', do it in the layout file.

Enjoy.


EDIT : If you want to see unpublished items in front-end, a filter will not do the job, because they can only reduce the existant query. In that case, please change your front-end model for that. (Have a look on the backend model of the same table)
Coding is now a piece of cake

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

Last edit: by admin.
  • Page:
  • 1
Time to create page: 0.077 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