| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 881 | [XMB1] Bugs | minor | always | 2026-01-24 00:07 | 2026-01-31 08:11 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | confirmed | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.9.12.10 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | post.php edit truncation issue - probably all xmb versions | ||||
| Description: |
xmb_posts.subject is TINYTEXT (can exceed 128 chars, up to 255?) xmb_threads.subject is VARCHAR(128) When editing the FIRST post in a thread, XMB updates BOTH tables. If subject exceeds threads.subject length, MySQL throws: "Data too long for column 'subject' (errno 1406)" New-topic posting already truncates correctly, but the EDIT path did not. To preserve full subject in posts while keeping threads safe: - Clone the already-escaped subject - Truncate ONLY the copy used for xmb_threads - Never modify $dbsubject (used by xmb_posts) This prevents edit-time errors without changing schema or behaviour. clone subject for threads // $dbsubject is already escaped at this point, so replace: if ((int) $isfirstpost['pid'] == $pid) { $db->query("UPDATE ".X_PREFIX."threads SET icon='$sql_posticon', subject='$dbsubject' WHERE tid=$tid"); } with if ((int) $isfirstpost['pid'] == $pid) { $dbtsubject = $dbsubject; // enforce threads.subject length $query = $db->query("SELECT subject FROM ".X_PREFIX."threads WHERE 1=0"); $tsubmax = $db->field_len($query, 0); $db->free_result($query); if (strlen($dbtsubject) > $tsubmax) { $dbtsubject = substr($dbtsubject, 0, $tsubmax); } $db->query("UPDATE ".X_PREFIX."threads SET icon='$posticon', subject='$dbtsubject' WHERE tid=$tid"); } OR the DB schema could be changed :) |
||||
| Tags: | |||||
| Steps To Reproduce: |
When editing the FIRST post in a thread, XMB updates BOTH tables. If subject exceeds threads.subject length, MySQL throws: "Data too long for column 'subject' (errno 1406)" |
||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 882 | [XMB1] Bugs | minor | always | 2026-01-31 08:05 | 2026-01-31 08:05 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Subject Schema is Different for Posts and Threads | ||||
| Description: | The subject field length and type needs to be unified because there's no advantage to having them work differently in 2 tables. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 880 | [XMB1] Bugs | minor | always | 2026-01-18 07:07 | 2026-01-18 07:07 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.10.03 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Quarantine Panel: Post Links are Broken | ||||
| Description: | Instead of linking to the public post address for each quarantined post, which is invalid, the quarantine panel should simply link to the public thread page. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 878 | [XMB1] Bugs | tweak | have not tried | 2026-01-08 15:54 | 2026-01-08 15:54 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Don't Use the Error Template on 404 Pages | ||||
| Description: |
XMB has long used the error template when items are not found. With v1.9.11, the 404 status code was added to these pages. Now, we need to stop displaying the error template when items are not found. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 875 | [XMB1] New Features | feature | N/A | 2025-12-24 07:58 | 2025-12-28 07:02 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Allow Relocation of config.php | ||||
| Description: | For an extra layer of security, it needs to be possible to change the location of the config.php file without breaking everything. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: |
Many search results on this topic recommend placing the config file outside of the web root, or placing the passwords in environment variables. I don't think these options are particularly simple or efficient on their own. I would like to take a direction in which the config.php file simply contains an extra variable $configPath which optionally points to a secondary file. This allows XMB to look for overrides in a customized location with little to no performance impact. This also preserves the ability to upgrade the configuration in future versions, because the values aren't getting locked away in some other system resource or auto included file. |
||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 877 | [XMB1] New Features | feature | N/A | 2025-12-24 12:57 | 2025-12-24 12:57 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.10.03 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Update Symfony Mailer to v8 | ||||
| Description: | Symfony 8.0 is available and should be updated for testing. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 864 | [XMB1] Bugs | minor | have not tried | 2025-12-18 19:30 | 2025-12-24 12:41 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.12 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.9.12.10 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | PHP 8.5 Backports | ||||
| Description: | Compatibility improvements on the master branch will need to be backported for branch 1.9.12. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 876 | [XMB1] Research Tasks | minor | N/A | 2025-12-24 12:05 | 2025-12-24 12:05 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.10.03 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | PHP 8.6 Compatibility | ||||
| Description: |
Items expected to affect XMB compatibility with PHP 8.6: Type casting a string that contains alphanumeric data will cause an error. No more (int) '56 stuff' allowed. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | https://wiki.php.net/rfc/deprecate-fuzzy-and-null-casts | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 873 | [XMB1] New Features | feature | N/A | 2025-12-22 10:47 | 2025-12-22 10:47 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Session Token Encryption | ||||
| Description: |
v1.9.12 brought us session tokenization and v1.10 brought us good improvements for password hashing. Now we need to go a step further and protect session token storage so that any kind of database exposure would not facilitate authentication by a 3rd party. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 872 | [XMB1] New Features | feature | have not tried | 2025-12-21 09:08 | 2025-12-21 09:08 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Asynchronous Mail Delivery | ||||
| Description: | The Symfony mailer causes significant page load delays when using SMTP. Need to add asynchronous delivery for most situations. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 870 | [XMB1] New Features | feature | N/A | 2025-12-19 06:22 | 2025-12-19 06:22 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Attachment Search for Orphaned Files | ||||
| Description: | The attachment search feature does a reasonable job of representing orphaned objects (files that have no associated post in the forums). However, there is no option to specifically find orphaned attachments only. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 867 | [XMB1] Bugs | minor | sometimes | 2025-12-18 20:12 | 2025-12-18 20:13 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.9.12.10 | ||||
| MySQL Version: | |||||
| PHP Version: | 8.5 | ||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Relative paths not working in imagefttext() | ||||
| Description: |
I've been unable to verify if this is a PHP issue or a host configuration issue, but switching between PHP 8.4 and 8.5 causes these errors to show up: [18-Dec-2025 19:15:32 America/Los_Angeles] PHP Warning: imagefttext(): Could not find/open font in include/attach.inc.php |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 865 | [XMB1] Bugs | tweak | sometimes | 2025-12-18 19:33 | 2025-12-18 19:33 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.12 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.9.12.10 | ||||
| MySQL Version: | |||||
| PHP Version: | 8.5 | ||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Function imagedestroy() is deprecated | ||||
| Description: | [18-Dec-2025 19:07:44 America/Los_Angeles] PHP Deprecated: Function imagedestroy() is deprecated since 8.5, as it has no effect since PHP 8.0 | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 807 | [XMB1] New Features | feature | N/A | 2025-07-05 23:11 | 2025-09-22 10:28 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | high | OS Version: | |||
| Status: | confirmed | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | UTF-8 Schema | ||||
| Description: |
The diverse string formats in the schema are one of the last things still driving me crazy in terms of maintaining this code base. This is the path forward: Convert all "double-slashed" strings to unslashed strings, no exceptions. Start brainstorming tools and procedures for conversion to UTF-8 encoding. If helpful, add schema columns that would aid the encoding conversion. Update page headers and templates with the new charset. Start addressing PHP charset use and any security implications. Create new translation files. Determine if non UTF-8 encodings will be supported or dropped completely. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: |
https://docs.xmbforum2.com/index.php?title=XMB_1.9.12_Schema_String_Audit Also note the bbrulestxt setting is still saved as raw HTML. |
||||
| Attached Files: | |||||
| Notes | |
|
(0000582)
miqrogroove 2025-07-14 23:22 |
I took a deep dive into the schema issues tonight. The good news is that the ISO-8859-1 languages can be converted in place using MySQL statements. All of the other languages have been assigned the 'latin1' charset in the schema out of convenience and will have to be converted to binary data types to avoid being interpreted incorrectly when reassigning the correct charset. The bad news is that we also have a Finnish language translation encoded as ISO-8859-10 which is not supported in MySQL. To support those data in the upgrader, we will have to convert them in the PHP layer and update all of the binary values with UTF-8 equivalents before reassigning a utf8mb4 charset. |
|
(0000583)
miqrogroove 2025-07-15 14:26 |
Extra consideration: The existing upgrader is built on latin1 charset connections. It will need to set and update the connection charset between schema versions. |
|
(0000592)
miqrogroove 2025-09-03 13:59 |
Extra consideration: Any password that currently contains an off-page code point might actually be received with HTML character entity references of which the user is unaware. Switching the input encoding to UTF-8 will effectively invalidate those passwords. Likewise, any on-page code point greater than 0x7F in the input will be explicitly re-encoded for UTF-8, and this will also have the effect of breaking many non-English passwords. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 421 | [XMB1] Research Tasks | minor | N/A | 2011-01-14 16:52 | 2025-09-20 06:43 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | LIMIT start, ppp Does Not Scale Well | ||||
| Description: |
During optimization testing on Exhale, I found that the LIMIT command runs about 10 times faster using an index instead of the table data. Thus, we now have two queries instead of one when we need to query paged information. The remaining problem is that this wont be helpful for a forum that grows 10 times larger than Exhale. If a forum had on the order of 10^6 threads or if a thread had 10^6 replies, then even the index scan would become rather onerous for the sake of locating page boundaries. It may be worth researching alternative strategies for paging information with greater magnitude. It may not be compatible with XMB 1.9.11, but it would be nice to know what direction these optimizations will take in the future. Partitioning? Stats tables? Views? |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000283)
miqrogroove 2011-01-15 13:06 |
Here is a post confirming the behavior, but does not really offer an alternative strategy for locating an offset. http://forums.mysql.com/read.php?24,112440,112461 |
|
(0000284)
miqrogroove 2011-01-15 13:22 |
This post has a nice discussion, basically concluding that every situation requires a different strategy. http://www.mysqlperformanceblog.com/2006/09/01/order-by-limit-performance-optimization/ |
|
(0000285)
miqrogroove 2011-01-15 13:45 |
This one by Yahoo basically says don't do what we are trying to do :) http://www.scribd.com/doc/14683263/Efficient-Pagination-Using-MySQL |
|
(0000286)
miqrogroove 2011-01-15 14:53 |
My conclusion so far is that we would have to maintain stats tables for key distribution data. It seems like that shouldn't be necessary, but here's how it would work: Without a specific WHERE condition, the best index scan rate I've seen is 300,000 rows in 0.1 sec. Let's assume a fixed time of 0.0000003 per row. SELECT dateline, pid FROM xmb_posts WHERE tid=288108 ORDER BY dateline ASC, pid ASC LIMIT 300000, 1 If we have a table identifying a key value (date) for each 1,000 rows in the table, then we could query that table to find any record within a range of 1,000 records. In theory, MySQL would be able run the resulting WHERE condition in just 0.0003 sec regardless of how many rows are in the table. This is essentially an index on an index. The above query returned dateline = 1238176252 so what would happen if... SELECT dateline, pid FROM xmb_posts WHERE tid=288108 AND dateline > 1238176252 ORDER BY dateline ASC, pid ASC LIMIT 1000, 1 Actual run time was 0.0008 :D |
|
(0000599)
miqrogroove 2025-09-20 06:43 |
It's time to consider this for v1.12. Also, I think there are good alternatives to stats tables that need to be considered. If the main issue is lack of indexed query criteria for page numbers, then we could just not use page numbers in URLs and queries. The existing lastpost column is too awkward for this, and autonumber fields are technically not appropriate, so what if we simply add a 'sort' column and assign serial numbers to each post in the same thread? This would give us all the advantages of speed in a single table and single query. The disadvantage is that it doesn't allow for graceful post deletion, unless we sacrifice the ability to display page numbers. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 858 | [XMB1] New Features | feature | have not tried | 2025-09-11 07:03 | 2025-09-11 08:28 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Input Font Should Be Configurable | ||||
| Description: | In the theme editor, we have only one font setting, whereas the CSS template uses hard-coded font-family for input elements to avoid using weird theme fonts for input. This needs to be easier to configure. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 857 | [XMB1] Bugs | minor | have not tried | 2025-09-10 06:25 | 2025-09-11 07:37 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Move Text Color to CSS | ||||
| Description: | Text color has been specified in HTML since XMB v1.1. This is confusing, inconsistent, and we're not sure if anyone distinguishes the body color from the table color. This needs to be moved to CSS and/or combined with the table text color setting. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 841 | [XMB1] New Features | feature | N/A | 2025-08-02 10:07 | 2025-09-10 06:49 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Whosonline Queries Can Be Less Frequent | ||||
| Description: |
Sending a DELETE query for every hit is not necessary and can be easily improved upon. Also, the thread SELECT queries can be consolidated for faster loading of misc.php?action=online |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 856 | [XMB1] Bugs | minor | have not tried | 2025-09-10 06:10 | 2025-09-10 06:10 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Header 'pluglinks' Should Have a Default / Themeable Icon Setting | ||||
| Description: | Using a fixed filename in config.php makes the pluglink icons somewhat incompatible with the theme system. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 850 | [XMB1] New Features | feature | N/A | 2025-09-05 22:17 | 2025-09-08 08:25 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Improve the search functionality | ||||
| Description: |
Right now all it does is take the input and look for anything matching it. Searching "the", for instance, will return every instance of the string "the", including sub-words. It'd be nice to be able to do more conditional searching and whatnot. Perhaps even something more exciting could be integrated - I'm not sure what's available, but maybe there's some sort of more "intelligent" search library we could be using. Writing our own is probably going to be difficult to get right. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 849 | [XMB1] Bugs | minor | have not tried | 2025-09-05 22:04 | 2025-09-08 08:24 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | member profile fields can't contain emoji | ||||
| Description: |
This not only breaks fringe cases like emoji URLs but also possibly breaks things like passwords too. Worth checking with non-emoji non-latin1 chars too for sanity's sake too because this could be more major then we realise. http://�.to is an example of a emoji URL |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000593)
flushedpancake 2025-09-05 22:04 |
Lol and of course the bug tracker doesn't like the emoji. Derp. It's a duck emoji. Unsurprisingly. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 832 | [XMB1] Bugs | minor | have not tried | 2025-07-28 09:28 | 2025-09-05 22:07 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Why Does the 'Use Signature' Option Even Exist? | ||||
| Description: |
With the update of all posts occurring by default... for which we have a setting: Should "use signature" in existing posts be automatically reset when the signature is removed and/or readded? Then what is even the purpose of having a "Use Signature" option? If a user deletes their signature with the admin setting enabled, then all of the "Use Signature" values are removed, making them meaningless. If a user deletes their signature with the admin setting disabled, then all of the "Use Signature" values are meaningless because there is no signature to use. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000594)
flushedpancake 2025-09-05 22:07 |
The admin setting seems kinda pointless if you ask me... |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 833 | [XMB1] New Features | feature | N/A | 2025-07-28 11:19 | 2025-07-28 11:19 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | "Your Personal Features" bar Should be Optional or Removed | ||||
| Description: | The "Your Personal Features" bar really clutters up the front page and isn't very useful. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 821 | [XMB1] New Features | minor | have not tried | 2025-07-20 15:16 | 2025-07-20 15:16 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Change Table Width to Body Width | ||||
| Description: |
The use of identical width attributes on every child of the page body is really pointless. All we need to do is make this a few line items of CSS and then mass remove this variable from all the other templates. Testing in Firefox shows we can use this: body { width: <?= $THEME['tablewidth'] ?> margin-left: auto; margin-right: auto; } |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 665 | [XMB1] Bugs | tweak | always | 2021-06-15 00:29 | 2025-07-19 11:19 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | 7.4 | ||||
| Web Server: | Apache | ||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | u2u subject is truncated where it exceeds the u2u table subject column setting | ||||
| Description: |
u2u table, subject column If subject exceeds table subject setting when sending a u2u, MySQL generates a warning [when debug is on]: 'Message' => 'Data truncated for column \'subject\' at row 1', Perhaps the code from post.php for handling where subject is > table subject setting field length could be repurposed/recycled into u2u code. |
||||
| Tags: | |||||
| Steps To Reproduce: | Send a u2u with a subject in excess of the table subject setting. | ||||
| Additional Information: | |||||
| Attached Files: |
oh god.png (135,058 bytes) 2024-04-21 22:11 https://bugs.xmbforum2.com/file_download.php?file_id=47&type=bug |
||||
| Notes | |
|
(0000451)
flushedpancake 2024-04-05 21:36 |
I'm wondering if this could potentially cause PMs to fail to send without any "notice" to the user depending on the DB's configuration, come to think about it. This could actually be more of an issue than it looks to be at the moment given the lack of proper error handling. |
|
(0000452)
flushedpancake 2024-04-05 21:40 |
Yep, just checked and if strict mode is turned on (which is actually the default ever since MySQL 5.7/8.0+ and MariaDB 10.2+ I believe), you'd instead get a "data too long" error and the U2U would fail to send. Running debug mode on production and exposing errors to users is also... less than ideal, too. |
|
(0000492)
miqrogroove 2024-04-20 17:13 |
There are a bunch of different issues here. Mainly, XMB needs stronger input validation. This problem applies to every database field that accepts user input. They can all throw the same warnings and errors. The MySQL server we are using here does not have strict mode enabled. It can be switched at runtime for testing, but I don't think it's a huge issue. The error handling was already addressed in 0000685. Patching the U2U subject and body fields might be adequate for now, but I think this issue should be examined more before doing that. |
|
(0000496)
flushedpancake 2024-04-21 22:00 |
With strict mode enabled it just outputs a data too long error (if I'm remembering right) in debug mode, or silently fails in non-debug mode. Tbh the fact the software even holds up so well DB-compatibility aside from a rather minor issue is actually really impressive, I've seen more active projects that would break entirely when STRICT_TRANS_TABLES was made default mode in MySQL 5.7/MariaDB 10.2 |
|
(0000497)
flushedpancake 2024-04-21 22:11 |
Correction. It truncates the subject even in strict mode. However, the limit being so liberal also allows you to do stuff like this, which isn't particularly ideal especially on mobile devices. |
|
(0000507)
miqrogroove 2024-04-24 08:53 |
That screenshot is off topic. We already have input validation for that one. |
|
(0000508)
miqrogroove 2024-04-24 09:04 |
Best examples are the AIM field (40 chars) and the bday field (10 chars). For some reason it's still possible to input a year greater than 9999. We only filter years less than 1900. |
|
(0000509)
flushedpancake 2024-04-24 15:22 |
I mean, the AIM field can be axed at this point, given AIM is dead. Fair enough, though. |
|
(0000587)
flushedpancake 2025-07-19 11:19 |
Is this still an issue on the latest build or have recent mysql changes fixed it? Implementing a check against the length of the title might still be worth doing, as some people still have a habit of turning strict_trans_tables OFF. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 65 | [XMB1] New Features | feature | N/A | 2008-07-22 05:43 | 2025-07-19 11:04 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | high | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | redesign | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | mundoo | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Limit Signature Size | ||||
| Description: |
I am wondering if it will be possible to have a restriction in size of the signature area? Often the signature is larger than the actual message and can overpower a thread when you have many members using that area with huge graphics and lists etc. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=772419 | ||||
| Attached Files: | |||||
| Notes | |
|
(0000585)
flushedpancake 2025-07-19 11:04 |
A reasonable size would be -four text lines, max 255 chars (not including bbcode markup) -images no taller than 192px |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 817 | [XMB1] New Features | feature | N/A | 2025-07-17 11:50 | 2025-07-17 11:50 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Site Health Panel | ||||
| Description: | Would like ability to view phpinfo() output, as well as stats with feedback about overall operation. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 813 | [XMB1] Bugs | minor | always | 2025-07-12 07:58 | 2025-07-17 11:41 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | confirmed | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | flushedpancake | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | GIF Format Lock-in | ||||
| Description: |
There are some GIF-specific filenames hard coded in XMB, which becomes problematic for any theme developer. Examples: pollbar.gif in viewthread. star.gif in ThreadRender, member profiles, and the FAQ. top/untop/folder (various) in forumdisplay and Core. All of the header link icons, now in BootupLoader. BBCode icons. U2U navigation icons. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | https://forums.xmbforum2.com/viewthread.php?tid=777210 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 816 | [XMB1] Bugs | minor | sometimes | 2025-07-16 18:12 | 2025-07-17 08:30 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | miqrogroove | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | resolved | Product Version: | 1.9.12 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 1.9.12.10 | ||
| Target Version: | 1.9.12.10 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | https://github.com/miqrogroove/xmb/commit/96cb996a3b1980a042209b1c476e91acff7dd044 | ||||
| Summary: | Upgrader Login Form Doesn't Work With 1.9.12 Schema | ||||
| Description: |
Mismatched input names prevent the upgrade login screen from working after upgrading to 1.9.12.00 or later. So, trying to re-run the upgrade causes the symptoms. This does not affect upgrading from 1.9.11 to 1.9.12. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000584)
miqrogroove 2025-07-16 18:55 |
This is now patched for the master branch only. Needs work. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 810 | [XMB1] New Features | minor | N/A | 2025-07-10 07:24 | 2025-07-15 06:36 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Adopt the Symfony Translate API | ||||
| Description: |
XMB needs a translation system for template variables, plural phrases, and extensibility. Symfony is one of the better options. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | https://forums.xmbforum2.com/viewthread.php?tid=777202 | ||||
| Attached Files: | |||||
| Notes | |
|
(0000574)
miqrogroove 2025-07-12 18:07 |
Folks at Weblate indicated we might qualify for translation hosting with them. There's a message in my emails from 7/10/2025. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 792 | [XMB1] Bugs | minor | have not tried | 2025-05-21 07:31 | 2025-07-13 19:47 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Review pid BBCode | ||||
| Description: | This area of bbcode needs improvement. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | https://github.com/miqrogroove/xmb/pull/4 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 814 | [XMB1] New Features | feature | N/A | 2025-07-13 06:55 | 2025-07-13 06:55 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Consider Switching to IntlDateFormatter | ||||
| Description: | Date translation was broken prior to v1.10. The fixed version only translates one code for the full month name, and doesn't touch any abbreviations or days of week. It might be appropriate to switch away from gmdate() for date formatting and use the IntlDateFormatter feature instead. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 809 | [XMB1] New Features | feature | N/A | 2025-07-08 08:52 | 2025-07-08 08:52 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Add Turnstile as extra 3rd-Party bot protection | ||||
| Description: | The Cloudflare Turnstile alternative to traditional captcha seems like a good competitor to reCAPTCHA, and currently more committed to a free tier instead of a quota billing system. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 770 | [XMB1] Bugs | tweak | always | 2025-03-25 21:33 | 2025-07-05 23:19 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Stop using popups | ||||
| Description: | The U2U system and related features should use tabs or normal links instead of popups. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 751 | [XMB1] New Features | feature | N/A | 2025-01-02 15:13 | 2025-07-05 23:18 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Reactions to Posts | ||||
| Description: | Facebook started it. GitHub has it. Teams has it. Implementation isn't too complicated. Let's consider adding a reactions feature. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 760 | [XMB1] New Features | feature | N/A | 2025-02-09 12:43 | 2025-07-05 23:17 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Favorite status should be displayed on threads | ||||
| Description: | After adding a favorite or a subscription, there is no visible change to the thread view. This should be more dynamic for ease of use. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 662 | [XMB1] New Features | feature | have not tried | 2021-05-02 08:00 | 2025-07-05 23:14 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | 1.12.00 | ||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Add Sitemap Feature | ||||
| Description: | The latest version of the Sitemap hack is relatively mature and could be included in a future XMB patch. | ||||
| Tags: | SEO | ||||
| Steps To Reproduce: | |||||
| Additional Information: | https://forums.xmbforum2.com/viewthread.php?tid=777110 | ||||
| Attached Files: | |||||
| Notes | |
|
(0000445)
flushedpancake 2024-04-03 12:46 |
I second this idea :) |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 778 | [XMB1] New Features | feature | have not tried | 2025-04-07 07:17 | 2025-06-25 06:43 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | There's no clear way to see post IDs while reading a thread | ||||
| Description: |
https://forums.xmbforum2.com/viewthread.php?tid=777197&goto=search&pid=1376661 The only reason I'm even able to tell that's post #137661 is because I copypasted the thing at the top where it says "posted on 6.4.2025 at 07:58" into the address bar of my phone. Being able to actually visually see what a post's ID is would make it a lot easier when using the "pid" tag for instance, you could just write the number out that way rather than needing to copypaste a URL. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000551)
flushedpancake 2025-04-07 07:18 |
I meant to mark this as trivial |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 606 | [XMB1] New Features | minor | have not tried | 2020-09-19 19:49 | 2025-04-08 11:40 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Custom navigation links via Admin panel rather than config.php | ||||
| Description: |
As per https://forums.xmbforum2.com/viewthread.php?tid=777074 perhaps a more user friendly interface for additional custom navigation links via Admin panel rather than config.php |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000558)
miqrogroove 2025-04-08 11:40 |
Without regard to any priority, I think in general, it would be a good plan to eliminate as many parts of config.php as possible. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 712 | [XMB1] Bugs | minor | N/A | 2024-05-02 16:46 | 2025-04-08 11:39 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | 1.9.8 SP2 | ||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | Apache | ||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Replace 'directory-blocking' index.htm's with a .htaccess in the root | ||||
| Description: |
Said .htaccess just needs to have this content: 'Options -Indexes' - having a directory-blocking 'index.html' in every single directory is pointless duplication at best, and doesn't properly return the relevant HTTP code (403) that is wanted for system directories. For the case of certain directories, i.e. where file uploads (e.g. uploaded attachments, custom avatars) go, an additional .htaccess file with this content: 'php_admin_flag_engine=Off' should be somewhere in there to prevent PHP parsing the contents of the directory when accessed. This may help to avoid certain exploits involving embedded PHP in otherwise innocuous-seeming user-submitted data from ever being parsed. If the intent is to keep the fancy 'forbidden directory' message, adding an additional .htaccess in each system directory (but not subdirectory, so say, images/ but not images/davis) with the contents 'ErrorDocument 403 'The required libraries have not been defined.'' or whatever it is would suffice here. Hopefully my wording isn't too awkward here. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000515)
miqrogroove 2024-06-01 07:05 |
Sounds like a hack for Apache users. I'm not saying the index.html files are totally necessary, but substituting an Apache-specific solution isn't my first choice. |
|
(0000516)
miqrogroove 2024-06-03 07:37 |
There are currently 12 copies of index.html. None of them appear to be necessary. I would think they only really hide some version hints under /include and /db. |
|
(0000517)
flushedpancake 2024-06-18 01:29 |
I'd just remove them and write some small documentation on how to configure the web server not to display the contents of board-related directories and to not execute PHP code in directories where it shouldn't do so like the ones for uploaded file storage. :P |
|
(0000533)
miqrogroove 2024-12-22 16:22 |
I learned today, almost by mistake, that in some environments a simple "chmod 770" at the directory level will block web requests and still allow PHP inclusion. This solution might be more portable than the htaccess file. |
|
(0000557)
miqrogroove 2025-04-08 11:39 |
One other possibility is to replace the html files with php files. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 779 | [XMB1] New Features | feature | N/A | 2025-04-07 07:26 | 2025-04-08 06:58 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Multiquote? | ||||
| Description: |
https://forums.xmbforum2.com/viewthread.php?tid=777197&goto=search&pid=1376661 Quoting multiple posts currently requires you to go back to the thread, quote the post in a new tab, and then copy and paste the quote box into the reply you were writing. This is cumbersome at best: irritating at worst. A multiquote like many other forum software have these days could be useful to alleviate this. This would require an extra button, as well as adding a quote button on the new reply page, so you can quote posts from the "recent posts overview" thingy in a thread too. :) |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 768 | [XMB1] New Features | feature | N/A | 2025-03-20 02:18 | 2025-03-20 02:18 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | flushedpancake | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Unify Quote and rQuote BBCodes | ||||
| Description: |
Is there any need to separate the two? Using quote with parameters messes up my post |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | https://forums.xmbforum2.com/viewthread.php?tid=777195 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 736 | [XMB1] Research Tasks | feature | have not tried | 2024-12-24 06:24 | 2024-12-24 06:24 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | none | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Passkey Authentication | ||||
| Description: | I'm interested in the new passkey system that pops up in places like Github. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 722 | [XMB1] Research Tasks | feature | N/A | 2024-12-01 07:09 | 2024-12-01 07:25 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | How to Mitigate TLS Inspection | ||||
| Description: |
TLS Inspection is a potential threat to all web servers and to any client not administered by the end user. For example, the user of a computer at work or at a library might not realize the client's root trust list has been compromised. The result of a TLS Inspection deployment is that the TLS channel cannot be trusted at either end, and is effectively not confidential. This exposes passwords, session cookies, and all other data on the wire. Unfortunately, this is almost entirely beyond the control of the end user, and next to impossible to detect at the server. At the scripting level, almost nothing can be done short of redundantly implementing full asymmetric cryptography for both the client and server. At the transport level, the obvious remedy is something like Apache's `SSLVerifyClient require` directive. But this means a full PKI deployment to end users, just to protect confidentiality at the server level. It also implies end users would be tied to their own devices or risk trying to use personal certificates on foreign clients. To further complicate matters, the certificates would have to be tied to each user's account so that one user couldn't proxy traffic for another. This is a systemic risk to the whole Internet, but I am interested in any practical mitigation. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 716 | [XMB Hacks 1.9.x] | crash | always | 2024-09-01 19:39 | 2024-09-01 19:39 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | member-approval-1.4 in member.php results in HTTP ERROR 500 upon registration | ||||
| Description: |
Member experiencing HTTP ERROR 500 on registration attempts: https://forums.xmbforum2.com/viewthread.php?tid=777171 Deduced it is the member-approval-1.4.zip mod Perhaps the mod spamhammer should be used instead Did see potential issues in the install notes - Find Code Near Line 622: altMail doesn't exist, xmb_mail does The line below references $locationnew, not sure if this should be $location $adminmessage = "$username has just registered on $dbboardname.\r\n\r\n[b]Registration Details:[/b]\r\n\r\nUsername: $username\r\nE-mail: $email\r\nLocation: $locationnew\r\nSite: $site\r\nAIM: $aim\r\nICQ: $icq\r\nMSN: $msn\r\nYahoo: $yahoo\r\nBio: $bio\r\nSig: $sig\r\n\r\n[url={$full_url}cp.php?action=approve&member=".recodeOut($username)."]Approve this user account[/url]"; |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 512 | [XMB Hacks 1.9.x] | minor | have not tried | 2017-12-20 06:25 | 2024-05-28 04:46 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | miqrogroove | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | resolved | Product Version: | |||
| Product Build: | Resolution: | unable to reproduce | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Moderation Panel Malfunction | ||||
| Description: | The moderation system on xmbforum2.com is showing an incorrect post count. It would be nice if this could be resolved automatically in the future. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 711 | [XMB Hacks 1.9.x] | crash | always | 2024-05-02 16:24 | 2024-05-03 12:09 |
| Reporter: | flushedpancake | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Avatar upload hack no longer works | ||||
| Description: |
Not only does trying to do svn patch not work (it creates broken php files and rejects the whole patch which is annoying), but trying to manually add the stuff just comes up a blank screen. Also the instructions for cp.php refer to lines which no longer exist in the cp.php file it seems. I'm not at my main pc at the moment and I forgot to turn error display back on on localhost after reinstalling linux so I'll fetch that in a bit. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000510)
flushedpancake 2024-05-02 16:29 |
Some other notes: -the avatar uploader doesn't allow you to use 'jpeg', 'jpe' or 'jfif' as an extension, which are perfectly valid JPEG formats (the first one of which is seen on iOS) -webp support should probably be added as the avatar url can handle it just fine -the token it uses is extremely insecure (md5 hashing the username? really?) -for some odd reason, it allows uploading BMP files which won't even be displayed by the browser anyways and will take lots of space up on the server -it should probably do checks if the gd extension is installed and whether the folder is writable - if both of these fail, fallback to the url system instead I shouldn't ramble on too much about the issues, though |
|
(0000511)
flushedpancake 2024-05-03 12:07 |
This makes even less sense now I turned on error display... require ROOT.'include/attach.inc.php'; $attachlimits = ' '.$lang['attachmaxsize'].' '.getSizeFormatted($SETTINGS['maxattachsize']).'. '.$lang['attachmaxdims'].' '.$SETTINGS['max_image_size'].'.'; |
|
(0000512)
flushedpancake 2024-05-03 12:08 |
Also, this causes a crash too: // Avatar Upload Translation if (!isset($lang['avatar_upload'])) { require_once(ROOT.'include/translation.inc.php'); setNewLangValue('avatar_upload', 'Upload Avatar:'); loadLang($langfile); eval($lang['evaloffset']); } However, the code still works properly with the 'eval' removed from what I can tell |
|
(0000513)
flushedpancake 2024-05-03 12:09 |
Oh I forgot to mention that the actual php error in comment 511 is 'call to undefined function'. You know, right after the line telling the system to require the file that includes that very function. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 670 | [XMB Hacks 1.9.x] | minor | have not tried | 2023-07-20 06:56 | 2024-04-03 14:07 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Sitemap: MySQL 8.0 Deprecated: User variables within expressions | ||||
| Description: |
[16-Jul-2023 16:33:13 America/Los_Angeles] MySQL generated 2 warnings in the following query: SELECT * FROM ( SELECT tid, thedate, pages, @running_pages:=@running_pages + pages AS running_pages FROM ( SELECT tid, SUBSTRING_INDEX(lastpost,'|',1) AS thedate, CEIL( (replies + 1) / 20 ) AS pages FROM xmb_threads WHERE fid IN(1, 468, 469, 29, 21, 105, 440, 353, 442, 431, 447, 349, 348, 441, 322, 427, 426, 355, 425, 420, 419, 391, 382, 462, 389, 422, 358, 424) AND closed NOT LIKE 'moved|%' ) AS t CROSS JOIN ( SELECT @running_pages:=0 ) AS init ORDER BY tid ) AS allthreads LIMIT 50000 array ( 'Level' => 'Warning', 'Code' => '1287', 'Message' => 'Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: \'SET variable=expression, ...\', or \'SELECT expression(s) INTO variables(s)\'.', ) array ( 'Level' => 'Warning', 'Code' => '1287', 'Message' => 'Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: \'SET variable=expression, ...\', or \'SELECT expression(s) INTO variables(s)\'.', ) |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 663 | [XMB1] New Features | feature | N/A | 2021-05-02 09:36 | 2021-05-02 09:36 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | HiDPI Theme Images | ||||
| Description: | It would be nice to enable HiDPI theming if it can be used as easily as adding new image files. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 609 | [XMB1] New Features | feature | N/A | 2020-09-20 08:18 | 2020-09-20 15:28 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Context-Sensitive Login | ||||
| Description: | It is always a nice feeling to go back to the referring page after login. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| Notes | |
|
(0000417)
lottos 2020-09-20 15:28 |
Yes! |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 489 | [XMB1] Bugs | tweak | sometimes | 2012-01-30 15:42 | 2020-09-18 16:10 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Who's Online Optimization | ||||
| Description: |
Saves 1 query: For the majority of forums, $count < $tpp, and $page < 2, therefore it is not necessary to query $count at all unless $page isset, or the query returns $tpp rows. Larger issue: The who's online page seems to use 1 query for each user who is viewing a thread. This shouldn't be needed. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum2.com/viewthread.php?tid=776654 | ||||
| Attached Files: | |||||
| Notes | |
|
(0000375)
miqrogroove 2017-12-28 06:58 |
Punting as low priority. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 569 | [XMB1] New Features | feature | N/A | 2020-09-02 14:57 | 2020-09-02 14:57 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Reported Posts: add note to the post | ||||
| Description: |
Reported Posts: - add an Admin setting that allows text along the lines of 'post has been reported' to the actual post or add a new post to the topic/thread [that can be removed later] so that members can see it's already been reported and so hopefully multiple members don't report the same post. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 535 | [XMB Hacks 1.9.x] | minor | have not tried | 2018-02-07 12:54 | 2018-02-07 12:54 |
| Reporter: | lottos | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Shop Hack installation Error | ||||
| Description: |
Member alkutob reports that: "I am using xmbforum 1.9.11.15 My server mysqld Ver 5.7.21-0ubuntu0.16.04.1 I tried to install xmb_shop_3.4 on my forum but still get the same error . The installation process freezes on the Checking for: `money`..... and never continue. I changed TYPE=MyISAM to ENGINE=MyISAM and had the same result" from https://forums.xmbforum2.com/viewthread.php?tid=777018 |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 91 | [XMB1] New Features | feature | N/A | 2008-08-01 14:35 | 2011-11-08 17:52 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | suspended | |||
| Projection: | major rework | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Implement Full-Text Indexing | ||||
| Description: |
I just realized XMB is using table scans to perform searches. D: |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: |
Typical result of EXPLAIN id select_type table type possible_keys key key_len ref rows Extra 1 SIMPLE p ALL tid NULL NULL NULL 10 Using where; Using temporary; Using filesort 1 SIMPLE t ALL PRIMARY NULL NULL NULL 4 Using where 1 SIMPLE f eq_ref PRIMARY PRIMARY 2 t.fid 1 See Also http://forums.xmbforum.com/viewthread.php?tid=773516 |
||||
| Attached Files: | |||||
| Notes | |
|
(0000009)
miqrogroove 2008-08-01 14:40 |
If we want to keep the table scan mode for short words then modes can be switched using the result of... SHOW variables WHERE variable_name = 'ft_min_word_len' |
|
(0000066)
miqrogroove 2008-11-16 19:35 |
More about our problem and why changes are needed: The existing XMB search feature, which is based on a table scanning algorithm, appears to run quickly due to the use of a LIMIT clause. However, search performance falls off dramatically when searching for a more-rare keyword. As the prevalence of the keyword decreases, the portion of the xmb_posts table that must be scanned increases. This creates a situation where searching for a keyword that cannot be found (a long random string) causes the database engine to scan the body of every post in the database. A full-text indexing strategy would give us the opposite result: Searching for a keyword that could not be found would result in the fastest possible SQL processing time of any search. This is because the database engine would be able to return an empty set from the index without even touching the table. |
|
(0000074)
miqrogroove 2008-11-22 16:05 |
Due to complications with the old upgrade.php utility, this feature will not be practical in the next version. Leaving open as a candidate for any future releases. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 479 | [XMB Hacks 1.9.x] | @0@ | @0@ | 2011-07-17 10:16 | 2011-07-17 10:16 |
| Reporter: | dessiebarnett239 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | mobile access | ||||
| Description: | is there going to be an option for direction connection via a web app like http://www.free-iphone-apps.com or even a native app. are there any plans? | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 478 | [XMB Hacks 1.9.x] | @0@ | @0@ | 2011-07-15 23:30 | 2011-07-15 23:30 |
| Reporter: | ssullivan466 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Interface bug | ||||
| Description: | the cancel button is not shown anywhere! just http://www.google.com it! | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 21 | [XMB1] New Features | feature | N/A | 2008-07-21 21:59 | 2011-04-24 12:09 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | high | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | major rework | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Send Subscription Notices When Topicadmin Actions Occur | ||||
| Description: | Especially on Merge, Move, and Split actions, the participants should be informed of what is happening to their posts. This could be implemented as a bit field in the settings table where each action has an on/off bit. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: |
http://forums.xmbforum.com/viewthread.php?tid=765189 http://forums.xmbforum.com/viewthread.php?tid=775618 |
||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 422 | [XMB1] Research Tasks | tweak | have not tried | 2011-01-15 20:06 | 2011-01-15 20:06 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Run Thread Query in Reverse? | ||||
| Description: | I was just thinking, the last page in a thread is commonly visited. It might make more sense to reverse the sort order when displaying that page. It's an idea to be explored. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 409 | [XMB Hacks 1.9.x] | minor | have not tried | 2011-01-04 11:41 | 2011-01-04 11:41 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Portal Using Invalid Location Headers | ||||
| Description: |
I just saw a board's front page emitting Location: portal.php This is an invalid header for HTTP. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 405 | [XMB Hacks 1.9.x] | major | always | 2010-12-23 00:53 | 2010-12-23 00:53 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | 3.0 | Resolution: | open | ||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Shop Permissions Are Messed Up | ||||
| Description: | When a shop category is created, the owner/creator cannot add items. No additional menu appears. Admins can add items etc. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: |
http://forums.xmbforum.com/viewthread.php?tid=775529&goto=search&pid=1369358 In my experience, the owner/creator stuff doesn't work. When Category Access is granted to Members, anyone can create categories and add items. I'm also guessing anyone can edit items, although the link for that doesn't appear consistently. I'm also guessing the ACLs never work and the code is generally impossible to read. |
||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 324 | [XMB1] New Features | feature | N/A | 2009-03-25 01:57 | 2009-03-25 01:59 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | blackvara | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Full Posts Option in Search | ||||
| Description: |
Hi, I think something is wrong in the search result. While the result is with the BB-Code and it looks not nice. It must be possible to do it with the forum format that you can see color and so on. br Peter |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=774279 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 64 | [XMB1] New Features | feature | N/A | 2008-07-22 05:40 | 2009-01-02 07:30 |
| Reporter: | Mouser | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | major rework | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Display Multiple "codes" for 1 smilie | ||||
| Description: | Group codes together by image, to be more visually pleasing. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=772422 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 204 | [XMB Hacks 1.9.x] | minor | have not tried | 2008-12-07 09:15 | 2008-12-07 09:15 |
| Reporter: | kuba1 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Spoiler Hack Undefined Variable imgdir | ||||
| Description: |
Line 506 of functions.inc.php img src="\'.$imgdir.\'spoiler.gif" |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 202 | [XMB Hacks 1.9.x] | minor | have not tried | 2008-12-05 06:55 | 2008-12-05 06:55 |
| Reporter: | kuba1 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | Timezone Error in Birthday Hack | ||||
| Description: |
i recently installed the birthday hack but i get this error message on my index page Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /home/rbdrocks/public_html/index.php on line 257 |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 185 | [XMB Hacks 1.9.x] | minor | have not tried | 2008-11-30 10:25 | 2008-11-30 10:25 |
| Reporter: | kuba1 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | You tube and Google video bbcode | ||||
| Description: |
Cancelling places [google]null[/google] in post text. Check these hacks for the presence of: } else { text = prompt(bbcode_prompt_song,"Song File URL (http://)"); if (text != null) { AddText("\r\n"+'[song]', '[/song]'+"\r\n", text, messageElement); } } |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | if (text != null) { (is missing) | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 183 | [XMB Hacks 1.9.x] | minor | have not tried | 2008-11-30 10:11 | 2008-11-30 10:11 |
| Reporter: | kuba1 | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| Summary: | SP3 Users viewing page does not follow invisible user rules. | ||||
| Description: |
http://forums.xmbforum.com/viewthread.php?tid=773518 Summary Explains the issue |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 37 | [XMB1] New Features | feature | N/A | 2008-07-22 00:26 | 2008-11-26 18:09 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | redesign | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | dolphin678 | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Forumdisplay Sort Options | ||||
| Description: | Is there any chance of increasing the sort options to include "by thread title" by "poster" by "replies" etc. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=764584 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 66 | [XMB1] New Features | feature | N/A | 2008-07-22 05:46 | 2008-11-26 18:07 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | redesign | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Schema Updates | ||||
| Original Reporter: | mundoo | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Folders For Favorite Threads | ||||
| Description: |
Is there a way of being able to sort or create folders for members Favourites list so they can organise their favourites how they want? The U2U system allows you to create folders to sort U2U's into and our members with large Favourites lists want to be able to sort them as well. |
||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=772421 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 113 | [XMB1] New Features | feature | N/A | 2008-08-12 16:00 | 2008-11-26 18:04 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | new | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | |||||
| Original Reporter: | |||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Custom Permissions Fields | ||||
| Description: | We need to expand the forum permissions API to include non-forum features in which hacks and mods need to rely on user status. In other words, how does hack x add a permissions field to perform action z within the hack? | ||||
| Tags: | API | ||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |
| View Issue Details | |||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 41 | [XMB1] New Features | feature | N/A | 2008-07-22 00:58 | 2008-11-26 18:03 |
| Reporter: | miqrogroove | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | low | OS Version: | |||
| Status: | acknowledged | Product Version: | |||
| Product Build: | Resolution: | open | |||
| Projection: | redesign | ||||
| ETA: | none | Fixed in Version: | |||
| Target Version: | |||||
| MySQL Version: | |||||
| PHP Version: | |||||
| Web Server: | |||||
| Browser: | |||||
| Flags: | Javascript | ||||
| Original Reporter: | lottos | ||||
| SVN Revision: | |||||
| Git Commit: | |||||
| Summary: | Ajax Quick Reply | ||||
| Description: | After viewthread.php, post.php is the most used and resource hungry. Ajax quick reply: less cpu useage, less bandwidth, faster page loads = better forum user experience. | ||||
| Tags: | |||||
| Steps To Reproduce: | |||||
| Additional Information: | http://forums.xmbforum.com/viewthread.php?tid=765158 | ||||
| Attached Files: | |||||
| There are no notes attached to this issue. |