Why are my searches slow, and how can I improve search speed?
Answer
Slow searches can occur when dealing with large amounts of content. Here are some workarounds and solutions:
MySQL timeout setting: For MySQL 5.7+, set a query timeout to prevent searches from locking up your database. Composr automatically sets this, but you can configure it manually if needed.
Use InnoDB tables: Switching to InnoDB tables in MySQL can prevent slow queries from affecting other users on your website. Note that InnoDB is not officially supported by Composr yet.
Enable the fast custom index: As mentioned earlier, the fast custom index is optimized for handling large datasets and filtered searches, potentially leading to significant speed improvements.
How does the search engine handle different languages?
Answer
Composr's fast custom index supports multiple languages. Content is indexed based on its translated version, ensuring that you get relevant results even when searching in a different language.
Quoted phrases allow you to search for an exact sequence of words. For example, searching for "red apple" will only return results containing that exact phrase. Keep in mind that enabling quoted phrases can increase disk space usage.
Stop words are common words (like "the", "a", "is") that are ignored by the search engine because they add noise and don't contribute to the meaning of the search query. You can customize the list of stop words for the fast custom index. See the search tutorial for more information.
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.
