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: At first: WOW! - 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: At first: WOW!


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 1 month ago #7 by arthos
Replied by arthos on topic Re: At first: WOW!
sent :-)

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 1 month ago #8 by arthos
Replied by arthos on topic Re: At first: WOW!
GOT IT!

Ok, the problem is on the "People" section. I'll try to explain:
- If I try add an Issue assigning it to one of the "fake" people installed with sample data all goes right!

-I've added an admin user (via the People section) and it's almost done except for one filed... the "project". Because the project I've selected is not saved.

That's why.

Hoping this could help.


--- EDITED POST ----

Ok, another brick in the wall...

if the USER level is CEO I've got problem on assigning the project.
If the USER level is "LEAD", I can assign project with no problems!

Edited by arthos - 27.03.2013 18:55
The topic has been locked.
11 years 1 month ago #9 by geoffc
Replied by geoffc on topic Re: At first: WOW!
There is a component option to set a default 'identified by person' which is used if they are not specifically chosen (or logged in). If logged in on the front end their user details should be picked up.
On the back end since it is usually an admin that is opening an issue it can be set to anyone, and the component default is used if not specified.

The compnent default is the 'specified Anonymous' user that should have been created in the installation. This explains why when you assigned one of the 'sample people' the save worked.

Not sure I understand the 'project' comment. If not specified the 'Unspecified Project' is used (or should be: there is a known problem in some cases with this in 1.3.0). This was one of the projects that were missing.

If a person has a default 'specified project' there is some logic to make use of that instead.

Regards
Geoff
The topic has been locked.
11 years 1 month ago #10 by geoffc
Replied by geoffc on topic Re: At first: WOW!
This 'project' setting is described in the docs (and FAQ). The CEO and Manager do not have an 'assigned project' since they do not usually (in my experience) work on a specific project, but rather 'supervise' many projects, hence the field is redundant as far as they are concerned.

They are usually 'too busy' to raise and answer issues by the same logic.

Your experience may be different of course. :-)

Regards
Geoff
The topic has been locked.
11 years 1 month ago #11 by geoffc
Replied by geoffc on topic Re: At first: WOW!
Have had a look at the system information and can't see anything there to cause any concern. The only specific component version that I haven't tested is the MySQL version but I do not think that is a cause.

I wil carry out a few more install tests to see if I can force the problem, but as it is restricted to the default table entries it may be possible to add some additional code checks as a fall back even if I fail to replicate it. I will add these into the next release, which will probably be 1.3.1.

There are a few known minor problems in 1.3.0 and one 'major' which is 'deleting projects' for which there is an already posted fix available.
See issue ADCNR5KM7L - Problem deleting projects. for details.

Regards
Geoff
The topic has been locked.
11 years 1 month ago #12 by arthos
Replied by arthos on topic Re: At first: WOW!
Many thanks for your support.

I've got a solution: Installing IT something goes wrong with the "Thread stack overrun" on MySQL.

Now we have upgrated the "thread_stack", and reinstalled the component.
All the tables are well poulated and seems to all working perfectly.

Thanks guys.
The topic has been locked.
Time to create page: 0.121 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries