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
Resolved: Can't save issue in 1.2.0 - Page 2 - 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: 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


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


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

Resolved: Can't save issue in 1.2.0


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

11 years 8 months ago #7 by jr@omnipotent.com.au
All good now thanks Geoff.

FYI: I can still generate the error if there are no suitable assignees.

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

The topic has been locked.
11 years 8 months ago #8 by geoffc
That is not surprising, there has to be a default assignee for an issue, and the assignee has to be a 'staff' member. For a new installation it makes the Super User an assignee, which resolves the problem, but may not be appropriate in all cases. One of the configuration options is to make assignees staff members in the it_people table.

Since yours is an 'existing' installation it would not do that. I will look at adding some extra checks in the logic.

It you could confirm that ensuring you have 'staff' members defined as 'staff' and also that the 'default assignee' is one of those, resolves the problem we are almost fit to go.

Thinking more on the topic, I currently have the assigned to field defined such that it could be NULL, which is fine. I could lever this and therefore effectively leave the field empty for the save IF a default assignee is not specified. This would also have an added possibility to tailor a message to the administrator to assign someone to work the issue. Logically this is possibly a better solution rather than just assigning the default assignee, who may or may not have been set up correctly. I should also add in that check at the assignment time.

I will test that and if it works out well will send you an update zip file.

Edited by geoffc - 06.09.2012 09:14

Have made my changes and sent you a new zip file.

Let me know if you find any problems.
Thank you for your assistance in making Issue Tracker a better component.

Edited by geoffc - 06.09.2012 12:51

Regards
Geoff
The topic has been locked.
11 years 8 months ago #9 by itd-ah.de
I have the same problem, could you send me the 1.2.1 release, too?

Best regards
The topic has been locked.
11 years 8 months ago #10 by geoffc
I am awaiting the feed back from the original poster to ensure that they do not discover any other problems.

I am reasonably confident (otherwise I would not have sent the file) that it will get a clean bill of health.

That said I would then propose to make it available on the web site, either tomorrow or the following day.

For that reason I will hold off sending out any more early releases as it makes support more difficult.

If it doesn't work out that way I will willing send you a pre-release copy, but I am sure you understand my reasoning.

PS. Glad to see you managed to log into the site OK.

Slight delay in the planned release. Firstly since I am still awaiting the users feedback, and secondly (if you have been reading the forums you will understand) I have been investigating a few other raised problems that have been found. Expecting Monday or Tuesday now if all goes well.

Edited by geoffc - 08.09.2012 21:35

Sent original raiser an email requesting an update. If I do not hear I will assume that it is no longer a problem and release 1.2.1.

Edited by geoffc - 10.09.2012 16:37

User confirmed by email that fix worked.

Edited by geoffc - 11.09.2012 10:12

Regards
Geoff
The topic has been locked.
Time to create page: 0.114 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries