View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005801 | Composr | core_rich_media | public | 2024-07-23 17:23 | 2024-09-05 00:23 |
| Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
| Severity | Trivial-bug | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 11.beta2 | ||||
| Fixed in Version | |||||
| Summary | 0005801: IPv6 addresses getting emoticon-ed | ||||
| Description | Any IPv6 address that has an octave starting with a D gets turned into the grinning emoji in standard text... e.g. D000:D000:D000:D000:D000:D000:D000:D000 Would get translated to D000(grin)000(grin)000(grin)000(grin)000(grin)000(grin)000(grin)000 | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Automated message: This issue was created using the Report Issue Wizard on the Composr homesite. |
|
|
Changed to a feature request as you can use the tt tag. We shouldn't be coding Comcode specifically to provide exceptions for something so specific as ipv6 addresses. Maybe the parser can be improved, or a new per-emotion option can be added to make it not adjoin to non-whitespace. |
|
|
This is an actual bug; it happens in notifications (e.g. IP bans, stack traces, spam blocks). But I agree we could put tt tags in the notifications. |
|
|
Oh ok. Then we should use tt tags in those notifications. |
|
|
Automated response: IPv6 addresses getting emoticon-ed Added tt and kbd tags where appropriate. It is possible some may have still been missed. |
|
|
Fixed in Git commit fb12ed50f3 (https://gitlab.com/composr-foundation/composr/commit/fb12ed50f3 - link will become active once code pushed to GitLab) |
|
|
hotfix-5801, 2024-09-05 12am.tar (221,184 bytes) |
|
|
A hotfix (a TAR of files to upload) has been uploaded to this issue. Only apply this hotfix if you absolutely need it and cannot wait until the next release of Composr (releases are more reliable and strictly tested). As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade (https://baseurl/upgrader.php, use the hotfix on the step “Transfer across new/updated files”). The upgrader will automatically skip files belonging to addons you do not have installed or that are newer on disk than in the hotfix. Otherwise, you can manually extract and replace these files (do not replace if your on-disk file is newer than the one in the hotfix). Always take backups of your site or at least files you are replacing before applying a hotfix. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-07-25 22:16 | Chris Graham | Severity | Trivial-bug => Feature-request |
| 2024-07-25 22:16 | Chris Graham | Product Version | 11.beta1 => |
| 2024-07-25 22:16 | Chris Graham | Description Updated | View Revisions |
| 2024-07-25 22:16 | Chris Graham | Category | core => core_rich_media |
| 2024-07-25 22:17 | Chris Graham | Note Added: 0008957 | |
| 2024-07-25 23:16 | Patrick Schmalstig | Note Added: 0008969 | |
| 2024-07-25 23:16 | Patrick Schmalstig | Note Edited: 0008969 | View Revisions |
| 2024-07-25 23:17 | Patrick Schmalstig | Note Edited: 0008969 | View Revisions |
| 2024-07-26 01:16 | Chris Graham | Note Added: 0008974 | |
| 2024-07-26 01:16 | Chris Graham | Tag Attached: Roadmap: v11 |
