If I sort a custom field column in 1.0.0a1 and then go into to the filter and press "Filter" I recieve a #401 error. This only happens with custom fields.
Any ideas?
#401 Error when using filter with customs fields
Moderators: Developer, Contributor
Hmm... I got this too.. I was trying out a new custom field and put it in the custom_function_default_get_columns_to_view
I was able to sort by my custom field just fine, but when I went to use a filter to change something, and then tried to return to the view all page, I got the 401 error. I had to clear my cookies to get my View All Issues page to display again.
I was able to sort by my custom field just fine, but when I went to use a filter to change something, and then tried to return to the view all page, I got the 401 error. I had to clear my cookies to get my View All Issues page to display again.
APPLICATION ERROR #401
Database query failed. Error received from database was #1066: Not unique table/alias: 'mantis_custom_field_string_table' for the query: SELECT DISTINCT mantis_bug_table.*, mantis_custom_field_string_table.value
FROM mantis_bug_table
LEFT JOIN mantis_custom_field_string_table ON ( ( mantis_custom_field_string_table.bug_id = mantis_bug_table.id ) AND ( mantis_custom_field_string_table.field_id = 7 ) ) LEFT JOIN mantis_custom_field_string_table ON ( ( mantis_custom_field_string_table.bug_id = mantis_bug_table.id ) AND ( mantis_custom_field_string_table.field_id = 7 ) )
WHERE 1 != 1
ORDER BY sticky DESC, mantis_custom_field_string_table.value ASC, mantis_custom_field_string_table.value ASC, last_updated DESC, date_submitted DESC
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.