• main_content block: Allows you to feature individual entries from modules/content like news or articles.
• main_multi_content, main_cc_embed, main_gallery_embed, main_news blocks: Enable you to pull in and display multiple entries based on categories or other criteria.
• main_include_module block: Provides a powerful way to integrate any module screen directly into a Comcode page.

• Protection from hackers: Uploaded files are stored with obscured filenames, preventing direct access and bypassing of the download system. Additionally, an anti-leech feature (when enabled) prevents direct download links from being shared on other websites (this is done by requiring a session ID which is validated against the person / device accessing it and only provided when Composr presents the download links to you on the site).
• Basic security: Composr will not let anyone upload dangerous scripts (such as PHP files) which can be executed.
• Rootkit detection: The rootkit detection tool under yourbaseurl/rootkit_detection.php can help scan files for shell scripts and backdoors. Composr's Health Check can also do this regularly. Note this only offers very basic detection and will not work for obfuscated backdoors (you should use antivirus to scan for those).

• General: Private messages are often combined into private topics.
• phpBB: Usergroup configuration and HTML entities may require manual adjustments after import.
• vBulletin: Calendar recurrences, ratings (karma), and 'goes to coventry' are not imported perfectly. Attachments may need to be extracted directly from the live database due to potential corruption in SQL dumps.
• Simple Machine Forum: Banning features may not import perfectly due to differences in how Composr handles bans.

• Staff-only replies in the Support Ticket system enable private communication among support staff.
• Notifications for new tickets, replies, or feedback ensure timely responses.
• Blocks like main_contact_us provide a simplified front-end for ticket creation.
• Forum moderation tools help manage support discussions effectively.

Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs.
 

Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker.

For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations.

We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage.

We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

• PHP IMAP extension installed
• System scheduler (Cron) running
• IMAP-compatible mail server

• Mail server enforces SPF and DKIM for email validation
• Mail server limits email size to prevent abuse
• System scheduler runs frequently (e.g., every minute) so members get prompt updates

• News-Style Blocks: side_forum_news, main_forum_news, and bottom_forum_news display forum topics in a news format, ideal for forums used for news posting.
• Topic-Focused Block: main_forum_topics showcases recent topics from specific forums, allowing you to highlight active discussions or important announcements.

• Define purpose: Allow testers to add, assign, and track tests, with security and forum integration.
• Design database: Plan the necessary database tables and fields to store the module's data.
• Create module shell: Write the basic module structure based on standard Composr modules.
• Define screens: Identify the module's screens and code their corresponding functions.
• Utilize API functions: Use Composr's built-in API functions like create_table, add_privilege, and do_template to implement functionality.

• Direct reference by URL: Include the library's URL in your theme's HTML.
• Composr's JavaScript API: Use Composr's API for organized inclusion and potential future compatibility benefits.
• Manual integration: Directly include the library's code in appropriate template files.

• Forum Software: Invision Board, MyBB, phpBB, Simple Machine Forum, vBulletin
• Content Management Systems: WordPress
• Special Importers: HTML website importer, Composr merge (for merging another Composr site)

• Copy the EN folder: Create a new folder with the ISO code of your target language (e.g., FR for French).
• Replace the images: Replace the English images with translated versions.
• Ensure correct image paths: Update any references to these images in your templates or content to point to the translated versions.

• 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).

• Zones: Create separate sections under different URLs with their own pages and content.
• Redirects: Make modules appear in different zones without actually moving them.
• Categories & Virtual Roots: Organize content like galleries, downloads, and catalogs into sub-trees that appear as separate entities.
• Usergroups & Permissions: Group members into subcommunities and control their access to specific content.
• Themes: Customize the look of different zones.

• Notification Defaults: You can set default notification preferences for all members. You can enable or disable specific notifications and choose the delivery method (Admin Zone > Setup > Notification defaults).
• Notification Lock-down: You can force members to receive or prevent them from receiving certain notifications (Admin Zone > Setup > Notification lock-down). This allows you to enforce specific notification policies and manage email volume.

• Content type: Choose to search specific content types like news, forum posts, or Comcode pages.
• Author/Submitter: Search for content submitted by a specific member.
• Date: Limit your search to content submitted within a specific time frame.
• Category (for certain content types): Narrow down your search to specific categories within a content type.

• Browse and select available blocks.
• Configure the block parameters.
• Preview the block output.
• Generate the necessary Comcode to embed the block.

• Zone access permissions
• Page (or content entry) access permissions
• Catalogue access permissions
• Category access permissions

• Sign up for a PayPal Business Account.
• Enable "Auto Return" in PayPal and set the return URL to http://yourbaseurl/index.php?page=purchase
• Enable "Payment data transfer" in PayPal and copy the data transfer identifier for Composr.
• In Composr, go to Admin Zone > Setup > Configuration > eCommerce options > Payment gateway (PayPal-specific).
• Paste the data transfer identifier and save.

• TaxJar integration: Supports international taxation for many countries.
• TaxCloud integration: Supports complex USA taxation, including destination-based rules.
• EU digital goods tax: Handles EU-specific regulations for digital products.
• Custom tax rates: Define your own percentage-based tax rates.
• Tax hooks: Developers can extend tax functionality and implement additional tax providers.

• Monetary payments: Issue refunds through your payment gateway.
• Point payments: Manually refund points through the points system.
• Cancellations: Cancel purchases in the Admin Zone to allow repurchasing. Remember to manually undo any associated actions (e.g., removing name highlighting).

• Sales list management: Cancel purchases, view sales history, and manage refunds (Admin Zone > Audit > eCommerce > Sales list management).
• Charts: Generate profit/loss accounts and cash flow diagrams for specific periods (Admin Zone > Audit > eCommerce, and Admin Zone > Audit > Site statistics).
• Manual transactions: Record transactions outside of Composr for accurate accounting (Admin Zone > Audit > eCommerce > Manual transaction).

• Virtual Forums: Special forums like "Posts since last visit" and "Topics with unread posts" provide filtered views of recent activity.
• Read Status: Topics with unread posts are displayed in bold with a jump-to-first-unread link. You can manually mark topics or entire forums as read or unread.
• Notifications: You can enable email notifications for specific topics or forums, either manually or automatically based on your activity.

• Structure: Composr's forums follow a hierarchical structure. You can create forum groupings, forums, and sub-forums (and sub-sub-forums etc) in that order of hierarchy.
• Strategies: Avoid creating too many forums, which can dilute activity. Start with a few well-defined forums and expand as needed.
• Permissions: Use Composr's permission system to control access to forums and features. For example, you can create private staff forums.

