Releases for Content Profile Search

content_profile_search 6.x-1.0-alpha1

6.x-1.0-alpha1

New features

Bug fixes

It's been ages, but it's time to get a proper 1.0 release out the door.

content_profile_search 6.x-1.x-dev

6.x-1.x

New features

Bug fixes

Use correct sort order field name.
Allow user switching via devel.module.

content_profile_search 6.x-0.6

6.x-0.6

Bug fixes

allowed_values matching was still using the old single string search method, not the new substring method, resulting in nothing found when searching a field with allowed_values set.

content_profile_search 6.x-0.5

6.x-0.5

New features

The on-our-way-to-one-point-zero release.

Use proper placeholders in the generated query.
Add support for user-selected boolean search operation.
Improve UI a bit, display found user count, stop abuse of the english language :-)

content_profile_search 6.x-0.x-dev

master

This is the a packaged release of the latest development version. It may contain untested features.

content_profile_search 6.x-0.4

6.x-0.4

New features

Closes #622722: The search doesn't recognise content profile fields by jagaimo

You can now search text fields with an 'allowed values' definition without needing to know which index key happens to be assigned to the text value you're after.

This also works on fields that define their allowed values via PHP code.

content_profile_search 6.x-0.3

6.x-0.3

New features

Bug fixes

Added the ability to search multi-value text fields, which should close #611824: Fields marked as `multiple' break the search.

Fixed the query generator, so it uses LEFT JOINS like it should and added the node type to each JOIN clause, so there are no duplicate empty result sets for each node type we're searching through.