Yes, users can contribute content to Wiki+ through posts. When the "Show posts" option is enabled for a page, users can add their insights and information as posts below the main page content.
What are orphaned pages and how should I handle them?
Answer
Orphaned pages are pages that exist within the Wiki+ database but are not linked to the main tree structure. These pages are not accessible through the tree navigation but can still be reached through direct links or cross-linking.
Orphaned pages are not necessarily problematic. They can be intentional if you prefer to link pages using the wiki-style syntax instead of a rigid tree hierarchy. You have the flexibility to choose the linking method that best suits your content organization.
While Wiki+ shares similarities with traditional wikis, it provides two key distinctions:
Optional Post Contributions: Wiki+ allows users to contribute short snippets of information (posts) directly on pages, enriching the content without formally editing the page itself. This feature is optional and can be enabled or disabled as needed.
Optional Tree Structure: Unlike standard wikis that rely solely on cross-linking, Composr's Wiki+ offers the flexibility of organizing pages within a hierarchical tree structure. This structure can be used in conjunction with or as an alternative to cross-linking.
Wiki+ is a feature in Composr that allows you to create a collaborative, tree-structured database of information. It functions similarly to a traditional wiki but offers enhanced features such as post contributions, a hierarchical structure, and moderation capabilities.
Can I integrate a dedicated issue management system with Composr?
Answer
While Composr doesn't have a built-in issue tracker, a non-bundled addon (cms_homesite_tracker) provides an integrated, modified version of Mantis. Additionally, the Support Ticket system can function as a basic private issue tracker using features like Post Templates.
How can I restrict access to the support system to specific users?
Answer
Utilize Composr's page access permissions to control who can access the Support Ticket page. This ensures only authorized users can submit support requests.
You can also control permissions based on ticket type when adding or editing a ticket type. Make sure if you go this route that the Support Ticket page permissions are very liberal (e.g. allow anyone to access, or just restrict to guests if you will never allow guests to make tickets). Otherwise, some people cannot make tickets even if they have permission on the type.
How does Composr handle email integration for support?
Answer
Composr can integrate with email for ticket management, assuming certain requirements are met:
PHP IMAP extension installed.
Functional PHP mail command (local SMTP server or configured Windows SMTP settings).
Active system scheduler (Cron).
With email integration, users can submit tickets via email, and staff can reply through the system. Composr cleans up email text for ticket clarity and allows forwarding emails to the integrated address for efficient handling.
How does Composr implement the Model-View-Controller (MVC) pattern?
Answer
Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules.
View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View.
Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.
Can I translate my content into multiple languages?
Answer
Yes, Composr supports multi-language content. You can enable this feature by:
Installing multiple language packs: Make sure you have at least two language packs installed.
Enabling the Conversr multi-language option: Go to Admin Zone > Setup > Configuration > Site options > Internationalisation.
Running a Commandr command: Execute the necessary command to set up the database structure for multi-language content (unless you already enabled Support content translations when installing).
Once enabled, you can translate your content into different languages and allow visitors to choose their preferred language.
My language uses gendered descriptors. How can I handle this in Composr?
Answer
Composr offers solutions for languages with gendered descriptors:
Template editing: You can modify templates to use different language strings based on user gender. This involves adding Tempcode logic to dynamically select the appropriate string.
Custom Profile Fields: Create a Custom Profile Field for "Gender" and use it to conditionally display gendered language strings in templates.
These methods allow for flexible handling of gendered language variations.
Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface.
By translating language strings, you change the text displayed on your website without modifying the underlying code.
How do I translate the content on my Composr website?
Answer
Once you've installed a new language pack, you can translate existing content by:
Editing the content directly: Go to the specific content item (page, news post, etc.) and edit it in the new language.
Using the language editor: Access the language editor from Admin Zone > Style > Translate/rephrase Composr to modify language strings used on specific pages.
Note that some elements like forum names are not designed to be translated directly. Instead, you should create separate forums for each language.
What should I do after successfully importing data into Composr?
Answer
After importing, if all files like avatars, photos, and attachments have been copied to Composr's directories, you can remove the imported product's directory. However, it's advisable to keep the directory, database, and import session for a few weeks in case any data was not correctly imported and needs further attention. Importing is a complex process, so keeping backups and sources for a while is a good practice.