• Control Result Visibility: Choose whether results are visible before voting.
• Require Topic Reply: Force users to reply to the topic before voting.
• Show Voter Identities: Optionally display which members voted for each option.
• Allow Vote Revocation: Let voters change their vote while the poll is open.
• Set Voting Close Time: Define a specific date or time for the poll to close.
• Restrict Selections: Limit the number of options voters can choose.
• Allow Guest Voting: Enable voting for unregistered users.
• Weight Votes by Points: Give more influential members greater voting power (requires the points addon).

• Forum View Access: Determine which usergroups can view each forum.
• Privilege Overrides: Grant or deny specific privileges (e.g., posting) to usergroups within a forum.
• Bypass Validation: Allow trusted members to post without moderation (or vice versa, require validation for certain usergroups).

• Email Tracking: Composr marks emails as read when processing posts. Marking an email unread will trigger re-processing.
• Log File: Create an empty file named data_custom/mail_integration.log to capture detailed log data for troubleshooting.

• Forum Groupings: Broad categories that contain forums.
• Forums: Contain topics related to a specific subject.
• Sub-forums: Forums nested under other forums, providing further categorization.
• Topics: Threads of conversation containing a series of posts.
• Posts: Individual messages within a topic.

• Regular Registration: Users can click on "join" links, agree to your rules, and fill out a registration form. They will then receive an activation email to confirm their email address (if enabled).
• Invites: You can restrict joining to invite-only. Existing members can send invites, and only those who receive an invite can register.
• Manual Addition: Administrators can manually create member accounts through the Admin Zone. This is useful for pre-joining members or handling issues with the regular registration process.
• Other Methods: Composr also supports automatic member joining through LDAP and HTTP authentication.

• Password Strength Setting: Administrators can set a minimum password strength requirement, forcing members to choose stronger passwords. Password strengths are calculated on a scale of 1-10 using algorithms that take into account letters (including case), numbers, symbols, repeat characters, use of dictionary words, and use of usernames / dates of birth / e-mail addresses.
• Forced Password Resets: Administrators can force specific members or all members to change their passwords upon next login, enhancing security in case of potential breaches.
• Expiring passwords: Administrators can require members to change their password after so many days.
• Encrypted CPFs: If the server has the OpenSSL PHP extension installed, specific CPFs (such as ones containing other passwords) can be encrypted to protect sensitive member data in case of a server compromise.

• main_rss block: Suitable for main content areas
• side_rss block: Designed for sidebars and smaller spaces

• Blog vs. Non-Blog Posts: Choose to display blog posts only, regular news posts only, or both.
• Category Filtering: Limit results to specific news categories.
• Double Filtering: Apply a second category filter for a two-level categorization system (useful for large sites).

• Default Menu: Generated automatically from the Sitemap, reflecting the structure of your content.
• Editable Menus: You can create and fully customize these menus, adding links to specific content or external websites.

• /pg/ (e.g., /pg/home)
• .htm (e.g., /home.htm)
• Simple unadorned URLs (e.g., /home)

• Improved user experience with more readable URLs.
• Potential SEO benefits, as some believe search engines favor cleaner URLs.
• Easier sharing on social media and other platforms.

• CAPTCHA: A visual or audio test that humans can easily pass but bots struggle with. This helps prevent automated spam submissions.
• Heuristics: If Composr thinks an action is spam based off of configurable criteria, it can either flag the content for validation, block the attempt, or ban the IP address outright.
• Public block lists: Composr can utilize the Stop Forum Spam system or other block list systems to identify and block known spammers based on IP addresses, usernames, and email addresses.
• Link posting restrictions: Disallowing links in member profiles for users with no posts and adding "nofollow" attributes to links discourages spammers seeking backlinks.
• Black hole fields: Hidden form fields that should remain empty. Bots often fill these in, allowing Composr to identify them.
• Project Honey Pot integration: A system that places hidden links on pages, attracting and identifying spam bots.
• Content/post reporting: Users can report spam, enabling staff to take action.
• Guest posting limitations: Restricting guest permissions raises the bar for spammers.
• Advanced techniques: Developer addons like "antispam_question" or probation systems provide additional layers of protection.

• Full backup: Backs up all files and folders within the Composr installation directory, including the database.
• Incremental backup: Backs up only new or changed files since the last backup, resulting in smaller backup files.
• Database backup only: Backs up only the database.

• Upload the extracted files to your webserver, overwriting the existing files.
• Run the included restore.php script in your browser. This script will restore the database from the restore_data.php file.

• Restore the initial full backup.
• Sequentially extract and overwrite files from each incremental backup over the restored full backup.
• The last extracted restore_data.php will contain the latest database state. Run restore.php to restore the final database version.

• Access the f_members table.
• Find the row corresponding to the user whose password needs to be reset.
• Edit the row, setting m_pass_hash_salted to the new password using MD5 encryption, clearing m_pass_salt, and setting m_password_compat_scheme to 'md5'.

• Obtain your IP address.
• Edit your _config.php file, setting $SITE_INFO['backdoor_ip'] to your IP address. This enables a temporary backdoor login for your IP address, bypassing security restrictions.
• Remove the backdoor entry after logging in and resetting the password through standard means.

• Browse tables: View and edit individual rows within database tables.
• Run SQL queries: Execute SQL commands directly for specific tasks.
• Repair corrupted tables: Access table repair functions.

• Dynamic content updates: Modifying page content without requiring a full page reload.
• User interface enhancements: Creating interactive elements like dropdown menus, image sliders, and form validation.
• Animations and visual effects: Adding visual appeal and engaging user experiences.
• Asynchronous communication: Fetching data from, or sending data to, servers in the background without disrupting user interaction.

• Virtual Machines: Use virtual machines to run different operating systems and test various Internet Explorer versions.
• Device Emulation: Use built-in device emulation features in browsers like Chrome to simulate mobile devices.
• Online Testing Services: Employ commercial online testing services like BrowserStack to access a wide range of browsers and devices hosted in the cloud.
• Real Devices: Conduct testing on physical mobile devices for a more realistic user experience.

• Automatic browser behavior: Browsers typically disable background images when printing.
• CSS print stylesheets: Composr utilizes CSS to define specific display rules for printed versions of pages, such as removing margins and hiding social media links.
• wide_print parameter: This parameter, activated through specific links or specifying it in the URL, further influences page layout for printing.

• Through the Admin Zone or Content Management Zone: Go to Admin Zone > Content > Calendar.
• Directly on the calendar: Click on a date box on the calendar view.
• Using the "Add Event" button on any calendar view.

