Composr has an integrated attachment system. You can upload files, like images or documents, via the attachments section (or the image button if using the WYSIWYG editor with simplified attachments UI), and they will be automatically added to your Comcode using the attachment tag. You can then move this tag within your content to position the attachment as needed.
Comcode tags are similar to HTML tags, but use square brackets [] instead of angle brackets <>. Each tag has an opening and closing tag, with content in between.
Example: [b]This text would be bold.[/b]
Tags can also have parameters: Example: [img src="image.jpg" alt="Image description"]
A shorthand exists for the param parameter (the primary parameter of Comcode tags): Example: [page="_SEARCH:howdy_do"]Howdy do[/page]
Intuitive content authoring: It's written like plain text, making it easy to learn and use. Dynamic functionality: You can embed dynamic content like blocks, comments, and forms using Comcode. Special effects: You can easily add prebuilt graphical features like tabs, carousels, and more. Basic styling and layout: Comcode allows for basic website styling and page layout. HTML integration: For advanced styling and layout, you can embed HTML code within Comcode with the semihtml tag.
Comcode is Composr's markup language, similar to BBCode used in forums. It allows you to create formatted text, embed dynamic content like blocks and attachments, and even mix in HTML for advanced styling. It's user-friendly and designed to work alongside standard web technologies.
Can I leave notes for myself or other staff members?
Answer
Yes, the Admin Zone includes a dedicated "Notes" block for you and your staff to leave messages and reminders. This space serves as a shared communication hub for your team.
How can I stay informed about the latest Composr version?
Answer
The Admin Zone dashboard displays information about your current Composr version and alerts you if it's not the most recent one. A link will be provided to guide you through the upgrade process if necessary.
The action log keeps track of administrative and content-related actions on your website. It allows you to see who did what and when, providing valuable insights into site activity and accountability. You can filter the log to focus on specific actions, users, or timeframes. It's also helpful for revisiting previous tasks by providing links to the relevant content or settings. Go to the Admin Zone > Audit > Action logs. A quick action log block is also available on the dashboard.
The staff checklist is an automatically generated list of tasks that need attention on your website. It includes routine updates like assigning new awards or adding news, as well as less frequent but important tasks like backups, software updates, newsletters, content validation, and periodic content reviews. You can customize the frequency of these tasks in the 'Configuration' section under 'Administrative options'. You can also add your own custom tasks. Anyone with Admin Zone access can see the checklist. So you can collaborate with your highest level staff on it.
I'm lost! How can I find a specific feature or setting?
Answer
The Admin Zone has a powerful search feature that you can access under the Help icon. It searches through various categories, including configuration options, privileges, templates, language strings, administrative modules, and more. You can even refine your search by adding "@sectionname" to the end of your search term to limit results to a specific section.
You can access the Admin Zone by clicking the "Admin Zone" link located at the bottom of every page on your website, assuming you are using the default theme. If you are logged in as a staff member, your user menu will also have a link to the Admin Zone or the Content Management Zone. You might be asked to log in again / confirm your session for security reasons.
Composr follows a rolling release model. This means:
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.
Users are responsible for staying updated to the latest release or applying necessary hotfixes.
This policy allows developers to focus resources on the latest versions and encourages users to leverage the ongoing improvements. You can find the release status on the Composr maintenance status page.
Constructive design feedback is valuable. To provide effective feedback:
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.
Directly reporting specific design bugs to the tracker or redesigning Composr interfaces yourself are excellent ways to contribute.
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.
How do I report an emergency problem with my Composr site?
Answer
Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these:
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.
Remember that bug fixing is not a free service. While developers are committed to Composr's stability, maintaining backups and practicing restoration procedures is your responsibility.
The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer.
I'm getting a lot of spam on my site. What can I do?
Answer
Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents.
My website is experiencing performance issues. What should I do?
Answer
If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server.
If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts.
Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released.
Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr.
When reporting a bug, be sure to:
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
relevant details.
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.
