0031130: [Bug]Custom Fields show Bad Request. - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0031130	mantisbt	custom fields	public	2022-10-13 00:09	2022-11-25 13:40

Reporter	Passerby	Assigned To	dregad
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	no change required

Summary	0031130: [Bug]Custom Fields show Bad Request.
Description	Version：2.25.0~2.25.5 Passed Version：2.25.0~2.25.1 Failed Version： 2.25.2~2.25.5 PHP Version：7.2.2, 7.4.32, 8.0.1 Database: Mariadb 10.9 DB encode：utf8mb4_general_ci DB data import from MantisBT Ver.2.10.0 custom fileds failed with imported DB in Version 2.25.2~2.25.5 Even replace with new custom fields. Custom fileds from db generated by mantisbt 2.25 has no problem in any version.
Additional Information	Example Dockerfile： FROM php:7.4.32-apache RUN a2enmod rewrite RUN set -xe \ && apt-get update \ && apt-get install -y libpng-dev libjpeg-dev libpq-dev libxml2-dev libldap-dev libfreetype6-dev \ && docker-php-ext-configure gd --with-jpeg --with-freetype #RUN docker-php-ext-configure ldap --with-libdir=lib/x86_64-linux-gnu/ RUN docker-php-ext-install gd mysqli pgsql soap ldap ENV MANTIS_VER 2.25.5 ENV MANTIS_URL https://downloads.sourceforge.net/project/mantisbt/mantis-stable/${MANTIS_VER}/mantisbt-${MANTIS_VER}.tar.gz ENV MANTIS_FILE mantisbt.tar.gz ENV MANTIS_TIMEZONE Asia/Taipei RUN set -xe \ && curl -fSLk ${MANTIS_URL} -o ${MANTIS_FILE} \ && tar -xz --strip-components=1 -f ${MANTIS_FILE} \ && rm ${MANTIS_FILE} \ && chown -R www-data:www-data . RUN set -xe \ && ln -sf /usr/share/zoneinfo/${MANTIS_TIMEZONE} /etc/localtime \ && echo 'date.timezone = "${MANTIS_TIMEZONE}"' >> /usr/local/etc/php/php.ini \ && echo 'upload_max_filesize = "5242880"' >> /usr/local/etc/php/php.ini \ && echo 'register_argc_argv = Off' >> /usr/local/etc/php/php.ini \ && echo 'display_errors = Off' >> /usr/local/etc/php/php.ini
Tags	No tags attached.
Attached Files	issue.png (6,960 bytes) issue.png (6,960 bytes)

dregad 2022-10-13 05:45 developer ~0067067	This could be the same problem as 0029624. Unfortunately, I was never able to reproduce it locally, and @virtualdreams reported that the problem just went away after a ctrl-F5 refresh. I assume the error is more persistent in your situation, so hopefully you can provide a reproducible test case, which is likely environment- or data-specific. Specifically, I need to understand what is happening in the AJAX call to return_dynamic_filters.php, and why it's returning HTTP 400. It would be great if you could trace the error.

Passerby 2022-10-14 02:50 reporter ~0067068	Due to contains sensitive data, I'd like to know what database tables are required, so I can export to test enviroment.

dregad 2022-10-14 10:01 developer ~0067069	Unfortunately, I can't really tell you up front what tables are required. An access to your data is probably not needed at all, if you are able to do some debugging on your end to determine what is causing the AJAX to fail using browser console, retrieve the failing AJAX's URL, e.g. http://example.com/mantis/return_dynamic_filters.php?view_type=simple&filter_target=custom_field_1_filter&_=1665755100331 try calling that page directly. Check for errors on the page, or in PHP/web server logs. Set `$g_show_detailed_errors = ON;` if needed to get more info

atrol 2022-11-09 02:41 developer ~0067133	Passerby, You did not provide some more feedback; I am therefore resolving this issue as "no change required". Feel free to reopen the issue at a later time and provide the requested information.