• Use specific field types: Utilize dedicated field types for sensitive data like member IDs, usernames, emails, IP addresses, and passwords for efficient handling by the privacy system.
• Enable "May contain personal information": Mark fields that may contain personal information, enabling the privacy system to identify and handle such data during purging or downloading.

• Private Topics:
  • Start a private topic from a member's profile, by clicking "Whisper" on their post and selecting "Quote post to a new Private Topic with this member," or from your account by selecting "Start a Private Topic" and entering the desired username.
  • Participate in the topic just like a regular forum topic.
  • You will receive notifications for new posts in your private topics.
  • Topics can be moved to the "Trash" category or other categories of your choosing for organization.
• Inline Personal Posts (Whispers):
  • Send a private message within a public topic by clicking "Whisper" on a post and selecting "In-topic personal post to this member."
  • Whispers are visible only to the sender and recipient, and the whispered post is highlighted.
  • Receive notifications for new whispers.

• bin: Stores Commandr scripts.
• database: Provides access to the raw database.
• etc: Allows access to Composr configuration options.
• home or filedump: Provides access to the File/Media Library.
  • home contains the files in a special JSON format with metadata
  • filedump contains the raw files
• members: Lists registered members with their settings and user groups.
• raw or root: Provides access to the Composr installation directory.
  • raw contains the raw files without overrides, and modifying any file modifies them directly without automatic override handling
  • root contains the files with applicable overrides applied automatically, and Composr will automatically handle overrides and utilizing _custom directories when these files are modified
• var: Contains structured website resources and content.

• Mobile mode: You can design separate layouts and CSS styles specifically for mobile devices, which Composr automatically activates when a mobile user visits your site.
• Tempcode's 0 symbol: This symbol helps conditionally display content based on whether the user is on a mobile device or desktop.
• CSS media queries: By using media queries, you can target specific screen sizes and adjust styles accordingly, making your theme responsive.
• Viewport meta tag: This tag controls how the browser scales and displays the webpage on mobile devices, ensuring a properly sized and zoomable experience.

• Set up SPF records: SPF (Sender Policy Framework) helps verify that your server is authorized to send emails from your domain.
• Ask users to whitelist your email address: Encourage recipients to add your email address to their contacts list or "Safe Senders" list.
• Configure DKIM: DKIM (DomainKeys Identified Mail) adds a digital signature to your emails, increasing their legitimacy.
• Use a reputable email service provider: Consider using a third-party email service if you're struggling with email deliverability.

• Unsubscribe links: Newsletters include an unsubscribe link, allowing recipients to opt out of the newsletters.
• Global unsubscribe: All Composr emails include a link to a global unsubscribe page (data/unsubscribe.php), letting users unsubscribe from all site emails.

• NEWSLETTER_DEFAULT_FCOMCODE.txt: This template defines the default content and layout for newsletters.
• MAIL.tpl: This template controls the overall appearance of emails sent from Composr.
• Custom mail templates: You can create custom HTML templates for specific newsletters.

• The PHP IMAP extension enabled on your server.
• A dedicated folder on your email server to collect bounced emails.

• Blocks: The main_content block allows you to display specific items by content type and ID or randomize content from selected categories.
• Awards: Create awards for different content types and assign them to specific items. You can then use the main_awards block to display current award holders. Awards also integrate with points to credit points to award holders. And you can be reminded on the staff checklist to assign a new award every configurable amount of time.
• Advanced Embedding: For greater control, use the main_include_module block to embed entire module screens within other content.

• Countdowns: Use the main_countdown block to add countdowns to specific dates and times.
• Hit Counters: While generally considered outdated, you can use the main_count block to display hit counters for specific content.

• Filtercode is used for selecting content based on defined filters, such as field values, ratings, or keywords. It utilizes a syntax of comparisons, separated by commas, where each comparison specifies a field and a matching condition.
• Selectcode is a simpler syntax for specifying a list of IDs or categories to include or exclude from the results. It uses a comma-separated list of match-specifier tokens, such as individual IDs, ranges, or wildcard characters.

• Upload the Composr files to your web directory.
• Navigate to the install.php file in your web browser.
• Follow the on-screen instructions, providing the required information, such as database details and administrator credentials.
• After the installation is complete, delete the install.php file for security reasons.

• On the old server, ZIP the entire Composr directory.
• Download the ZIP file to your computer.
• Upload the ZIP file to the new server using SFTP/FTP.
• On the new server, unzip the file.

• On the old server, create an SQL dump of your database using the mysqldump command or phpMyAdmin.
• Download the SQL dump file.
• If your URL is changing, search and replace the old URL with the new one in the SQL dump file.
• Upload the SQL dump file to the new server.
• Restore the database on the new server using the mysql command or phpMyAdmin.

• File Permissions: After transferring files, ensure correct file permissions are set on the new server. You can use the fixperms.php script, the upgrader script, or manually adjust them.
• Configuration: If database settings are different on the new server, update the _config.php file or use the config_editor.php script to change the settings for both the site and forum databases.
• Base URL: If your URL has changed, update the base URL setting in the Installation Options editor (config_editor.php).
• Caches: Clear the block cache using the upgrader.php script.

• Download the language pack: You can download language packs from the Composr website.
• Install the language pack: Upload the downloaded language pack addon through Admin Zone > Structure > Addons > Import non-bundled addon(s).
• Change the default language: Go to http://yourbaseurl/config_editor.php and set the desired language.
• Update your profile: If you had a previous language set in your profile, update it to the new language.

• 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.

• Joining the translation team on Transifex: Translate language strings collaboratively with other volunteers.
• Becoming a language maintainer: Take responsibility for the translation and support of Composr in your native language.
• Reporting translation issues: If you encounter unclear, incorrect, or duplicated language strings, file bug reports.
• Providing feedback and suggestions: Share your thoughts on improving the translation process through feature suggestions.

• 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.

• data-tpl: Used with the $cms.behaviors.initializeTemplates function and PARAMS_JSON tempcode directive to bind JavaScript logic to HTML templates.
• data-view: Used with the $cms.behaviors.initializeViews function to associate JavaScript view classes (inheriting from $cms.View) with specific HTML elements.

• Content Optimization: Write high-quality, keyword-rich content using clear headings, relevant links, and descriptive image alt text.
• URL Monikers: Enable this feature to create human-readable URLs that incorporate keywords instead of numerical IDs.
• XML Sitemaps: Composr automatically generates and submits XML Sitemaps to major search engines, aiding them in discovering and indexing your content.
• robots.txt: This file allows you to control which parts of your site search engines can access and index. Composr provides a default robots.txt that can be customized as needed.

• Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options.
• Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section.
• Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.

