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
New install to 2.5.4 Issues - 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

New install to 2.5.4 Issues


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

12 years 1 month ago #7 by dajo
Line 95: // Check general edit permission first.
Line 96: if ($user->authorise('core.edit', $asset)) {
Line 97: $value->params->set('access-edit', true);
Line 98: }

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.

12 years 1 month ago #8 by dajo
Playing about with the file here, but commenting out line 97 makes the form work...

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

12 years 1 month ago #9 by geoffc
I had that error reported a few hours ago (in the last thread) although they didn't say it generated a 500 error message so I didn't connect the two.

In the module components/models/form.php there are two lines 87/88 which are currently commented out.

// $value->params = new JRegistry;
// $value->params->loadString($value->parameters);

Uncommenting these lines may well also resolve your problem, as an alternative to deleting line 97.

It never ceases to amaze me that things work well on one or two sites and then on a third for no apparent reason they fail. Hmmmm.

I am not sure what the implications are by removing that line at present, I will need to look into it further to be sure. Let me know if you find anything untoward.

Thank you once again for your feedback.

I hope you find the component useful.

Regards
Geoff

Edited by geoffc - 10.04.2012 21:52

Regards
Geoff

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

12 years 1 month ago #10 by dajo
Hi Geoff,

I have done as you have suggested, uncommented those two lines and uncommented line 97 (that I did myself), I'd prefer to follow your way rather than my random testing lol!

It works with those two lines uncommented so thank you for that.

My "new" problem, if a none logged in user attempts to log a new call they get a joomla error: 403 - You are not authorised to view this resource.

Ideally, I would prefer a message to appear saying login to submit a problem - is this possible?

My next task is to get captcha working too :)

Regards,
David

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

12 years 1 month ago #11 by geoffc

Unknown Error 8192: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in libraries/kunena/external/nbbc/src/BBCode.php on line 2115


Unknown Error 8192: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in libraries/kunena/external/nbbc/src/BBCode.php on line 2115


Unknown Error 8192: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in libraries/kunena/external/nbbc/src/BBCode.php on line 2022


Unknown Error 8192: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in libraries/kunena/external/nbbc/src/BBCode.php on line 2070

The 403 message is because you need to set the permissions to enable guest (or any other group to create. To do this go into the component options and pick the last 'Permissions' tab. Then for the 'public' set the create permission to allow. By default it is 'inherited'. This is described somewhere buried away in the documentation but may not be immediately obvious.

I haven't coded anything (yet) to display a message and they try to navigate to the form, if they are not logged in. I generally set the menu setting to only display the form for registered users so that it doesn't display for guest users. I will put it on the to-do list for a later version.

As an aside, one 'trick' that may be useful to you is to have the form displayed to the public but not necessarily visible to all. It still requires teh correct ACL permissions. For example you can from the Issue Tracker installed component admin 'Support' tab find a link to raise an Issue on my site directly. This link is not visible on my site at all. It is only accessible IF you happen to know the correct URL, which is encoded in the 'Support' tab screen. This way I know that only issues raised by people who have installed the component will (currently) raise issues. I achieved this by creating a 'hidden' menu with the 'Create an Issue' link as the only entry. The 'hidden' menu is NOT assigned to anything so is not visisble, but you can use the URL directly to get to the screen.

Setting up ReCaptcha is easy too. Assuming that you have a 'recaptcha' already set up with Google. [If not you can get one free from Google.]
1. Ensure that Joomla 2.5 is set up for ReCaptcha. Go into the plugins manager and ensure that ReCaptcha is enabled and enter your keys. There is a video
people.joomla.org/videos/adeelch/video/8...omla-25-website.html that explains it in more details. IF you have any problems let me know.
2. Then in the Issue Tracker component options there is a setting that enables it to automatically appear in the form. It uses the 'built in' Joomla recaptcha and doesn't require anything other than the links to the 'system' plugin. I don't generally use the recaptcha except for 'guest' users as I tend to trust registered users not to generate spam, which is reallty what I am trying to minimise.

Regards
Geoff

PS Thank you for confirming that uncommenting the two lines works. It was rather difficult for me to check since I have never seen the problem, which is why I left them commented out.

Edited by geoffc - 11.04.2012 10:06

Regards
Geoff

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

12 years 1 month ago #12 by Mcw_33
Hi, awesome extension from what I've been able to test and use.

Also having the same problem with "create a issue" the above did solve the issue as well.


But I'm also having a small problem underneath the form it has some info about Joomla. The picture will show what I mean.

1) imageshack.us/photo/my-images/405/issuer.png/

2) Also keen to know if in a future release/edit if the "create a issue" will be customizable?

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

Time to create page: 0.187 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries