View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006070 | Composr alpha bug reports | [All Projects] General / Uncategorised | public | 2024-11-26 19:08 | 2024-11-26 20:57 |
| Reporter | Adam Edington | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Summary | 0006070: Option to install Conversr to a unique database | ||||
| Description | I am not sure if it is the standard that databases are limited to 1024MB, but on my hosting package they are. This is currently not an issue, but perhaps it could be in the future. Would it be possible to create the option to install Convesr to its own database (perhaps also other features which may result in large amount of data)? | ||||
| Tags | No tags attached. | ||||
| Sponsorship open | |||||
|
|
I don't know if this will work for Conversr but I do know you can specify the following in _config.php: $SITE_INFO['db_forums'] = ''; $SITE_INFO['db_forums_host'] = ''; $SITE_INFO['db_forums_user'] = ''; $SITE_INFO['db_forums_password'] = ''; This is mainly for third-party forum drivers. You can give it a try for Conversr and let me know if it works. Migrate everything starting with (prefix)_f_* over to a new database, and fill these in your _config.php. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-11-26 19:08 | Adam Edington | New Issue | |
| 2024-11-26 20:57 | Patrick Schmalstig | Note Added: 0009683 |