• Check for duplicates: Make sure the bug hasn't already been reported.
• Report bugs individually: Each issue should be reported separately for better tracking and resolution.
• Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
• Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
• Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other

• Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
• Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

• Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
• Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
• Take backups before upgrading. This allows for easier recovery in case of problems.

• Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
• Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
• Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
• Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.

• Be specific and detailed. Identify particular issues and provide clear examples.
• Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
• Avoid vague statements. General comments like "it looks dated" are unhelpful.
• Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.

• Create a new project or open an existing one.
• Add a Prefix Header file (.pch) if you don't have one, following the provided instructions.
• Add required frameworks to your project's Build Phases.
• Add the CMS SDK to your project, then remove references to unwanted files.
• Set the header search path to the CMS SDK folder in build settings.
• Add a compiler option for the JsonKit library.
• Import CMS_SDK.h in your .pch file.

• Create a new project or open an existing one.
• Import CMS SDK into your workspace as an Android project.
• Ensure "Is Library" is checked in the CMS SDK's "Android" properties tab.
• Add CMS SDK as a dependent library in your project's properties.
• Clean and rebuild your project.

• Check Email Logs: View the email log (Admin Zone > Audit > E-mail queue/log) to see what notifications have been sent.
• Use the SU Feature: Impersonate a member using the SU feature (described in the "Testing access and privileges" tutorial) to view their notification settings and confirm they are set up correctly.
• Enable Carbon-copy Email: Configure a "Carbon-copy e-mail address" in the configuration settings to receive copies of all outgoing emails, including notifications. This helps you monitor email delivery.
• Verify System Scheduler: Ensure the system scheduler is configured correctly if members are not receiving digest emails.
• Check Digest Settings: Confirm that "Enable digest notifications" is enabled in the Messages configuration settings.
• Review "Safety listing limit": If a notification has too many categories, members might not see the full selection tree. Adjust the "Safety listing limit" in the configuration settings if necessary.

• $SITE_INFO['disable_smart_decaching'] = '1';
• $SITE_INFO['no_disk_sanity_checks'] = '1';
• $SITE_INFO['hardcode_common_module_zones'] = '1';
• $SITE_INFO['prefer_direct_code_call'] = '1';
• $SITE_INFO['charset'] = 'utf-8';
• $SITE_INFO['known_suexec'] = '1';
• $SITE_INFO['dev_mode'] = '0';
• $SITE_INFO['no_extra_logs'] = '1';
• $SITE_INFO['no_extra_bots'] = '1';
• $SITE_INFO['no_extra_closed_file'] = '1';
• $SITE_INFO['no_installer_checks'] = '1';
• $SITE_INFO['assume_full_mobile_support'] = '1';
• $SITE_INFO['no_extra_mobiles'] = '1';

• Configuring the CDN option in Composr with a comma-separated list of CDN domain names.
• Ensuring your files are mirrored on the CDN servers.
• Utilizing the CDN_FILTER directive and symbol to control what content is served via CDN.

• Joining the website: A welcome bonus for new members.
• Daily visits: Encourage regular engagement.
• Content interactions: Liking, rating, and submitting various forms of content.
• Forum participation: Posting and having posts validated.
• Chatroom activity: Reward active participation in chatrooms.
• Quizzes and polls: Encourage learning and engagement.
• Website recommendations: Reward referrals.
• Receiving points from other members: Facilitate community appreciation.
• Selling downloads: Monetize content creation.
• Birthdays: Offer a special bonus on their birthdays.

• Navigate to Admin Zone (or CMS Zone) > Content > Quizzes.
• Use the provided interface to define your quiz questions, answer options, and settings.
• You can manage quiz results and view participant responses under Admin Zone > Audit > Quizzes.

• Restrict access: Limit quiz participation to specific usergroups or newsletter subscribers.
• Shuffle content: Randomize question and answer order to make it harder to copy answers.
• Set time limits: Enforce quiz completion within a specified timeframe.
• Define open time ranges: Control when the quiz is accessible to participants.

• Multiple-choice and short answer questions: These are automatically marked based on your defined correct answers.
• Long answer questions: These require manual marking, resulting in a percentage range being displayed to the user until you assess their response.
• Unmarked questions: These questions are collected but don't contribute to the overall score, allowing you to include optional or non-scored elements.

• Using the search bar in the header: This is the simplest way to search. Just type your search term in the box and click the search button.
• Using the 'Search' module: This module offers more detailed search options. You can access it via the 'site:search' page-link (usually under About > Search in the default menu).
• From the Forum: Click the 'Search' button on the forum or use the contextual search box on the forum member bar. This will search within your current forum or topic.

• Use specific keywords: The more specific your keywords, the better your results.
• Use boolean operators: Use "+", "-", and quotation marks to refine your search.
• Optimize content titles and meta keywords: These fields are given priority during search, so make sure they accurately reflect your content.
• Consider enabling the fast custom index: Especially beneficial for large websites or frequent filtered searches.

• HTML Filtering: Configurable levels of filtering prevent malicious script injection.
• Content Security Policy (CSP): Restricts the sources from which scripts and other resources can be loaded.
• Input Sanitization: Data is sanitized before being processed to prevent malicious code execution.
• Output Encoding: Data displayed to users is properly encoded to prevent interpretation as active code.

• Choose a Secure Host: Opt for hosts that offer suEXEC and open_basedir for better account isolation.
• Test Security: Verify the host's security measures with the provided filesystem_browser.php script.
• Restrict _config.php: Remove world-writable permissions from _config.php after installation.

• XSS Attacks: By restricting inline scripts and limiting script sources.
• Data Injection Attacks: By controlling the allowed origins for data requests.
• Clickjacking: By specifying allowed framing sources.

• Private forums: Dedicated forums with restricted access enable staff to discuss site operations and coordinate activities. Composr installs a staff forum by default in Conversr.
• Conflict detection: When multiple staff members attempt to edit the same resource simultaneously, Composr displays warnings at the top to prevent accidental overwrites.
• Staff checklist & dashboard: The Admin Zone dashboard provides a shared checklist for task management, along with space for notes and links.
• Staff notifications and tickets system: Staff receive notifications about various site events, including support tickets from the "Contact Us" page, allowing for efficient issue handling.
• Content notes: Staff can embed notes within Comcode or use dedicated "staff notes" fields for various content types to share information and context.
• Validation and workflows: Content can be intentionally left unvalidated even by staff, enabling secondary checks before publishing. A dedicated workflows addon allows for complex approval processes with multiple stages involving different staff groups.

