[SOLVED] Search breaks when sorted by custom field (date)

Search is working fine if any of the built-in options are used (including the ones that go by date, such as 'Added -- Oldest First'), but it fails when told to sort by a custom date field. This is true if I tell it to sort on that field as the default via back-end settings (which is really what I want to do) or if I allow a drop-down on the front-end results page and choose to sort from the field there. It causes a 404 error.

I notice that all of the built-in sorts seem to have a letters-only, one-word orderby such as 'date' or 'rdate'. The custom one is trying to use &orderby=custom%3A17%3Adate%3Aasc and I wonder if that's somehow involved the issue? I tried replacing the %3As in the URL with : (since I believe that's the equivalent) and pressing enter, but it was still 404 so at least the encoding there probably isn't the problem.

I'm using FC 3.0.14-rc2a on Joomla 3.5.1.

Hello

a fix was made on February 13, that fix is included inside v3.0.14-rc2a

i have tested just now and it works

Hello

the change history for the file, fix was added in 3rd commit of February 13
github.com/FLEXIcontent/flexicontent-cck...h/flexiadvsearch.php

maybe not all your files were updated, in your installation, try to re-upload v3.0.14-rc2a

No, sadly, that doesn't appear to be the same issue. I've reuploaded it anyway to be sure, and the error remains.

Hello

PHP version ?

also enable in Joomla global configuration
- Joomla Debug (inside System TAB)
- error reporting (inside Server TAB)

and retry to see, if you get the error text to appear

It's possible the PHP version could be an issue -- it's 5.3.24, and I can't get my hosting to update it further. (Very frustrating.)

...okay, I have found what's happening. In the SQL when it's trying to use the custom date for sorting, the SQL tries to alias two different tables as 'f': Do you want/need the entire error (1066 - Not unique table/alias: 'f' SQL = <the whole query>)?