Common Errors
These are some of the most common errors you may encounter when using Composr, how they happen, and what to do if you get them (click an error to view its details):
MySQL client ran out of memory
MySQL could not serve a Composr database request because it ran out of memory.How Did This Happen?
Either
- A database table contains a very large amount of data
- The server is configured to have a very low limit
- Your server is overloaded
How Do I Fix It?
Contact your webhost for advice on how to fix it. Or consult the MySQL documentation.
The SELECT would examine more than MAX_JOIN_SIZE rows
MySQL could not serve a Composr database request because a configured limit was exceeded.How Did This Happen?
Either
- A database table contains a very large amount of data
- The server is configured to have a very low limit
How Do I Fix It?
There is currently no straight-forward fix to this problem. It may be a bug, or it may be a server configuration problem. Make a judgement call whether to contact your webhost or whether to post to the issue tracker. You may also wish to consult the MySQL documentation.
Can't open file: 'xxx.MYI'
A MySQL data file has corrupted or gone missing on your server.How Did This Happen?
Something outside the control of Composr caused this error, such as a hard disk fault, a power surge, a power cut, a forced computer reset, or a system administration mistake.How Do I Fix It?
Contact your webhost or the MySQL documentation. Anticipate that you may need to restore a backed up database.
MySQL server has gone away
MySQL was not able to serve a Composr database request.How Did This Happen?
There are three likely possible causes:
- The MySQL server is overloaded
- The web server is overloaded
- You have a particularly large amount of data (less likely)
How Do I Fix It?
Contact your webhost or MySQL configuration. Note that Composr usually tries to establish the connection again a few times. So it is unusual if you get this error and probably points to a problem.
Got packet bigger than 'max_allowed_packet' bytes
MySQL was not able to serve a particularly large Composr database request.How Did This Happen?
It is likely you're trying to insert a very large amount of data into a Composr entry.How Do I Fix It?
Consider breaking your data over a number of separate entries / queries in the code. If this happened in core Composr code, and your max_allowed_packet is greater than or equal to 16M, then please report it to the tracker.
Can't connect to local MySQL server through socket
Composr cannot connect to the MySQL database.How Did This Happen?
It is likely that either:
- MySQL is no longer running on the server.
- The MySQL server is (no longer) running on the same physical server as your web server ("localhost").
How Do I Fix It?
If you have just moved/installed your website then you likely entered the wrong database hostname. Your webhost, or webhosting control panel, likely provides documentation indicating what the correct setting is.
Otherwise, contact your webhost.
Can't connect to MySQL server on xxx
Composr cannot connect to the MySQL database.How Did This Happen?
It is likely that either:
- MySQL is no longer running on the server and needs resetting.
- MySQL is intentionally (no longer) running on the server.
- Your firewall is blocking the connection between your web server and the MySQL server.
How Do I Fix It?
If you have just moved/installed your website then you likely entered the wrong database hostname. Your webhost, or webhosting control panel, likely provides documentation indicating what the correct setting is.
If the MySQL server you are trying to access is on a different computer network to the web server it is likely you will need to use a different MySQL server. Most physical machines running web servers also run MySQL servers, so it is likely you can use 'localhost' as the MySQL server.
Otherwise, contact your webhost.
Access denied for user xxx
Composr cannot connect to the MySQL server with the configured username and password.
This advice is not relevant if you got the larger error message: Access denied for user xxx to database xxxHow Did This Happen?
This could happen for a number of reasons:
- You have configured Composr to use the wrong MySQL username and/or password.
- The MySQL username and/or password you configured have been changed or removed.
- You have moved your website to a new web server and not correctly updated the Composr configuration and/or set up your database.
- If your MySQL server and web server are different physical machines it is important MySQL is configured to allow connections from the web server machine (or all machines) for your configured username. This is not the default configuration.
- The authentication scheme was recently changed on the database server and the passwords were not updated to match the new scheme.
How Do I Fix It?
If you have just moved/installed your website then you likely entered the wrong username/password. Your webhosting control panel likely provides documentation an interface where you can configure MySQL usernames and password. Note that on some webhosts you enter a username but it gets given a prefix - if this is the case it should be indicated in the webhosting control panel.
If you have recently changed your MySQL username/password or moved web servers you can edit your configured 'Installation Options'. Call up the '/config_editor.php' script (by URL) and log in to it. You can update your configuration from there.
If your MySQL server and web server are different physical machines then you will need to either change that situation, or make some changes to your MySQL credentials. It may be as simple as choosing to allow 'Any host' to make connections. Some webhosting control panels allow you to change these settings.
Access denied for user xxx to database xxx
Composr cannot connect to the MySQL database with the configured username and password.How Did This Happen?
While the given username and password is correct, that user does not have privileges to access the database.How Do I Fix It?
Make sure that the username you have configured has access to the database you have configured. You will be able to do this from your webhosting control panel or a tool such as PhpMyAdmin. You could also do this through raw SQL (consult the MySQL documentation). This is not automatic even if the username and database name are the same.
Unknown database xxx
The configured database that Composr should use is not present on the MySQL server.How Did This Happen?
This could happen for a number of reasons:
- You have configured Composr to use the wrong MySQL database.
- The MySQL database you configured has been renamed or removed.
- You have moved your website to a new web server and not correctly updated the Composr configuration and/or set up your database.
How Do I Fix It?
If you have just moved/installed your website then you likely entered the wrong database name. Your webhosting control panel likely provides documentation an interface where you can manage your MySQL databases. Note that on some webhosts you enter a database name but it gets given a prefix - if this is the case it should be indicated in the webhosting control panel.
You can edit your configured 'Installation Options'. Call up the '/config_editor.php' script (by URL) and log in to it. You can update your configuration from there.
The PHP XML extension on your server is needed to use this feature
Composr is trying to work with XML but your web server is not capable of doing it in the standard way.How Did This Happen?
The web server's PHP configuration does not enable the 'XML' extension. It is usually enabled by default.How Do I Fix It?
Consult with your webhost, choose a different webhost, or configure your PHP settings to enable the XML extension (and restart).
The PHP FTP extension on your server is needed to use this feature
Composr is trying to write some files and it does not have access to them.How Did This Happen?
To access files for writing Composr needs the server to be configured as 'suEXEC' or it needs to be able to use an FTP connection to do the work. Neither of these options are available.
Note that this advice is not relevant for Windows servers.How Do I Fix It?
Consult with your webhost. Let them know you need either:If you are able, you can try enabling the FTP extension in PHP yourself (and restart).
- PHP to have the FTP extensions enabled, and an FTP server to be running
- suEXEC to be enabled (this is a major change for a webhost to implement but the Composr core team strongly recommends it)
You are using a shared install, which makes this action prohibited
You are trying to do a low-level administrative action but cannot as you are on a shared install.How Did This Happen?
You cannot perform certain actions on shared installs, either for security reasons, or because it would impact all other websites.How Do I Fix It?
There is no way around this. If it is a problem for you please discuss it on the Composr forums.
The TAR file xxx is corrupt
You tried to use a corrupted TAR file, such as a corrupted addon archive.How Did This Happen?
The file likely corrupted at some point when being downloaded/uploaded.How Do I Fix It?
Try again or get a new copy of the file. If the problem persists then contact the creator of the file. If it was generated or download from Composr then make an issue on the issue tracker.
A block file is missing: xxx
You have referenced a file that does not exist.How Did This Happen?
It is likely you used the Comcode or Tempcode block tag but you used the name of a block that is non-existent. It is also possible you referenced a real block but then later uninstalled the addon that contains that block.How Do I Fix It?
Correct the name of the block referenced, or remove the appropriate Comcode or Tempcode, or reinstall the block (or addon) in the Admin Zone > Structure > Addons > Module management.
A template file is missing: xxx
Some Composr code referenced a file that does not exist.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded, or you mistyped the name of the template.How Do I Fix It?
You can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A language file for language xxx is missing: xxx
Some Composr code, or a template, referenced a file that does not exist.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded, or you mistyped the name of the language file, or the file does not exist for that particular language pack.How Do I Fix It?
You can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A source code file is missing: xxx
Some Composr code referenced a file that does not exist.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded, or you mistyped the name of the file.How Do I Fix It?
You can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A text file for language is missing: xxx
Some Composr code referenced a file that does not exist.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded.How Do I Fix It?
You can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A language string is missing: xxx
Some Composr code, or a template, referenced a language string that does not exist.How Did This Happen?
If you have recently edited a template you may have accidentally created the problem by referencing a non-existent language string, or a language string that isn't in a file that gets loaded where the template is used. Language strings are referenced in templates like {!EXAMPLE}.
Otherwise, it is possible a language file did not fully upload when you upgraded/installed.How Do I Fix It?
If you recognise that the error might stem from a template change you have made then fix your language string reference. You may also need to clear the language and template caches under Admin Zone > Tools > Cleanup tools.
Otherwise you can use the 'Integrity checker' option within the upgrader to find a list of all corrupt files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A parameter, xxx, is referenced in the template, xxx, but not passed
A template referenced a parameter that the template is not actually given from the source code (or referring template).How Did This Happen?
If you have recently edited a template you may have accidentally created the problem by referencing a non-existent parameter. Parameters are referenced in templates like {EXAMPLE} and different templates receive different parameters (e.g. do_template in PHP code). You may have copy&pasted some code from one template into another and not realised it was not compatible.
Otherwise, you may have found a bug. It is possible that the software may neglect to pass a parameter in certain usages of a template. No errors of this type are left unfixed, but it is a common problem.How Do I Fix It?
If you recognise that the error might stem from a template change you have made then fix your template. Otherwise submit an issue to the tracker so it can be fixed.
The requested resource does not exist
A resource (usually a piece of content or a category of content) is being referenced or linked to by name/identifier, but there is no such resource.How Did This Happen?
Common causes include:
- If you delete something and then use your back button to try and access what you just deleted.
- If you follow a link to something that has since been deleted.
- A search engine bot is crawling your site and checking for resources (the bot should correct itself for ones that it finds missing; but some problematic bots might not).
It is also possible that there is some form of corruption in the database. For example, an entry says it is in a category that doesn't actually exist.How Do I Fix It?
Fix any invalid links if applicable, or set up a URL redirect to point that link somewhere else.
If you believe you have found a bug in the software, report it to the issue tracker.
The requested resource (xxx) does not exist
A resource (usually a piece of content or a category of content) is being referenced or linked to by name/identifier, but there is no such resource.How Did This Happen?
Common causes include:
- If you delete something and then use your back button to try and access what you just deleted.
- If you follow a link to something that has since been deleted.
- A search engine bot is crawling your site and checking for resources (the bot should correct itself for ones that it finds missing; but some problematic bots might not).
It is also possible that there is some form of corruption in the database. For example, an entry says it is in a category that doesn't actually exist.How Do I Fix It?
Fix any invalid links if applicable, or set up a URL redirect to point that link somewhere else.
If you believe you have found a bug in the software, report it to the issue tracker.
A resource, xxx, requested within some Comcode (the xxx tag) does not exist
A resource (usually a piece of content or a category of content) is being referenced or linked to by name/identifier in a Comcode tag, but there is no such resource.How Did This Happen?
You or someone else is referencing some resource within a Comcode tag, but that resource was later deleted or moved. Or, there was a typo.How Do I Fix It?
Fix any invalid Comcode tags if applicable.
If you believe you have found a bug in the software, report it to the issue tracker.
A link was posted here (xxx tag, xxx) but it appears to be a broken link
A URL is being referenced or linked to in a Comcode tag, but the URL is broken or cannot be accessed.How Did This Happen?
You or someone else is referencing a URL within a Comcode tag, but the URL is broken. Or, there was a typo.How Do I Fix It?
Fix any invalid Comcode tags if applicable. Note that URLs which redirect to other URLs (including redirecting http to https) will also trigger this error; you should update old URLs with the new one.
If you believe you have found a bug in the software, report it to the issue tracker.
Table 'xxx' is marked as crashed
There is a corrupt MySQL database table. Composr needs this table to function.How Did This Happen?
Something outside the control of Composr caused this error, such as a hard disk fault, a power surge, a power cut, the forced termination of a PHP process, or a forced computer reset.How Do I Fix It?
Your webhost will almost certainly provide a webhosting control panel with a tool called 'phpMyAdmin' (it may be called something else, such as 'Database management').
- Access / Log in to this tool
- Make sure you are in the database that Composr uses
- Tick (check) the table referenced in the error message.
- Scroll to the bottom of the screen.
- In the 'With selected' option list, choose 'Repair table'.
- You should see the page reload with a message stating the repair was successful.
If in doubt or if the table will not repair, contact your webhost.
Composr also offers a database repair tool in the upgrader. Call up '/upgrader.php' to run it.
A symbol was not properly closed
There is a mistake in a template or some Comcode.How Did This Happen?
It is likely you edited a template incorrectly or wrote some incorrect Comcode.How Do I Fix It?
A symbol is defined like {$EXAMPLE}. Make sure that this is the case for anything that starts {$. For example, make sure the final } is not missing.
You have gone to a URL which requires
A Composr screen was loaded up incorrectly.How Did This Happen?
It is likely you tried to access a screen via pure URL that was supposed to be the targeted for posted form data. This can happen if you press enter in the address bar of a results screen, click back and do not choose to 'resend posted data', or bookmark a results screen.How Do I Fix It?
Don't access the screen in this way.
You did not provide an upload, or you tried to upload a file that exceeds the file-size limit
A required upload was not provided or was too large.How Did This Happen?
It is possible that you did attach a file but it was larger than the server can accept for its 'max_post_size' setting and therefore resulted in all posted data for the request being lost.How Do I Fix It?
Check your system limits.
You can find more about setting the PHP 'max_post_size' option in the FAQ.
Cannot read from xxx
A file is missing or could not be read.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded.
It is also possible the permissions are incorrect for the file, but this is unlikely (by default files always have read permissions for everybody).How Do I Fix It?
You can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A critical parameter, xxx, was missing
An invalid URL was used.How Did This Happen?
It is likely part of a URL was missing. The URL was to a real Composr page, but it required some parameters that were not passed. For example, linking to the Composr page/screen-type for viewing downloads without specifying what download to view within the URL.
Some web spiders (automatic programs that read websites) can cause these errors because they will try and guess URLs based on other URLs.
Alternatively (and less likely), your server may be redirecting the domain you're using to another one in such a way that parameter information is lost.How Do I Fix It?
Provide the required parameters for the URL. If this error was triggered naturally from clicking something in Composr, it may be a bug and should be reported to the tracker.
Unknown tempcode directive, xxx
A template, or some Comcode, referenced a directive that does not exist.How Did This Happen?
It is likely you made a template change incorrectly. Directives are written:Code
{+START,IF,EXAMPLE,...}
...
{+END}
but the directive 'EXAMPLE' must actually exist. There are only a few defined.How Do I Fix It?
Only reference valid directives. Either correct or remove the offending code.
A symbol is missing: xxx
A template, or some Comcode, referenced a symbol that does not exist.How Did This Happen?
It is likely you made a template change incorrectly. Symbols are referenced like {$EXAMPLE}, but 'EXAMPLE' must actually exist. The following are defined.How Do I Fix It?
Only reference valid symbols. Either correct or remove the offending code.
No such theme image, xxx
A template, or some Comcode, referenced an image that does not exist.How Did This Happen?
It is likely the file did not upload correctly when you installed/upgraded.
Alternatively, you may have edited some Comcode or a template to refer to an image incorrectly.How Do I Fix It?
This might be a cache issue. Clear your caches (especially theme image and template caches) in the Admin Zone > Tools > Cleanup tools.
If this does not work, you can use the 'Integrity checker' option within the upgrader to find a list of all missing files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are missing you need to upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
A category (xxx) that doesn't exist is being referenced
A category is being referenced or linked to by name/identifier, but there is no such category.How Did This Happen?
Common causes include:
- If you delete a category and then use your back button to try and access what you just deleted.
- If you follow a link to a category that has since been deleted.
It is also possible that there is some form of corruption in the database. For example, an entry says it is in a category that doesn't actually exist.How Do I Fix It?
Fix any invalid links, or create URL redirects from deleted categories.
If you believe you have found a bug in the software, report it to the tracker.
Could not connect to the database
Composr cannot connect to the MySQL database.How Did This Happen?
It is likely that either:
- MySQL is no longer running on the server and needs resetting.
- MySQL is intentionally (no longer) running on the server.
- Your firewall is blocking the connection between your web server and the MySQL server.
How Do I Fix It?
If you have just moved/installed your website then you likely entered the wrong database hostname. Your webhost, or webhosting control panel, likely provides documentation indicating what the correct setting is.
If the MySQL server you are trying to access is on a different computer network to the web server it is likely you will need to use a different MySQL server. Most physical machines running web servers also run MySQL servers, so it is likely you can use 'localhost' as the MySQL server.
Otherwise, contact your webhost.
Could not connect to the database with the database username you specified
Composr cannot connect to the MySQL database with the configured username and password.How Did This Happen?
You are likely using correct settings to connect to your database, but MySQL has not been configured correctly.How Do I Fix It?
Make sure that the username you have configured has access to the database you have configured. You will be able to do this from your webhosting control panel. This is not automatic even if the username and database name are the same.
You must have a forum to perform this action
You are trying to perform a member-related action, or comment on something, but you don't have a forum.How Did This Happen?
You installed Composr with the 'No forums or members' option.How Do I Fix It?
We strongly advise to give this option consideration when you install. If you have not done a lot of work on your website yet it is best to reinstall.
Otherwise edit the Installation Options by calling up your '/config_editor.php' script by URL. Change the 'forum_type' from 'none' to 'cns'. Check all your permissions to make sure they are correct.
You must have a member system to perform this action
You are trying to perform a member-related action but you don't have a forum.How Did This Happen?
You installed Composr with the 'No forums or members' option.How Do I Fix It?
We strongly advise to give this option consideration when you install. If you have not done a lot of work on your website yet it is best to reinstall.
Otherwise edit the Installation Options by calling up your '/config_editor.php' script by URL. Change the 'forum_type' from 'none' to 'cns'. Check all your permissions to make sure they are correct.
You are accessing a directory through the software (xxx) which is not a zone
You are accessing a directory that appears to be a zone but is not one.How Did This Happen?
It is quite likely the 'pages' directory is missing from the zone's directory.
It is also possible you're loading up files from somewhere you've placed a partial backup.How Do I Fix It?
If you really are trying to access the named zone, either upload the missing files or recreate the zone.
Otherwise avoid the URL or remove the Composr index.php file from the 'zone' directory.
Could not save xxx. Are you out of disk space or quota space?
Composr failed to do a simple file write.How Did This Happen?
The most common causes of this problem are a lack of disk space of available disk quota.
However it is also possible that:
- You tried to use an empty file for something that requires a real file.
- There is a disk error.
How Do I Fix It?
First identify if you are out of disk space or quota space. If you are, resolve this problem by making some space or contacting your webhost.
If you believe it could be a disk error, take a backup (and download it) as soon as possible and contact the webhost to replace your disk.
If it is just due to an empty file, observe that you need to give a real file to perform the operation you attempted.
Non-closed brace or directive in template xxx
A template is corrupt.How Did This Happen?
The file may have uploaded incorrectly, or it may have been edited incorrectly.
Tempcode directives must end. i.e. For any {+START,...} there must be a {+END} somewhere later in the file.
Any kind of variable (parameter, symbol, language reference, or directive) must have a closing brace (}) corresponding to it's opening brace ({). e.g. {EXAMPLE,a,{B} is invalid and should be {$EXAMPLE,a,{B}}.How Do I Fix It?
If you have mis-edited a template, correct that error. If you can't because the template editor itself shows the error then open up Composr using the default theme and safe mode by appending &keep_safe_mode=1&keep_theme=default to a URL then browsing to the editor as normal (or ?keep_safe_mode=1&keep_theme=default if the URL you are adding to it doesn't have any parameters on yet). The Setup Wizard asked you to bookmark the safe mode URL so you may find it in your bookmarks if you're struggling.
You can use the 'Integrity checker' option within the upgrader to find a list of all corrupt files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are corrupt you need to re-upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
No directive type specified in xxx
A template is corrupt.How Did This Happen?
The template was edited incorrectly.
Tempcode directives must specify a directive type. E.g. {+START,EXAMPLE} is a directive of type 'EXAMPLE'.
Writing {+START} is meaningless and will cause this error.How Do I Fix It?
Remove or correct the offending code. If you can't because the template editor itself shows the error then open up Composr using the default theme and safe mode by appending &keep_safe_mode=1&keep_theme=default to a URL then browsing to the editor as normal (or ?keep_safe_mode=1&keep_theme=default if the URL you are adding to it doesn't have any parameters on yet). The Setup Wizard asked you to bookmark the safe mode URL so you may find it in your bookmarks if you're struggling.
Abrupted brace or directive in template xxx
A template is corrupt.How Did This Happen?
The file may have uploaded incorrectly, or it may have been edited incorrectly.
Some Tempcode has been miswritten in some way.
For example:orCode
{+
STARTorCode
{+START
,EXAMPLE}orCode
{$ EXAMPLE}Code
{$EXAMPLE
}
In other words, anomalous spaces or symbols will cause this problem.How Do I Fix It?
If you have mis-edited a template, correct that error. If you can't because the template editor itself shows the error then open up Composr using the default theme and safe mode by appending &keep_safe_mode=1&keep_theme=default to a URL then browsing to the editor as normal (or ?keep_safe_mode=1&keep_theme=default if the URL you are adding to it doesn't have any parameters on yet). The Setup Wizard asked you to bookmark the safe mode URL so you may find it in your bookmarks if you're struggling.
You can use the 'Integrity checker' option within the upgrader to find a list of all corrupt files. You can access the upgrader by calling up the '/upgrader.php' URL on your site.
Once you have identified which files are corrupt you need to re-upload them. Download the manual installer from the Composr website that corresponds to your version, and then upload the files using an FTP client (or by some other means if you prefer).
Brace/directive mismatch: too many closes, or closed one that was not open in xxx on line xxx
A template is corrupt.How Did This Happen?
The file has been edited incorrectly. Every {+START,...} needs a corresponding {+END}.How Do I Fix It?
Correct the template with the error. If you can't because the template editor itself shows the error then open up Composr using the default theme and safe mode by appending &keep_safe_mode=1&keep_theme=default to a URL then browsing to the editor as normal (or ?keep_safe_mode=1&keep_theme=default if the URL you are adding to it doesn't have any parameters on yet). The Setup Wizard asked you to bookmark the safe mode URL so you may find it in your bookmarks if you're struggling.
You tried to upload a file xxx which was larger than the maximum allowed size (xxx bytes)
You tried to upload a file that was too largeHow Did This Happen?
The file is larger than either:
- the PHP 'post_max_size' setting
- the PHP 'upload_max_filesize' setting
- the website's setting for the maximum file size
- the website's setting for the maximum image size (if it is an image)
- your remaining quota space
How Do I Fix It?
Go to the Admin Zone, then the Setup section, then the Configuration icon, then the Security options, then the 'Upload' section. You will see the PHP and website settings laid out here. If you need the PHP options changed you can likely use the .user.ini file to do it – see the FAQ.
It is unlikely you are being affected by a quota restriction, as by-default staff do not have any quota restrictions. You can see quotas when editing usergroups.
A page (xxx) was referenced that does not exist
A page was accessed by name, but there is no such page.How Did This Happen?
It is likely the page once existed but does not exist any more.How Do I Fix It?
Check the zone directory inside all html/comcode/modules sub-directories to see if it exists. Change/remove any broken links. Add URL redirects from broken links elsewhere if necessary.
Error detected with respect to the upload of a file: the uploaded file was only partially uploaded
An error occurred when uploading a file.How Did This Happen?
There was a transmission error. This could be due to a network interruption.How Do I Fix It?
Please try again. If it keeps happening, your connection might be getting terminated due to size restrictions or other issues. You may need to diagnose your network or the network of the server.
Error detected with respect to the upload of a file: no file was selected, or a missing file was chosen
A file was expected but was not received.How Did This Happen?
You likely referred to an attachment via Comcode ([attachment]new_1[/attachment]), but no file was actually attached.How Do I Fix It?
This error is usually safe to ignore, but be aware when copying & pasting Comcode that references yet-unattached attachments, you would need to choose to re-attach the file also.
You may wish to go back and edit your content, attaching the file this time around, or removing the Comcode.
Error detected with respect to the upload of a file: the uploaded file is too large
You tried to upload a file that was too largeHow Did This Happen?
The file is larger than either:
- the PHP 'post_max_size' setting
- the PHP 'upload_max_filesize' setting
- the website's setting for the maximum file size
- the website's setting for the maximum image size (if it is an image)
- your remaining quota space
How Do I Fix It?
Go to the Admin Zone, then the Setup section, then the Configuration icon, then the Security options, then the 'Upload' section. You will see the PHP and website settings laid out here. If you need the PHP options changed you can likely use the .user.ini file to do it – see the FAQ.
It is unlikely you are being affected by a quota restriction, as by-default staff do not have any quota restrictions. You can see quotas when editing usergroups.
The uploaded file (xxx) could not be moved to its target destination (xxx)
The server could not put your uploaded file where it needs to be.How Did This Happen?
This could be caused by a number of problems:
- There is a permission problem on the upload temporary directory.
- There is a permission problem on the target directory.
- There is an 'open_basedir' restriction in place that does not allow access to the upload temporary directory.
How Do I Fix It?
First check the permissions on your target directory. There are tools in the upgrader script to check and repair permissions.
You can access the upgrader by calling up the '/upgrader.php' URL on your site.
If you still have not been able to solve the problem contact your webhost and ask them to investigate for you.
Cannot create a directory xxx. This file should have existed anyway
A directory was needed but missing. Composr tried to create it but failed.How Did This Happen?
This happens often when people upload a new language pack without adding it first by starting a translation via the language tools in the Style section of the Admin Zone.How Do I Fix It?
Create the directory manually via an FTP client, or some other file management tool if you prefer.
Could not save. Are you out of disk space or quota space? The file failed to save in a temporary directory
Composr failed to create a temporary file.How Did This Happen?
It is likely either:
- the server is out of disk space on it's temporary directory (sometimes temporary directories are on different partitions/disks to website directories)
- the quota on the temporary directory has been exceeded
How Do I Fix It?
Consult with your webhost.
A system e-mail could not be sent
Your web server is unable to send e-mails.How Did This Happen?
It is likely that either:
- You are on a Windows server and nobody has configured the PHP SMTP settings (in the php.ini file).
- You are on a Linux server and there is no outgoing e-mail service on it (e.g. sendmail, postfix, qmail).
How Do I Fix It?
The system administrator should resolve the problem by making the correct php.ini settings or setting up an e-mail server.
You can try and work around the problem by configuring Composr to send e-mail through a different SMTP server using its own code (configure this under the Admin Zone, Setup Section, Configuration icon, 'Site options').
The necessary forum for this has not yet been created
You selected a forum in a configuration setting which does not exist.How Did This Happen?
Addons which have configuration options involving forums might set an arbitrary forum ID which does not exist yet as its default. Or, you might have defined a forum which existed at one point but does not anymore.How Do I Fix It?
Go into the configuration setting and change it to a forum which exists.
A configuration option (xxx) which does not exist was referenced
Some code or template is trying to access the value of a configuration option which does not exist.How Did This Happen?
This can happen when you mis-type the name of the configuration option. It can also happen if the addon containing the option is no-longer installed or was never installed (this is a bug and should be reported to the tracker).How Do I Fix It?
Check to ensure you typed the configuration option name correctly and that it exists, e.g. a hook exists for it under hooks/systems/config. You might also need to clear caches (template, self-learning, block) in Admin Zone > Tools > Cleanup tools.
Form field $description parameters should end in full stops
A description for a form field lacked a full stop.How Did This Happen?
You created or modified a language string which is used as a form field description and lacked a full stop.How Do I Fix It?
Fix the responsible language string so it ends in a full stop (usually a period, end bracket / brace, question mark, exclamation point, or ending HTML kbd tag.
cannot access the file from the given URL
Composr tried to access a file from an external URL but encountered an error or access restrictionHow Did This Happen?
You tried to use a URL as a file in some component of Composr (e.g. a download, attachment, thumbnail, embed, image, video). However, when Composr tried to access the URL, a non-successful status code was returned.How Do I Fix It?
Try the following:
- Double-check that you typed the URL correctly and that you have the correct access permissions for that URL. If a URL requires credentials / logging in to access, Composr usually cannot handle that (therefore you will get this error); you must use publicly-accessible files.
- Also check to ensure the URL still exists and does not redirect; if it redirects, you must update the URL in Composr with the new one.
- Also make sure your server can access external sites and that the site is not blocking Composr from accessing it (sometimes other sites will perceive this check by Composr as a bot action, since it is automated, and block it, though we try to work around that).
A file, xxx, is either corrupt or a filetype not recognised
An uploaded media file is corrupt or its file type could not be determined.How Did This Happen?
You or someone else uploaded a file, which was supposed to be a photo or video, that was either not a photo or video, or that was corrupt. Composr tried to do some post-processing on the file but failed to do so.How Do I Fix It?
Make sure the uploaded image or video is a supported file type by Composr. Also ensure it is not corrupt by checking it on your computer. It is possible a network interruption caused the upload to abruptly terminate, thereby corrupting the file on the server, so check your network connection on the server as well. Also ensure your PHP's GD extension is working properly.
