This is just a placeholder site for Composr CMS 11 beta. It will become the new homesite once version 11 reaches stable. For the current v10 homesite, click here. Please also use the v10 tracker to report v11 issues.

The telemetry service is being re-built and will not work for any sites until v11 beta7. Please report all Composr errors you encounter to the tracker to ensure the developers receive them.

Featured Sites: A-Z Index

H

Composr CMS: Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your ControlComposr CMS: Your Data, Your…

Composr CMS:
Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your Control

Earth & Sky

Legends of Nor'Ova

Legends of Nor'Ova

PDStig, LLC

Super Tilted

Saving Wallden

Newest 10 Entries

Question	What are the different ways to target recipients for my newsletters?
Answer	Composr offers several targeting options: 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.

Question	How can I prevent my emails from being marked as spam?
Answer	Here are some tips to reduce the likelihood of your emails being flagged as spam: 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.

Question	Why are my emails being blocked by spam filters?
Answer	Several factors can cause emails to be blocked: 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.

Question	How do I configure SMTP settings in Composr?
Answer	Composr can use either its own SMTP connection code or PHP's built-in SMTP functionality. Using PHP's SMTP settings is generally recommended and can be managed at the server level. However, if your SMTP server requires authentication (which PHP doesn't support natively) or if your server lacks an SMTP server, you'll need to use Composr's SMTP connection code, configurable in the Configuration module.

Question	How does Composr send emails?
Answer	Composr constructs emails using language strings and templates written in Comcode. It sends emails in both HTML and plain text formats to ensure compatibility with different email clients. To minimize the chance of emails being marked as spam, Composr embeds CSS and images directly into the email instead of linking to them externally.

Question	How can I make my website design more appealing to different thinking styles?
Answer	Different individuals process information differently. Some are more visual, while others are more analytical. To appeal to diverse thinking styles, a website design should incorporate a balance of elements. For instance, using a striking header image coupled with well-structured, informative text can cater to both visual and analytical thinkers. Understanding your target audience and their thinking styles is key to creating a design that resonates with them.

Question	What considerations are necessary when designing for different user levels on a website?
Answer	User levels often necessitate different content or functionalities. For instance, administrators might need access to content creation tools, while regular visitors only view published content. Consider these factors during design: 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. Remember, a well-designed website should cater to all user levels while maintaining security and a cohesive experience.

Question	How do I make my website theme mobile-friendly in Composr?
Answer	Composr offers several features to optimize themes for mobile: 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.

Question	What is responsive design, and why is it essential for mobile devices?
Answer	Responsive design ensures a website adapts seamlessly to different screen sizes, providing an optimal viewing experience across devices, particularly mobile phones and tablets. It utilizes techniques like flexible grids, fluid images, and CSS media queries to adjust layout and content based on screen dimensions. This is crucial because mobile device usage is significant, and a non-responsive site leads to a poor user experience on smaller screens, potentially driving visitors away.

Question	How can I create a theme pack for release in Composr?
Answer	After designing your theme, go to the admin panel's "Addons" section. You'll find an option to export your current theme as an addon. Composr will package the necessary files into a downloadable archive, ready to be shared with others or submitted to the Composr community for installation on other sites.

Top 10 Entries

Website	PDStig, LLC
Screenshot
Short Description	This is an informational site / portfolio for PDStig, LLC, the company run by one of Composr's lead developers, Patrick Schmalstig.

Website	Composr CMS: Your Data, Your Privacy, Your Control - Composr CMS: Your Data, Your Privacy, Your Control
Screenshot
Short Description	This is the main website for Composr CMS version 11. It runs the latest build of v11. Currently it is just a placeholder but will soon replace compo.sr when v11 becomes stable.

Question

Should I use the bleeding edge releases or the git repository?

Answer

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

Bleeding edge releases	Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git	Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates	Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated	Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions	Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release	Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing	Intended for developers / developer testing: * special run-time checks are enabled for extra debugging (if the .git directory exists in the install) * contains the automated test suite for running tests

Click here to access the git repository.

Question	Can I switch a v11 install from git over to using the releases from composr.app?
Answer	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.

Question	Should I update my non-bundled addons after updating to a newer release of version 11?
Answer	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.

Question	Can I upgrade a version 10 site to version 11?
Answer	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.

Question	Can I upgrade a previous version 11 release to a newer one using the upgrader?
Answer	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).

Question	What are the current release plans for version 11?
Answer	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.

Question	Why is there a separate website for version 11?
Answer	That is explained in detail in this news article on compo.sr including the migration plans and implications.

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test