• Report links: "Report this" links embedded throughout the site enable users to flag content for review.
• Custom reporting interface: Forums offer a dedicated interface for reporting individual posts.
• Anonymous reporting: Logged-in users can choose to report content anonymously.
• Ticket-based management: Reports are automatically created as support tickets, facilitating staff collaboration and record-keeping.
• Comprehensive report details: Tickets include content title, type, ID, submitter information, an embedded rendering of the reported content, and the reporter's explanation.

• Genuine interest: Look for members passionate about the community and its goals.
• Available time: Ensure potential staff can dedicate sufficient time to fulfill their responsibilities.
• Relevant skills: Prioritize skills and experience aligned with the specific role requirements.
• Maturity and discipline: Seek individuals who demonstrate responsible behavior and commitment.
• Recruitment methods like directly approaching active community members or allowing the Composr points system (or the karma non-bundled addon) to identify dedicated contributors can be more effective than traditional advertising.

• Respect staff limitations: Avoid overwhelming staff with excessive workload or overly ambitious site expansions.
• Active involvement: Maintain active involvement in overseeing staff activities and ensuring their effective functioning.
• Open communication: Engage in regular communication, providing feedback, addressing concerns, and recognizing achievements.
• Foster teamwork: Encourage collaboration and information sharing among staff members.
• Lead by example: Ensure staff adhere to community rules and demonstrate expected behavior.
• Empowerment and trust: Grant sufficient freedom and control to enable staff to excel in their roles.

• Random tracking code: Choose a random tracking code from a set and activate it for the user session.
• Conditional output: Generate different content variations based on the active tracking code.

• PHP IMAP extension installed.
• Functional PHP mail command (local SMTP server or configured Windows SMTP settings).
• Active system scheduler (Cron).

• 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.

• Referencing them in the child-list of an existing page.
• Using the special Comcode syntax [[pagename]] to create inline links, which automatically generates new pages when accessed.
• Utilizing the "Edit tree" button visible on Wiki+ pages to add child pages directly.

• Integrity checker: The upgrader tool, accessible via http://yourbaseurl/upgrader.php, includes an integrity checker that identifies outdated or corrupted files.
• MySQL table repair: The Admin Zone > Tools > Cleanup tools provides access to MySQL table repair functionalities. Alternatively, use phpMyAdmin or your web host's database management tools for more direct control.
• Safe Mode: Access safe mode via the bookmarked link from the setup wizard or by adding &keep_safe_mode=1 to any website URL. This disables custom themes and caching, helping isolate problems caused by themes or custom code.

• 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.

Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated.

Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

That depends on several factors. Here are some pros and cons of each:

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.

• Blocks are functional units that generate dynamic content or provide specific features. They don't inherently have a visual form and their output can vary widely.
• Boxes are a visual design element in Composr, essentially containers that visually group content on a page and often with a title at the top.

• home (Welcome and Site zones): The default front pages for the respective zones.
• sitemap (Welcome zone): Displays the sitemap, typically generated automatically.
• _rules (Welcome zone): Outlines the site rules, also displayed during registration. The "rules" page (no underscore) is a wrapper for this page.
• privacy (Welcome zone): Provides privacy policy information. By default, this is generated automatically with Composr's privacy policy generator block.
• 404 (Welcome zone): The page shown for 404 errors (page not found) and includes a sitemap.
• help (Site zone): Contains general help information.
• userguide_comcode (Site zone): A basic guide to Comcode for users.

• Content Security Policy
• Session expiry time
• Password reset process
• Password expiry days
• Minimum password length and strength
• Login error secrecy
• IP strictness for sessions
• Cryptographic ratchet
• CAPTCHA usage
• Brute force threshold
• Audio CAPTCHA
• URL Monikers
• .htaccess restrictions on maintenance scripts
• Enquiry on new IP addresses

• Minimum: Very bare-bones informational-only sites
• Low: Sites which do not allow public registrations and do not use eCommerce but have content managed by different staff, and are not concerned with privacy or data
• Medium: Sites with social features / public accounts but do not use eCommerce.
• High: Sites which use eCommerce.
• Ultra High: Sites containing very sensitive data, such as but not limited to cybersecurity sites, government departments, banks, healthcare, etc.

• The script: http://yourbaseurl/config_editor.php
• The Admin Zone: Admin Zone > Setup > Configuration > Installation Options

• Generate a default theme and logo
• Set initial site options
• Remove predefined content and unnecessary addons
• Place initial blocks on your pages

• Uploading via web form (when adding a download in the Content Management Zone): This is the simplest method, where you attach the file directly when defining the download details. However, it's not suitable for large files and can be affected by unreliable internet connections.
• Uploading and referencing the URL: You can manually upload the file using FTP/SFTP/SCP and then provide the URL to the file in the 'Add download' form. While this is better for large files, it requires additional

• Batch adding from an FTP server: This allows staff to add multiple downloads from an FTP server in one go using FTP URLs. It's efficient for bulk uploads but requires separate addition of descriptions.
• Batch adding from a directory: Similar to the FTP method, staff can add downloads from a web server directory accessible by URL.
• File/media library (filedump): Webmasters can use any of the above methods to upload a file to uploads/filedump and then reference it in a download. This is especially handy if you are going to reference the file more than once on your site.

• Create a new container gallery (e.g., with codename "downloads").
• Change the "Create download galleries under" configuration option to your new gallery's codename.
• Use Commandr to move existing galleries to the new location.

• 32-bit PHP build: Files larger than 2GB are not supported.
• 64-bit PHP build: Files larger than 2GB are supported, but the file size will not be displayed.

• Usergroup subscriptions: Offer access to specific usergroups with recurring payments.
• Catalogue items: Physical or digital goods sold through the shopping cart and a special "products" catalogue.
• Orders: Collections of products purchased together.
• E-mail addresses: Sell personalized email addresses on your domain.
• Topic pinning: Allow users to pay to pin forum topics.
• Name highlighting: Offer highlighted usernames on the forum.
• Banners: Sell banner advertising space.
• Custom products: Define and sell any product or service you wish.
• Permission products: Sell access to specific permissions, such as download categories.
• Gambling: Allow users to wager points.
• Work: Represent invoiced services.
• Non-purchasable products: For accounting purposes (interest, tax, wages, other).

• Flat rate per order: Configure a fixed shipping cost for all orders.
• Weight-based calculation: Define shipping costs based on the order's total weight.
• Shippo integration: Get real-time shipping quotes from various carriers based on weight, dimensions, and destination.

• Regular Posts: Standard posts made by members within a topic.
• Quick Replies: Shorter replies made directly from the topic view.
• Anonymous Posts: Members can choose to post anonymously, appearing as a guest. Staff can track the actual user if needed.
• Emphasised posts: Posts made by staff (or marked by staff) which are highlighted to draw attention as they are important.
• Whispers: Private messages embedded within public topics, allowing for side conversations.
• Private Topic Posts: Private messages sent between specific members (e.g. an on-site "inbox").

