chnovo7 / wordpress-custom-content-type-manager

Automatically exported from code.google.com/p/wordpress-custom-content-type-manager
0 stars 0 forks source link

Ajax Search Parameters broken in Modal Windows #519

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
To reproduce:

1. Create a Relation or Image Custom Field
2. Add it to a post-type (e.g. posts)
3. Create a post in that post-type
4. Click "Select Image" to launch the modal window
5. Attempt to filter the results, e.g. by a search term

The results do not filter: we expect the list of results to become smaller 
after a search term is entered and the "Filter" button is pushed.

Relatedly:  the config/post_selector/_image.php file does not seem to have any 
effect on the search.

Original issue reported on code.google.com by ever...@fireproofsocks.com on 2 Sep 2013 at 11:12

GoogleCodeExporter commented 8 years ago
Downgrade to version 0.9.4 help with this problem temporary :/

Original comment by pmare...@gmail.com on 9 Sep 2013 at 8:23

GoogleCodeExporter commented 8 years ago
0.9.4?  I think the problem is only in 0.9.7.9 and later.

Original comment by ever...@fireproofsocks.com on 9 Sep 2013 at 8:43

GoogleCodeExporter commented 8 years ago
Looks like the problem is that the name parameter isn't being set correctly, so 
the search parameter is not being passed.

Original comment by ever...@fireproofsocks.com on 1 Feb 2014 at 7:10

GoogleCodeExporter commented 8 years ago
Ah: makes sense: the placeholders are never generated because the form's 
configuration was not set correctly.  To fix this, add the following line to 
the config/post_selector/_media.php and _image.php and _relation.php configs as 
described here: 
https://code.google.com/p/wordpress-custom-content-type-manager/wiki/Config_post
_selector_media

CCTM::$search_by[] = 'search_term';

Original comment by ever...@fireproofsocks.com on 1 Feb 2014 at 7:20

GoogleCodeExporter commented 8 years ago
Committed revision 849527.

Original comment by ever...@fireproofsocks.com on 1 Feb 2014 at 7:41