Jump to content
Boost up your community

All Activity

This stream auto-updates

  1. Earlier
  2. In this tutorial we will create a simple feature plan. In this plan you can hold your steps to improve and extend your community features. The community members can visit the plan and see what is planned, coming soon or already implemented. This can improve engagement as they see that you actively work on new community.
  3. V0RT3X

    Final

    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.
  4. V0RT3X

    The CSS

    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
  5. 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
  6. 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
  7. 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
  8. 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
  9. V0RT3X

    The Basics

    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.
  10. With this tutorial we will create a simple but efficient bug tracker for reporting bugs etc., similar to the one IPS itself uses HERE for the 4.5 beta. The result will look like on the following screenshot, so everything will be a bit more stylish and above all more clearly arranged. Unnecessary information has been left out and important ones have been highlighted. Notes on this tutorial You have already learned the basics in other tutorials like the one for the recipe database. To avoid repeating ourselves all the time, we will link directly there for these steps and con
  11. We have already included some CSS classes in the templates. And now we can add the CSS styles to the page. Create and assign CSS file In your AdminCP go to Pages -> Page management -> Templates and click on New. Choose Add CSS file. Name it docs and add it to the existing group CSS. If we had more than one CSS file, it might be useful to create a new group at this point. Add the following CSS to docs.css: To include this CSS in the page for the database, go to Pages -> Page Management -> Pagein your AdminCP and open the page with the documentation for editing
  12. Now we are ready to create a block (plugin) that we will use as side menu. The side menu displays categories and the pages hierarchically. This block is created in AdminCP and we are going to use a custom template for it. Block with page menu In your AdminCP go to Pages -> Page management -> Blocks and click on Create new block. Click on Next. On the tab Details enter the name for the block and template key docs_side_menu. In the tab Feed Configuration set the following: You define here the number of records in the block. In earlier versions of I
  13. Now it is time to create templates for the database. In your AdminCP go to Pages -> Page management -> Templates. Click on New and select Add Database Template. Enter Docs in the Name field and select Record listing in Template Type. Assign the template to our database Documentation. A new template set Docs will be created. It contains several template bits for the listing of the records. Let's add another set of template bits to it. It will handle displaying the records in the database. Execute exactly the same steps as in the previous step (see screenshot above), except
  14. To avoid the navigation block be to heavy, we can optionally create a field that contains a short version of the page title. An example for the long title of the page can be "General introduction to databases with Pages". This page title is too long for the left navigation. It would be nicer if we could output a shorter version here, for example "Introduction". Create field for short version In AdminCP go to Pages -> Documentation -> Fields and click on Create new. Fill out the form on the tab General Options as shown below: Note that the field is set as not required
  15. In the introduction to this tutorial we have mentioned that we will limit categories to a two-tier hierarchy. This will keep the page navigation smart and user-friendly. For testing purposes you should now create some categories. In AdminCP go to Pages -> Documentation -> Categoriesand create some main categories or subcategories. An example I will work is shown below: You can either delete and rename the default category Records, which was automatically created with the database. Just edit it. Create at least one additional main category (in my example Development
  16. 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
  17. In this tutorial we build a documentation section à la IPS help guides. We will not build the documentation exactly the same, however you can customize, extend or adapt it to your needs at any time once you have understood the basic structure. The database for the documentation uses the categories to divide it into the larger sections. A kind of chapter. In each chapter (category) there are several pages that are subordinated to the category. In the original IPS documentation, categories have a three-level hierarchy. I find it overloaded, confusing and difficult to navigate. Therefore we
  18. This way to monetize the community is very exclusive. The most websites out there do not have such a large number of email notifications sent out instantly. So, why not to offer the space to the companies/advertisers? To add a banner into notifications emails in your AdminCP go to System -> Site Promotion -> Advertisements and click on the tab Email Advertisements. Click on Create New and fill the form out. Be aware that right now there is no possibility to restrict email advertisements to certain group. Upon saving the form your test banner will be instantly added to all outgoing e
  19. Table of Contents Default advert locations in IPS Smaller versions for mobile Additional ad settings Invision Community has the basic internal advertising feature that will help you to place ads in default locations without any programming knowledge. The best way to start with ads is to try out some default advert placements with your admin account. This way you can see how and where the ads are placed. You can also test if the placement is annoying or the size of the banner is not appropriate. Let's start. Default advert locations in IPS In your AdminCP go to System
  20. Welcome to Invisionify.com! The aim of this community is to elaborate the idea of how to boost your community content and cash flow.
  1. Load more activity
×
×
  • Create New...