• Advanced Polls: Blind polls, forcing or setting of default options, and point-weighting.
• Private Topics: More sophisticated than traditional private messages.
• Forum Introduction Questions: A flexible way to control access and encourage engagement (e.g. forum-specific rules or forum passwords).
• Cascading Topics: Pinned topics that appear in multiple forums.
• Integrated Moderation: Streamlined moderation tools within the forum interface.

• .jpg/.jpeg: Highly compressed, best for photos due to minimal noticeable quality loss.
• .png: Good compression with no quality loss, ideal if bandwidth isn't a concern.
• .gif: Limited to 256 colors and poor compression. Better alternatives are video or APNG.

• .mp4 (h.264 aac encoding): The recommended format, widely supported.
• .mov (h.264 aac encoding): Identical to .mp4.
• .webm: Supported natively in most browsers, but requires plugins for Internet Explorer/Microsoft Edge and Safari.

• Enforce specific requirements for membership (e.g., job role in a company forum).
• Categorize members based on their interests or affiliations (e.g., football players in a school forum).
• Display additional information on member profiles and forum posts.

• Visitor: Any one or device who visits the site but is not necessarily identified
• User: Any visitor who can be identified (e.g. has a session ID or tracked IP address)
• Guest: A user who is not logged in (in Conversr, they all share a special "Guest" ID / account)
• Member: A user who is logged in with a registered account on the website (they have a username and a member ID)
• Author: Specific to the authors addon, a profile of an entity (could be a member, individual, or even a company) who makes content for the site
• Subscriber: A user who receives newsletters from the site (they do not necessarily have to be a member)
• Submitter: A user who submitted content (usually a member, but could be a guest if the site is very open to submissions)
• Staff: A member who moderates any significant portion of the website
• Super-moderator: A staff member with global moderation capabilities
  • Moderator: Same as super-moderator but does not have those capabilities globally; they may only be able to moderate certain sections or content
• Super-administrator: A staff member with literally undeniable access to everything on the site
  • Administrator: Same as super-administrator but they might not have access to the most elevated of privileges such as accessing maintenance scripts

• title: The article title
• url: The article URL
• rss: The URL of your news RSS feed

• Wider audience reach: Your content becomes accessible to those using feed readers and aggregators.
• Content repurposing: Other websites can incorporate your feed, increasing visibility.
• Increased traffic: Users discovering your content in feeds may visit your website directly.
• Staying on top: Those who use your RSS feeds will see when you post new news articles.

• The original article includes a "trackback" link in its HTML.
• When another blogger writes an article referencing the original, their software uses the trackback link to inform the original site.
• Composr receives the trackback and displays a list of articles linking back to the original.

• FirePHP: This browser add-on allows you to view detailed logs of permission checks performed by Composr. By analyzing these logs, you can identify which checks are failing and adjust your settings accordingly.
• Permission Check Logging: Enable logging of failed permission checks to a file (data_custom/permission_checks.log). This provides a persistent record of permission issues that you can review and troubleshoot.

• Zones, Pages, and Categories: Control which usergroups can view specific zones, pages, and categories (permissions).
  • Admin Zone > Security > Permissions Tree Editor, or on the UI for the Zone / Page / Category.
• Global Privileges: Define permissions for actions like using advanced Comcode or bypassing the word filter, applicable across the entire site.
  • Admin Zone > Security > Global privileges
• Module/Page Overrides: Tailor privileges for particular content types by overriding them on the controlling module or page.
  • Admin Zone > Security > Permissions Tree Editor [> Content permissions]
• Category Overrides: Modify privileges for specific categories, allowing fine-grained control over actions within those categories.
  • Admin Zone > Security > Permissions Tree Editor
• Match-key Permissions: Implement ad-hoc access control based on specific match-keys, offering flexibility beyond traditional permission structures.
  • Admin Zone > Security > Match-key page restrictions

• Welcome Zone: The initial landing page, often used for login/signup.
• Site Zone: Your main website content, with features for viewing, submitting, editing, and deleting content on the member level.
• Admin Zone: For site administrators to manage the website.
• Content Management Zone: Where content is added, edited, and deleted, typically by site staff.
• Forum Zone (if using Conversr): Houses the forum section of your site.

• Generating menus.
• Creating the user-facing sitemap page.
• Generating the XML Sitemap for search engines.
• Providing a visual representation of your website structure in the Sitemap editor and Permissions tree editor.

