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

TOPIC:

[FAQ] Filters Not Displayed properly - have you changed FK table names? 28 Sep 2013 05:05 #11209

  • BTB300
  • BTB300's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Posts: 415
  • Thank you received: 132
Similar, but not the same... last nights build 27/9
anyone noticed filter bricks missing on front end views -- but they were there on recent builds?

Firstly:
have you changed the fk table name? and do you have it in a filter or two or three... perhaps?

SYMPTOMS:
This appeared to me to look like a component wide issue - issue was on many collection layouts
- I am thinking i made some major changes to the fk-table names which upset the builder (unsure)
- no amount of regeneration and download would change the outcome
- in the builder the combos are still in displayed correctly in the filter brick
- trash the filter replace the combos still apparently no change
- A standard default grid is displayed (limit - direction - sort) with no additional filters

in the meantime... checked another template folder or two
- Checked Template html file, checked component forked file --> no overrides found
- full regeneration, download, uninstalation and reinstall,
- in the downloaded component additional filters not generated as can be seen below
             <div>

			<!-- BRICK : filters -->
			<div class="pull-right">
				<?php echo $this->filters['limit']->input;?>
			</div>
			<div class="pull-right">
				<?php echo $this->filters['directionTable']->input;?>
			</div>
			<div class="pull-right">
				<?php echo $this->filters['sortTable']->input;?>
			</div>
			<div class="clearfix"></div>

		</div>

SOLUTION:
TRASH THE FILTER BRICK!!! and Rebuild the filters from scratch - I think I hear admin :cheer: and saying how many times have i told you that :whistle:

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

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