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
Changing Status Field and Remove others from form - 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

Changing Status Field and Remove others from form


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

9 years 1 month ago #1 by agouriet

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

Hi,

Wonder if I could have a little guidance.

I have just installed your component but need to make some alterations, namley to the 'add an issue' field.

The form is far too long and has far too much to be added from an 'end user' just trying to report a problem. Here are some of the things I would like to achieve:

1) Summary - At the moment there is WYSIWYG editor in the summary field and what I really wanted is a single text box that a line can be added into. I have seen that this was raised on another ticket on the forum but there was never really a resolution posted. How can I achieve this?

This is part of the solution which someone was told to change within the itissues.xml file. There was mention that another file; com_issuetracker/views/form/view.html.php that needed changes made to them but no information was provided as to what needed to be changed to where.

<field name="issue_description" type="textarea"
label="COM_ISSUETRACKER_FIELD_ISSUE_DESCRIPTION_LABEL"
description="COM_ISSUETRACKER_FIELD_ISSUE_DESCRIPTION_DESC"
size="2000" rows="10" cols="50"
class="inputbox textarea-span"
required="true" />

2) There are a number of other fields and sections that I wanted to hide. Both the 'issue resolution' and the 'issue status' isnt really needed for a creation of a new issue. How can these be hidden?

Many Thanks :)

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.

9 years 1 month ago - 9 years 1 month ago #2 by geoffc
I need to know more about the 'user' opening an issue.

First there is a check for whether WYSIWYG is required for the front end create/edit issue. There is a component option for whether a 'normal' user is presented with the WYSIWG editor. Issue admin and staff members get WYSIWYG automatically.

Whether the status field is also an optional parameter setting.
Also a normal user, i.e NOT staff or issue admin will not see the issue resolution field at all.
Can you check the settings for the user raising the issue?

Regards
Geoff

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

9 years 1 month ago #3 by agouriet
OK, I have just set up a new 'registered' on joomla and then synced the users with issue tracker. I allocated the user 'customer status'. I then logged in and clicked on the 'create a new issue' link and the following message came up: 'Public access is restricted to the requested item. Please login or register first.'.. even though i am logged in.

I take it this is a permissions issue? Any ideas and then I can check the form as a user :/

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

9 years 1 month ago #4 by geoffc
This is one of the standard FAQ items, You need to assign the correct ACL settings for the 'registered' users to 'create' an issue, and also if you want 'public' users to create issues. There are also other ACL permissions you may or may not wish to set.

The users will automatically sync across when they register. You only need to do it manually if you delete some or wish to reset them.

Regards
Geoff

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

9 years 1 month ago #5 by agouriet
That brilliant, thanks.

Once logged in as a customer the available fields are much more user friendly.

Thanks for all your help

Andy :)

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

9 years 1 month ago #6 by geoffc
You are welcome.

To answer your initial question about the itissues.xml file and the views/form/view_html.php file. The first specifies the various fields and their default values. The latter is user to modify the settings for each of the different user types, i.e The text fields are made WYSIWYG for staff and issue admin etc.

The logic is basically that a 'normal' user can add a issue summary and a description, and also add additional information to an already existing issue that they are associated with. The issue admin and staff can also open issues but they can change virtually any of the fields, update progress, close an issue etc. These may want to open and immediately close an issue (after the event) to ensure that a record is maintained.

I will mark the question as resolved.

Regards
Geoff

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

Time to create page: 0.149 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries