Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
Filter by Issue Raised date - Macrotone Forum

Unknown Error 8192: KunenaControllerApplicationDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in libraries/kunena/controller/application/display.php on line 21


Unknown Error 8192: Automatic conversion of false to array is deprecated in libraries/kunena/route/route.php on line 437


Unknown Error 8192: ComponentKunenaControllerWidgetAnnouncementDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/widget/announcement/display.php on line 18


Unknown Error 8192: ComponentKunenaControllerTopicItemDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/topic/item/display.php on line 25


Unknown Error 8192: Automatic conversion of false to array is deprecated in libraries/kunena/forum/category/category.php on line 415


Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Date/Date.php on line 112

Unknown Error 8192: Automatic conversion of false to array is deprecated in libraries/kunena/bbcode/bbcode.php on line 107

Filter by Issue Raised date


Unknown Error 8192: ComponentKunenaControllerTopicItemActionsDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/topic/item/actions/display.php on line 23


Unknown Error 8192: ComponentKunenaControllerTopicPollDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/topic/poll/display.php on line 21


Unknown Error 8192: ComponentKunenaControllerTopicItemMessageDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/topic/item/message/display.php on line 23

7 years 9 months ago #1 by chimz
good day, thank you for this amazing component.
Please help me do this, I have a report which displays all issues on the front end and my boss would like to filter by the date the issue was created and not the date the issue was 'identified' as is at the moment.
How can i just tweak this current one so that the filter can work using the date when the issue was raised and not when it was identified.
Thanks in advance :)

Unknown Error 8192: ComponentKunenaControllerMessageItemActionsDisplay implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in components/com_kunena/controller/message/item/actions/display.php on line 25

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

7 years 9 months ago #2 by geoffc
Replied by geoffc on topic Filter by Issue Raised date
To most intents the 'identified date' and the 'created date' are usually the same (or very close), with the slight difference being when the issue was first recorded in the system. Most users usually report problems soon after then discover them, rather than wait days (or more) before the problem is reported, which is why they are usually very close, usually a matter of minutes or hours, rather than days or weeks.

That said, when the issue is saved there is a field named 'created_date' which is one of the 'audit' fields usually not shown in the front end report list, although it is a option to display them if required.

One can always click on the list column header and the issues would then display in increasing (or decreasing) order.

This does not however answer the filtering question. Filtering on the list is slightly more complex since we need to add the column name into the model file, to enable it to perform the sort, and also modify the displayed form to show the 'created_date' as a filtering field.

Depending upon your particular skill you could modify the itissueslist model and view to add the required filtering column to your installed version. Our next release (1.7) changes the front end list display to make use of a different display mechanism (Joomla searchtools) for the filters, mainly since they currently occupy so much screen space, given the number of possible filter fields different people request. I do not recall immediately whether the 'created date' is one of the 1.7 filtered fields so would need to take a closer look.

Regards
Geoff
The following user(s) said Thank You: chimz

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

7 years 9 months ago #3 by chimz
Replied by chimz on topic Filter by Issue Raised date
ok thanks...do you have the slightest idea when we could have v1.7? just a rough date or even the month :)

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

7 years 9 months ago #4 by geoffc
Replied by geoffc on topic Filter by Issue Raised date
It is always difficult to specify dates, mainly since they are subject to change as they are subject to other activities/problems being found. The 1.7 release has a number of major changes mainly for multi-lingual sites and some new requested features, all of which means more testing. We are also looking to relocate which will mean changing of our broadband suppliers which is likely to cause further problems which will have to be resolved. This will not impact our web site only how we access it.

For these reasons we expect 1.7. to be made available in the late August/September timeframe, but there are no guarantees.

PS The main problem with date filters is that they require two fields to enable specification of from and to values to display the records within the range. Just doubles the amount of coding.

Regards
Geoff

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

Time to create page: 0.142 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries