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.
Search tracker issues
Open issues
| Identifier | Issue type | Title | Status | Funded? | |
|---|---|---|---|---|---|
| #5552 | Feature request or suggestion | Slim down addon_registry hooks | Open | No | View |
| #5569 | Feature request or suggestion | Compliance for new regulatory laws (holder issue) | Open | No | View |
| #5570 | Feature request or suggestion | Generative AI poisoning | Open | No | View |
| #5584 | Feature request or suggestion | Handle catalogue fields in privacy system | Open | No | View |
| #5586 | Feature request or suggestion | Task queue: Cron does not respect number of locked tasks; maybe it should | Open | No | View |
| #5593 | Feature request or suggestion | Add an "Activity Points" concept | Open | No | View |
| #5595 | Feature request or suggestion | Modify coding standards: PSR-12 requires short form types everywhere | Open | No | View |
| #5601 | Feature request or suggestion | Add ability to send anonymous warning PTs | Open | No | View |
| #5607 | Feature request or suggestion | Allow configuration options set to their defaults to dynamically change when the default changes | Open | No | View |
| #5609 | Feature request or suggestion | Add unit test for composr_release_build.ini to check target="_blank" | 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 |