• Enable Safe Mode: Use the safe mode link or the config editor (http://yourbaseurl/config_editor.php) to enable Safe Mode.
• Uninstall the problematic addon: Once in Safe Mode, navigate to the addon management section and uninstall the addon causing the issue.
• Disable Safe Mode: After resolving the problem, disable Safe Mode through the config editor.

• Permanent: These banners are always displayed as long as there is available space.
• Campaign: These banners have a limited number of impressions or clicks before they stop displaying. They can be associated with specific campaigns and can have their hits increased if needed.
• Default: These banners are displayed only when there are no permanent or campaign banners available to show.

• Images: Uploaded directly or via an image URL.
• Text: Textual banners, including support for "hot text" that dynamically displays banners based on keyword matches within the content.
• Frames: Banners embedded within frames using an iframe URL.
• Direct Code: Raw HTML or PHP code can be used to integrate banners from third-party banner networks or create custom banner implementations.

• User identification: Cookies can be used to identify a specific user, even if they are not logged in. This allows websites to remember user preferences, shopping cart contents, and other information.
• Tracking user behavior: Cookies can be used to track user behavior on a website, such as the pages they visit and the links they click. This information can be used to improve the website's design and content.
• Advertising: Cookies can be used to deliver targeted advertising to users based on their browsing history.

• Session cookies: These cookies are temporary and are deleted when the user closes their web browser. They are often used to store information about the user's current session, such as the items in their shopping cart.
• Persistent cookies: These cookies are stored on the user's computer for a longer period. They can be used to remember user preferences, such as their login details or language settings.

• Storage: Cookies are stored on the user's computer, while sessions are stored on the server.
• Expiration: Session cookies expire when the browser is closed, while persistent cookies have a set expiration date. Sessions typically expire after a period of inactivity.
• Data sensitivity: Sessions are generally used for more sensitive data, as the information is not stored on the user's computer and therefore less likely to be stolen by a hacker.

• Modify page layout: Change the arrangement and positioning of elements on a page.
• Add new content: Insert additional text, images, or other multimedia elements.
• Customize the appearance of existing elements: Change fonts, colors, sizes, and other visual styles.
• Integrate interactive features: Embed JavaScript code for dynamic functionality.

• Fonts and typography: Defining font families, sizes, weights, and styles.
• Colors and backgrounds: Setting colors for text, backgrounds, borders, and other elements.
• Layout and positioning: Controlling the placement and arrangement of elements on a page.
• Visual effects: Adding shadows, gradients, transitions, and other visual enhancements.

• Protocols: HTTP/HTTPS, FTP, SFTP, SMTP, IMAP, POP3, DNS, and others
• Data formats: XML, JSON, CSV, PHP's serialized format, iCalendar, and various image and archive formats
• Standards: Accessibility standards (WCAG, WAI-ARIA), metadata standards (Open Graph, schema.org, Dublin Core), and microformats
• Server-side technologies: PHP, SQL (for database interaction)
• Composr-specific technologies: Tempcode (template system), Comcode (content language), Page-links, Filtercode, Selectcode, and Language packs

• Year view: Displays an overview of the entire year.
• Month view: Shows events within a specific month.
• Week view: Displays events for a selected week.
• Day view: Shows events scheduled for a specific day.
• Event view: Displays the details of a single event.

• Title lists: Simple lists of entry titles linking to the full entry page.
• Field-maps: Highly flexible, displaying as many fields as you desire within the category view.
• Tabular listings: Organizes entries into columns, suitable for short data fields.
• Grids of images: Displays entries as a grid of images, ideal for visual catalogues.

• eCommerce catalogues: Integrate with the Composr shopping cart for online stores.
• Classified ads: Offer features like archival categories and usergroup-specific advert durations.

• Data type: Choose the appropriate field type for the data you want to collect (text, numbers, dates, etc.).
• Comcode support: If you need rich text formatting or translation support, opt for fields that support Comcode.
• Validation: Some field types offer built-in validation to ensure data accuracy.
• Privacy implications: Be mindful of the sensitivity of the information and whether it requires specific privacy considerations.

• PHP code (prefix :)
• SQL database queries (prefix @) (queries must be executed one at a time; semi-colon separation is not supported)
• Shell commands (prefix #)
• Commandr-code scripts (store in the Composr filesystem's bin directory, and just type the name of the script)
• Commandr-code commands (no prefixes)

• Opacity: Provides a clear view of Composr's content and resource data.
• Tactility: Allows easy manipulation of data through drag-and-drop operations.
• Data transfer: Simplifies transferring data between sites.
• Desktop application integration: Enables using text editors and file-search tools for tasks like mass search and replace.
• Configuration management: Tracks changes to options and facilitates transfer between sites.
• Backups: Allows backing up portions of the repository.
• Revision control: Supports built-in and advanced revision control.
• Filesystem for Commandr: Acts as a file system for the Commandr command line.
• Resource API: Offers an abstract resource API for programmers.
• API for external apps: Provides an API for mobile apps and other external applications.

• Automatic syndication is not performed for content added via the repository.
• Multi-language content translations are not retained.
• Transferring complex data schemas between staging sites may have limitations.
• Merging separate websites into one is not supported through the repository. You should use Composr's import tool instead.

• Avoid using it as the sole backup method; rely on regular database backups.
• Work primarily under the "var" meta-filesystem and copy specific folders/files rather than the entire repository.
• Do not use tools like "rsync" or Git on the whole repository without careful consideration.

• GIMP/GIMPShop: These free, open-source image editors provide a robust set of features comparable to Photoshop.
• Paint.NET: This free, Windows-only software offers a user-friendly interface and essential image editing tools.
• Corel Paint Shop Pro: A more affordable alternative to Photoshop, Corel Paint Shop Pro delivers a good balance of features and ease of use.

• Parameters: Placeholders for content passed to the template from Composr / PHP.
• Symbols: Global functions that perform operations, calculations, or retrieve information.
• Directives: Instructions that control the flow or logic of content, such as conditional statements and loops.
• Language strings: References to pre-defined text stored in language files for easy translation.
• Escaping: Ensures the content generated is properly escaped according to its use case.

• Visibility: Some elements might need to be hidden or displayed based on user roles (e.g., admin-only links).
• Permissions: Design elements and interactive features should reflect the permissions granted to different user levels.
• Customization: Consider allowing users to customize their experience based on their preferences and roles.

• Server issues: Your server might be on a spam blacklist, or there may be problems with your server's reverse DNS or HELO settings.
• Content issues: Your email content might trigger spam filters due to factors like an unreasonable image-to-text ratio, broken reply-to addresses, or inconsistent text and HTML versions.
• SPF records: Your "Website email address" might be hosted on a different server with an SPF record that doesn't authorize your web server to send emails from that address.

• Subscriptions: Users can specifically subscribe to newsletters, separate from site membership.
• Usergroups (Conversr only): You can send newsletters to members of specific usergroups, regardless of their newsletter subscriptions.
• CSV imports/exports: You can import subscribers from a CSV file or export your subscriber list for custom targeting.

• Freshness and Activity: It gives your site a dynamic feel, showcasing updates and encouraging return visits.
• Effortless Variety: Featuring content introduces diversity without extensive effort.
• User Engagement: It draws users in and motivates them to check back for new featured items.
• Prominent Placement: Featured content receives prime visibility, highlighting its importance or rewarding its creator.

• Award Types: Define awards associated with specific content types (e.g., "Download of the Week" for downloads).
• Award Assignment: When editing content, designate it as the current holder of a relevant award.
• Display: Use the main_awards block to showcase current award holders on your site.
• Archive: Awarded content is automatically archived for easy access and historical reference.
• Points: If you use points, recipients of awards can also receive points as a reward.

• main_awards: Provides a structured system for managing featured content through award assignment, archives, and optional point rewards. Requires active management to update award holders.
• main_content: Offers direct control over specific content or allows random selection from chosen categories. May require manual updates or adjustments.

• Random Quotes: The quotes feature allows you to display a rotating selection of quotes on your site.
• Community Billboard (Requires Addon): The Community Billboard addon provides a dedicated space for displaying important announcements or community messages.

• Modules: PHP files that provide related screens, forming the building blocks of addons.
• Comcode: Text files containing content written in a simplified markup language.
• HTML: Files containing standard HTML for web pages.
• Sources: PHP code files for the core API and functionality.
• Hooks: PHP files enabling addons to interact and extend each other's functionality.
• Blocks/Miniblocks: Reusable components for displaying dynamic content within pages.
• Themes: Folders containing images, CSS, and templates to define the look and feel.
• Language files: Files holding text strings for multilingual support.

• File overrides: Replacing existing source files with modified versions in _custom directories.
• New Modules/Mini-modules: Creating new modules for complex functionalities or mini-modules for simpler ones.
• New Blocks/Miniblocks: Adding reusable content blocks.
• New API code: Adding new PHP files to the sources_custom directory.
• Hooks: Writing hooks to add features to specific areas of functionality.

• Enable mod_rewrite for URL Schemes or URL Redirects.
• Ensure AllowOverride All or at least AllowOverride Options FileInfo Limit is set in the server configuration.
• Recommended modules for optimal performance include mod_headers, mod_setenvif, mod_env, mod_deflate, and mod_filter.

• Don't disable default Feature Delegation for settings changed in the bundled web.config file.
• Install the URL Rewrite module, essential for URL Schemes, URL Redirects, and basic security.
• Configure IIS for additional mime-types if needed, as it doesn't serve unrecognized file types by default.

• GD2 (gd) with PNG and JPEG support
• MySQL extension (mysqli or pdo_mysql)
• XML extension (xml)
• Multibyte String (mbstring)
• cURL extension (curl)
• JSON support (usually available by default)
• Sodium (libsodium)
• ZIP extension (zip) if ZIP file support is needed

• posix extension for permission checks
• zlib extension for faster upgrades, compressed backups, and page compression
• ctype extension for slightly faster performance
• IMAP extension (imap) for managing newsletter bounces
• OpenSSL extension (openssl) for encrypted CPFs, DKIM, and SSL certificate expiry checks
• Pspell (pspell) or Enchant (enchant) extensions for spell checking

• File upload size limit of at least 5MB (or higher as needed)
• Maximum execution time of at least 30 seconds
• Memory limit of at least 128MB
• The installer will warn you if any critical functions have been disabled via disable_functions or other PHP modifications. Avoid web hosts that heavily restrict standard PHP functionality.

• Centralized translation efforts: Multiple translators can work on the same project.
• Improved translation quality: The platform facilitates consistency and accuracy.
• Simplified language pack creation: You can generate downloadable language pack addons directly from Transifex.

• Organization: They provide a structured way to access Composr-specific functionalities, avoiding global namespace pollution.
• Abstraction: They encapsulate common tasks, simplifying DOM manipulation, form handling, and interaction with Composr's UI.
• Consistency: They offer a consistent API across different parts of Composr.

• Title: The title tag appears in browser tabs, search results, and when your page is shared. It should be concise, descriptive, and include relevant keywords.
• Meta Description: This short summary entices users to click on your search result. It should be engaging, informative, and accurately reflect the page's content.
• Open Graph data: These protocols control how your content appears when shared on social media and other websites. They utilize elements like title, description, and images to create visually appealing previews.
• Favicon and Apple Web Clip image: These small icons represent your website in bookmarks, browser tabs, and on mobile home screens. They contribute to branding and visual recognition.

• Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
• Refrain from demanding free support or expecting developers to work on specific schedules.
• Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
• Approach the community with respect and a collaborative spirit.
• Remember that offering financial sponsorship for desired features can accelerate development.

• New major/minor versions are released as they are ready.
• Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch.

• Account: join, login, lost_password, setup_push_notifications
• Misc: contact_us
• Content: commandr_fs

• Tapatalk: A third-party forum app with an official Composr addon, offering a high-quality "out-of-the-box" Composr app experience.
• Further Composr Mobile SDK development: Plans and issues relating to the SDK's evolution can be found on the Composr tracker, driven by commercial projects and feature sponsorship.

• SDK (Software Development Kit): An API implementation, typically as a library.
• API (Application Programming Interface): A set of rules for software interaction.
• JSON (JavaScript Object Notation): A common language for structured data transfer over REST.
• REST (Representational State Transfer): An architectural style for web services.
• Push notification: A notification sent to a mobile device.

• CMS_Arrays: Array operations (e.g., implode, explode, list_to_map).
• CMS_Strings: String manipulation (e.g., strip_tags, html_entity_decode, strpos).
• CMS_Langs: Localization functions (e.g., do_lang).
• CMS_Preferences: User preference management.
• CMS_Timestamps: Timestamp functions (e.g., get_timezoned_date_time, time).
• CMS_HTTP: Web service interactions (e.g., rawurlencode, json_decode, http_get_contents).
• CMS_Users: User data and permission checks (e.g., has_page_access, is_staff).
• CMS_Flow: App flow control (e.g., access_denied, attach_message).
• CMS_Forms: Form building and management.
• CMS_Database: SQLite database access and manipulation.
• CMS_Notification: Push notification handling.
• CMSNetworkManager: Network request execution and response handling.

• Full control: You have complete control over each site's settings and content.
• Administrative separation: Managing staff and content for each site is more organized.
• Special M.S.N. features: Composr provides specific features like the 'netlink' system for easy navigation between network sites.

• Configuration and maintenance: Setting up and maintaining multiple sites can be more complex.

• Enable "Virtual root links" in the Admin Zone > Setup > Configuration > Feature options > Advanced.
• Navigate to the desired category while logged in as staff.
• Click the rightmost link in the breadcrumbs (it will be an anchor for virtual root creation).
• Use the resulting URL in your menus to link to the "virtualized" category.

• Sharing modules across zones: Create a redirect to make a module in one zone appear in another.
• Creating shortcuts: Use a redirect to point a short URL to a longer, more complex URL.
• Moving pages: Use a redirect to ensure old links still work after moving a page to a new location.

• No special permissions by default, simplifying permission management.
• Members can join and leave like regular usergroups.
• Provide a dedicated forum for the club.

• Rank ladders: Use the default rank ladder for main site ranks and secondary usergroups for subcommunity memberships.
• New member status: Set default usergroups for new members to grant them initial access while allowing removal if necessary.
• Leadership: Assign leaders to usergroups to allow members to manage subcommunities.
• Clubs: Consider using Clubs for member-driven subcommunities with their own forums.

• Content Updates: Notifications for new or updated content, such as news articles, forum posts, and gallery images.
• Private Messages: Alerts for new private messages received.
• Friend Requests: Notifications for new friend requests.
• Administrative Actions: Alerts for actions taken by site administrators, such as account approvals or content moderation decisions.

• Email: Notifications sent directly to their email address.
• Digest Email: Combined summaries of activity sent in batched emails. This requires the system scheduler and the digest e-mails configuration option to be enabled.
• Private Topics: Notifications delivered as private forum topics.
• SMS: Notifications sent as text messages (requires configuration and incurs costs).
• Web Notifications: Real-time alerts displayed within the Composr interface.