Composr Issue Tracker

Welcome to the issue tracker! Here, you can view reported software issues.

All users are encouraged to report software issues or suggestions to the tracker. You will be awarded points for each issue you report that gets completed by someone.

Developers are encouraged to go through the tracker and implement issues. You will receive points for issues you implement. Prioritise issues in the following order:
  • Security issues
  • Major issues
  • Minor issues
  • Trivial issues
  • Feature requests
    • Be aware this requires you create a measure for voting, and you achieve a simple majority, before implementing into core code. This is not necessary for non-bundled addons.

Please read our providing feedback tutorial page before reporting an issue.

Click here to view the full issue tracker catalogue.

Click here to report an issue or suggestion.


Open issues

Identifier Issue type Title Status Funded?
#6262 Feature request or suggestion Report log times explicitly in privacy policy Open No View
#6259 Minor issue (breaks specific functionality) Optimise/fix database tables = 504 Open No View
#6258 Minor issue (breaks specific functionality) Facebook Image Meta not sanitised Open No View
#6245 Trivial issue (does not break functionality) Spacing issue with Join Declarations Open No View
#6239 Feature request or suggestion JS linter: check for accidental assignment to browser globals Open No View
#6238 Feature request or suggestion Add config option to block AI bots Open No View
#6237 Minor issue (breaks specific functionality) testing_platform: critical_error_display_test_set fails even though _critical_error.html works Open No View
#6236 Feature request or suggestion testing_platform: In lang_ini_size, add smart test for global.ini Open No View
#6234 Minor issue (breaks specific functionality) Adding an attachment to quick reply does not actually add it Open No View
#6232 Security issue (exploit in Composr) Loose string comparison may return true for scientific notation Open No View

Completed issues

Identifier Issue type Title Status Funded?
#6103 Trivial issue (does not break functionality) Catalogue field sort order confusion Completed No View
#6101 Trivial issue (does not break functionality) [beta6] Home Home Home Completed No View
#6087 Minor issue (breaks specific functionality) It appears auto-banning in log_hack_attack_and_exit is not working for anyone Completed No View
#6086 Feature request or suggestion Add option to make new Comcode pages not validated by default Completed No View
#6085 Feature request or suggestion Change get_username_from_human_name to process_username_discriminator Completed No View
#6084 Minor issue (breaks specific functionality) cms_comcode_pages not properly checking permissions Completed No View
#6076 Minor issue (breaks specific functionality) Newsletter block allows easy spam subscriptions Completed No View
#6073 Minor issue (breaks specific functionality) We need a special field type for serialized data Completed No View
#6072 Feature request or suggestion If the password ratchet is changed, update member passwords when they next log in Completed No View
#6069 Trivial issue (does not break functionality) messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5 Completed No View