How do I translate the content on my Composr website?
Answer
Once you've installed a new language pack, you can translate existing content by:
Editing the content directly: Go to the specific content item (page, news post, etc.) and edit it in the new language.
Using the language editor: Access the language editor from Admin Zone > Style > Translate/rephrase Composr to modify language strings used on specific pages.
Note that some elements like forum names are not designed to be translated directly. Instead, you should create separate forums for each language.
What should I do after successfully importing data into Composr?
Answer
After importing, if all files like avatars, photos, and attachments have been copied to Composr's directories, you can remove the imported product's directory. However, it's advisable to keep the directory, database, and import session for a few weeks in case any data was not correctly imported and needs further attention. Importing is a complex process, so keeping backups and sources for a while is a good practice.
The Composr documentation provides extensive information. Additionally, you can seek assistance from experienced Composr developers, including the Composr team if your project allows for professional support.
Can I switch from a third-party forum to Conversr (Composr's built-in forum)?
Answer
Yes, if an importer exists for your current forum software, you can switch to Conversr during the import process. Composr will handle the forum driver switch and remap user IDs, but it's recommended to double-check permissions afterward.
The HTML website importer is an advanced tool for migrating static HTML websites to Composr. It analyzes the HTML structure to create zones, Comcode pages, and a basic template. It also attempts to fix links and file paths for Composr compatibility.
Import sessions track the progress and ID remapping for each import, allowing you to merge multiple sites or resume interrupted imports. This is particularly useful when merging multiple Composr sites into one.
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.
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.
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).
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.
