The front end screens are not as extensive since there are not as many required. There are two ways in which the front end screens can be reached. Prior to release 1.3.0 a menu item was required for each screen and these will be described first.
Menu accessed screens
Each of the following can be configured as menu items. The first of these is the user ‘Create an Entry’. This has be opened up to registered or un-registered users. By default it is only registered users who may raise an issue and it is this screen that is displayed below. Un-registered users are presented with an additional entry box requesting user name, email address, an optional web site address and the Captcha box to complete. These details will be added to the issue progress details when the issue is saved to the database.
Not all the screens are displayed in this section, but rather a representative sample.
In Issue Tracker 1.5 and earlier there was an optional section displayed to request for Joomla version and product version which was controlled by the component options. If specified they were/are added to the issue progress details when the issue is/was saved. In release 1.6 and above these are now part of a Custom Field Group (see the section Custom Fields later in this document), and controlled by the Custom Field Group published state. When entered the values are stored in with the other 'custom field' entries in with the issue details in the database record.
Note | |
---|---|
For a guest user to be able to view the creation screen it is necessary to set the appropriate options for the public. The figure below illustrates the setting to enable creation of issues. Without this setting a 403 error message is displayed. The display of the project selection in the Raise issues form is controlled by a menu option for the 'Create an issue' item. The default is to display the project selection. |
Alternatively if it is not required that the public user should be able to raise issues, change the setting on the menu item to ‘registered’ (or what ever your desired ACL setting is) so that it does not apply to the public.
The ‘product details’ fields shown above are controlled by a component option and not necessarily displayed depending upon the option choice.
Included above is the options introduction text. Leave the option text blank of you do not want it displayed.
If the guest user is permitted to raise issues then the following panel is also displayed to enable capture of the user's details. These are also stored in the progress field for the record within the database.
If Captcha is configured then the display above is displayed. The captcha is the default one supplied with Joomla! 2.5, and can be configured with the usual configuration options. If Joomla 3.4 is in use then it is possible to use version 2 of the Google captcha and this would be reflected in the captcha image displayed in the form.