New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serious date filter issues #192
Comments
I can confirm 4, adding as a comment that it only takes in mind the first date a trob said AND it filters like this: "Return all the the records that has their date element SMALLER or EQUAL THAN the first day of the url" Can also confirm 6 and 7 |
just updated from github and noticed that it now works in a different way!Now the filtering is made like: "Return all the the records that has their date element SMALLER or EQUAL THAN the SECOND date of the url" !!! |
We're working on the date filtering. I think some things got fixed in commits over the last 24 hours or so, I'm continuing to test the issues raised here. |
Uups, now date_time is always in SQLformat (list view, form/detail view) and date selector has vanished |
ive changed things so that url filters now have to be in mySQL format. This makes things a lot more consistent with the fact we submit dates in a mySQL format. I tested all filters and things seem to work ok for me, Which browser were you using for the vanished date selector and where did it vanish from (list filter view or the form view)? |
strange.just updated from github and it works exactly as I say in my previous comment here. Also,the date in the url is in list format(form is recording to database). |
Sorry, ignore my last post; The reason is a prefilter issue: using a date element |
So, if the URL should contain the SQL format we have to use {element_raw} in the jump page URL? This looks a lot better, but there are still some issues with the time: As I don't set a time I think it should be 00:00:00 but any date is stored in the DB with the actual time (which you can see shortly during save when it's displaying the date in SQL format) So, if I've inserted a row this afternoon with a date 07-03-2012 it's stored in DB as 2012-03-07 16:23:33 Now (21:30) I select 07-03-2012 in the search form, the generated URL is ...2012-03-07 21:30:24 and the row is not found. So to handle only dates without time I have to set all date_time elements (in list and searchform) to Some more remarks: if "Time selector"=yes {element_raw} inserts e.g. 2012-03-10 00:00:00__,00:00:00__ , appending a additional time string (and breaking all date filtering with error 500: DateTime::__construct() [datetime.--construct]: Failed to parse time string (2012-03-10 00:00:00,00:00) at position 20 (0): Double time specification) |
hi I couldn't replicate the last issue where if "Time selector"=yes {element_raw} inserts e.g. 2012-03-10 00:00:00,00:00:00. Can you check that my other changes havent fixed that and if they haven't can you provide me with more info on testing that one? thx |
Form not recording to DB, date element list+form format = %d-%m-%Y, time selector=yes Cache cleared still this issue: with time selector {element_raw} inserts e.g. without time selector it's ok |
I can confirm that using a form that RECORDS to database(not a good thing cause every search is recorded to the database) works ok now, with time selector = o When I tried to test it without recording to database i got this error: DateTime::__construct() [datetime.--construct]: Failed to parse time string (ΣΤΕΦΑΝΙΔΗΣ) at position 0 (�): Unexpected character I tried to search the table first with the common search and i got the above error... |
It's working on my site with Tested with a search form with only one date element (should be the same as enabeling list settings/filter for this element) You must clear your browser cache after updating. |
I'm kind of confused now where we are with all this. Is there an outstanding issue here still or not? If there is an issue can a video showing what you are doing be added please? |
I'm closing this ticket - if you have additional date filter issues please open a new ticket |
latest GitHub (2012-03-06 03:07:35), Joomla 2.5.1
all date elements have list and form format %d-%m-%Y, UTC, no time selector
!!Markdown is displaying 3 underscores as bold, so I changed to _ x _
selecting 16-02-2012 from date selector --> SQL = WHERE (
test
.date_time
BETWEEN '16-02-2012' AND '2012-02-16 23:59:59' )listid=1&test_x_date_time[value][]=18-02-2012&resetfilters=1&fabrikdebug=1
--> WHERE (
test
.date_time
BETWEEN '18-02-2012' AND '2012-02-18 23:59:59' )index.php?option=com_fabrik&view=list&listid=1&resetfilters=1&test_x_date_time[value][]=20-02-2012&test_x_date_time[value][]=22-02-2012&test_x_date_time[condition]=BETWEEN&fabrikdebug=1
--->WHERE (
test
.date_time
BETWEEN '20-02-2012' AND '2012-02-20 23:59:59' )jump page = index.php?option=com_fabrik&view=list&listid=1&test_x_date_time[value][]={_x_date_time}&resetfilters=1&fabrikdebug=1
is redirecting to
listid=1&test_x_date_time[value][]=2012-03-27 23:31:06&resetfilters=1&fabrikdebug=1
index.php?option=com_fabrik&view=list&listid=1&test_x_date_time[value][]={datummit_x_date_time}&resetfilters=1&fabrikdebug=1
is redirecting to
listid=1&test_x_date_time[value][]=01-03-2012&resetfilters=1&fabrikdebug=1
Date element range filter is ok:
selecting 18-02-2012 and 21-02-2012 via date selector
--> SQL = WHERE (
test
.date_time
BETWEEN '2012-02-18 00:00:00' AND '2012-02-21 23:59:59' )The text was updated successfully, but these errors were encountered: