| # |
Dec 9th 2016, 15:03 |
 dereuromark |
most of the time it is however possible to map them to a !empty() compatible value in the view layer |
| # |
Dec 9th 2016, 15:03 |
dereuromark |
depends on the form data coming in |
| # |
Dec 9th 2016, 15:02 |
dereuromark |
when "no" or sth would be equals to empty |
| # |
Dec 9th 2016, 15:01 |
admad |
gtg |
| # |
Dec 9th 2016, 15:00 |
admad |
what are "custom empty values"? |
| # |
Dec 9th 2016, 14:59 |
dereuromark |
thats a limitation now that wasnt there before, but so far that seems to suffice in the cases I encountered |
| # |
Dec 9th 2016, 14:58 |
dereuromark |
It only works with !empty() values, not with custom empty values |
| # |
Dec 9th 2016, 14:57 |
admad |
so you never have `?foo=` if you use the Prg component |
| # |
Dec 9th 2016, 14:56 |
admad |
also the PRG component filters out keys with empty values from query string before redirecting anyway |
| # |
Dec 9th 2016, 14:55 |
admad |
there's "filterEmpty" |
| # |
Dec 9th 2016, 14:55 |
admad |
there's no "allowEmpty" option for filters |
| # |
Dec 9th 2016, 14:53 |
Neon1024 |
The ‘value’ type search, doesn’t seem to care about allowEmpty |
| # |
Dec 9th 2016, 14:53 |
Neon1024 |
I mean, I have ‘allowEmpty’ on my ‘brand’, but it’s still making it to the SQL as ‘Brand.slug’ = ‘’ |
| # |
Dec 9th 2016, 14:52 |
Neon1024 |
Right, so I can use a beforeFilter or similar to ditch the empty request data |
| # |
Dec 9th 2016, 14:49 |
admad |
Neon1024: https://github.com/FriendsOfCake/search/blob/master/src/Controller/Component/PrgComponent.php#L97 |
| # |
Dec 9th 2016, 14:49 |
hmic |
dont forget to rebake the table and entity classes (and forms probably) after changing it! |
| # |
Dec 9th 2016, 14:49 |
dereuromark |
all fields must be lowercase |
| # |
Dec 9th 2016, 14:48 |
dereuromark |
I bet you named your columns wrong in the DB |
| # |
Dec 9th 2016, 14:47 |
luv2quit |
Hello. I am a beginner. I am trying to get an item by id but i get this error msg: Error: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'Item.i_d' in 'where clause'. I don't know why it uses Item.i_d. It shold be Item.id |
| # |
Dec 9th 2016, 14:39 |
dereuromark |
not sure of that feature of mine ever got ported to the other search plugin :slightly_smiling_face: |
| # |
Dec 9th 2016, 14:37 |
Neon1024 |
In relation to this, https://github.com/CakeDC/search/blob/master/Docs/Documentation/Examples.md#default-values-to-allow-search-for-not-any-of-the-below |
| # |
Dec 9th 2016, 14:35 |
Neon1024 |
Is there a way to prevent empty GET form params being included in the url? |
| # |
Dec 9th 2016, 14:10 |
birdy247 |
cheers |
| # |
Dec 9th 2016, 14:07 |
hmic |
exactly |
| # |
Dec 9th 2016, 14:07 |
birdy247 |
Configure::write ? |
| # |
Dec 9th 2016, 14:06 |
hmic |
birdy247: sure. just do so in the action! |
| # |
Dec 9th 2016, 14:05 |
birdy247 |
i.e. I want to turn it on for one controller action |
| # |
Dec 9th 2016, 14:05 |
birdy247 |
Can i set Debug on a per controller action level? |
| # |
Dec 9th 2016, 13:41 |
iqu |
hmic: you are correct. thats the best solutions |
| # |
Dec 9th 2016, 13:41 |
hmic |
*fg* |
| # |
Dec 9th 2016, 13:40 |
iqu |
someone should write a proper and easy plugin for file upload with progress-bar support :) |
| # |
Dec 9th 2016, 13:40 |
hmic |
for the requested thing, you would only need a dedicated sequence table and overwrite the newEntity function, sounds easy to me... |
| # |
Dec 9th 2016, 13:40 |
iqu |
hmic: :D |
| # |
Dec 9th 2016, 13:39 |
hmic |
iqu, are you using created/modified fields in your tables? - this is as easy a behaviours get! :p |
| # |
Dec 9th 2016, 13:38 |
iqu |
i found behaviours complicated |
| # |
Dec 9th 2016, 13:38 |
hmic |
go check :p |
| # |
Dec 9th 2016, 13:38 |
hmic |
!awesome |
| # |
Dec 9th 2016, 13:38 |
hmic |
still quite some qork to implement i think - maybe one could write a behavior, maybe there is one already? |
| # |
Dec 9th 2016, 13:38 |
iqu |
hmic: that is right |
| # |
Dec 9th 2016, 13:37 |
hmic |
but the proper solution to the problem is using a sequence table! |
| # |
Dec 9th 2016, 13:37 |
iqu |
but seriously, as you said better to create one table with autoincrement |