V0RT3X

That's all for it now, your bugtracker is finished and we hope that your users won't have to use it too often 😉 You could of course add a filter function to the overview page, the status field is prepared accordingly and how this works has already been explained in the recipe database. If something doesn'twork, or you have any other questions, we are happy to help you in the support forum.

For the status field we have already defined several different values, but they all look the same at the moment. Especially with a bug tracker, the status of an error message should be immediately visible, for example with an alarm red for critical errors, green for fixed errors, and so on. Now we do all this in one washup with CSS. This is not only much easier and more elegant, the old font color tag is also no longer supported under modern HTML5. Now I have to say that it's actually the idea of IPS that you create your own CSS files for your pages (the Release Notes Tutorial explai

Since we want to use our own view, we naturally need our own templates. You can also simply display the user-defined fields automatically at fixed positions, but that is exactly what we are NOT doing here. So now we create our own set for the listing and the record, we already prepared the field on the last page. To do this, go to AdminCP and select Pages -> Page Management -> Templates -> New. Now we add two new database templates: Name: bugtracker_display -> Record Name: bugtracker_listing -> Record Listing Now you should see two new template gr

After you have specified the selection options on the last page, we only need to define how we want them to appear in the listing and detail view of the bugs. This is done via the Display options tab and looks like this ... Show in listing template = Yes Listing View Format = Custom Listing Custom Format {{if $formValue}} {{$items=explode(',',$formValue);}} {{foreach $items as $item}} {{if $item=="bugtracker_found"}} <span class='ipsBadge_large ipsBadge ipsBadge_style1'>{lang="$item"}</span> {{elseif $item=="bugtracker_fixed"}} <span class='ipsBadge_larg

The user, or later the staff member, should be able to assign a processing status to each error and to change it. For this purpose, we have created a select box on the last page, which we will now fill with information, which looks like this in the AdminCP ... Now it is important that you insert all keys and values exactly as I list them here ... bugtracker_found Bug bugtracker_fixed Fixed bugtracker_cant_reproduce Can't reproduce bugtracker_in_progress In progress bugtracker_answer Waiting for reply bugtracker_no_bug Not a bug Of course you can work with your own values

For this database we actually only need 3 fields. The title for the message, the content and the status. How to add custom fields has already been explained in the Documentation database. So let's go directly to the settings ... 1. Title Title = Title Type = Text Template Key: bugtracker_title Leave the rest as it is. 2. Content Titel = Content Type = Editor Template Key: bugtracker_content The other settings are fine too. But you can adjust them a bit, for example by disabling attachments. 3. Status Title = Status Type = S

For this bug tracker you need a database for the bugs reported by the users and a page where this database is included. The steps you have to do can be found HERE ... Create a page Create database Add database to page These steps are identical, except that you simply use bug tracker etc. instead of documentation. We don't use categories this time, but work more with fields and content filtering. We will also modify the included templates for the look and add our own CSS.

We are going to create a database that contains categories and assign the key doc for the database. In your AdminCP go to Pages -> Contents -> Databases and click on Create new. On the tab Details check that the database use categories, otherwise you will not be able to create a menu block. The key of the database should be set to docs. Use default templates as shown in the screenshot below, we will change them later where necessary. On the next tab you set the language. This documentation consists of guides / pages, so we will use the word "guide" here, instead of entry