New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | A shortcode for displaying paginated lists of users. | You have to log in to add a translation. | Details |
Original untranslated |
|||
| ↑ | Simple User Listing | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Likely you are experiencing a conflict with another plugin, specifically one that is filtering <code>pre_user_query</code> to modify all user queries. The S2 Member plugin is a known culprit of this. To disable S2 Member's modifications on all Simple User Listing lists, add the following to your theme's functions.php or to a site-specific plugin. Ensure you are using at least SUL 1.5.3. | You have to log in to add a translation. | Details | |
Original untranslated
Likely you are experiencing a conflict with another plugin, specifically one that is filtering <code>pre_user_query</code> to modify all user queries. The S2 Member plugin is a known culprit of this. To disable S2 Member's modifications on all Simple User Listing lists, add the following to your theme's functions.php or to a site-specific plugin. Ensure you are using at least SUL 1.5.3.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The search form will not work with the default permalinks. Try changing your permalinks to some other structure. The reason is form submits via the GET method and so adding those parameters to the URL seem to clash with the parameters already on the URL from the default permalink setup. | You have to log in to add a translation. | Details | |
Original untranslated
The search form will not work with the default permalinks. Try changing your permalinks to some other structure. The reason is form submits via the GET method and so adding those parameters to the URL seem to clash with the parameters already on the URL from the default permalink setup.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes! <a href="http://wordpress.org/plugins/wp-pagenavi/">WP Pagenavi</a> supports pagination for <code>WP_User_Query</code> and I configured the navigation-author.php template to automatically use WP Pagenavi if it is installed and activated. | You have to log in to add a translation. | Details | |
Original untranslated
Yes! <a href="http://wordpress.org/plugins/wp-pagenavi/">WP Pagenavi</a> supports pagination for <code>WP_User_Query</code> and I configured the navigation-author.php template to automatically use WP Pagenavi if it is installed and activated.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For complex queries, you will want to read the <a href="http://codex.wordpress.org/Class_Reference/WP_User_Query#Parameters">WP Codex reference on WP_User_Query</a>. | You have to log in to add a translation. | Details | |
Original untranslated
For complex queries, you will want to read the <a href="http://codex.wordpress.org/Class_Reference/WP_User_Query#Parameters">WP Codex reference on WP_User_Query</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| And then in your theme's <code>functions.php</code> or a site-specific plugin, you could filter the user query args: | You have to log in to add a translation. | Details | |
Original untranslated
And then in your theme's <code>functions.php</code> or a site-specific plugin, you could filter the user query args:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For example you could pass a specific ID via shortcode: | You have to log in to add a translation. | Details | |
Original untranslated
For example you could pass a specific ID via shortcode:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It isn't worth the effort to get the shortcode parameters to handle complex arrays. And in the end it isn't necessary as there are several filters in place to permit you to run a complex query. The key will be using the <code>query_id</code> parameter. | You have to log in to add a translation. | Details | |
Original untranslated
It isn't worth the effort to get the shortcode parameters to handle complex arrays. And in the end it isn't necessary as there are several filters in place to permit you to run a complex query. The key will be using the <code>query_id</code> parameter.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It is much more useful to search by the user's display name, however this requires some trickery via the <code>pre_user_query</code> hook. Similar to <code>pre_get_posts</code> this is your last chance to change the <code>WP_User_Query</code> query before it is executed. I’ve built in a <code>query_id</code> variable so that you don’t go willy-nilly filtering all user queries which could have some unintended side effects. | You have to log in to add a translation. | Details | |
Original untranslated
It is much more useful to search by the user's display name, however this requires some trickery via the <code>pre_user_query</code> hook. Similar to <code>pre_get_posts</code> this is your last chance to change the <code>WP_User_Query</code> query before it is executed. I’ve built in a <code>query_id</code> variable so that you don’t go willy-nilly filtering all user queries which could have some unintended side effects.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| By default the WordPress search relies on username, though wih the <code>search_columns</code> parameter can be made to search the user's email or ID. Frankly, I think this is weird, but that's how WordPress works. | You have to log in to add a translation. | Details | |
Original untranslated
By default the WordPress search relies on username, though wih the <code>search_columns</code> parameter can be made to search the user's email or ID. Frankly, I think this is weird, but that's how WordPress works.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Now the search will return users that match the entered "last_name". You can adjust as needed or use the <code>meta_query</code> array for more complicated meta queries. | You have to log in to add a translation. | Details | |
Original untranslated
Now the search will return users that match the entered "last_name". You can adjust as needed or use the <code>meta_query</code> array for more complicated meta queries.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Add the following to your theme's functions.php: | You have to log in to add a translation. | Details | |
Original untranslated
Add the following to your theme's functions.php:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| While you could modify the <code>search-author.php</code> template, if you are only searching by one field it isn't really neccessary. You will, however, need to modify the shortcode's arguments for <code>WP_User_Query</code>. You can do that by filtering <code>sul_user_query_args</code>. | You have to log in to add a translation. | Details | |
Original untranslated
While you could modify the <code>search-author.php</code> template, if you are only searching by one field it isn't really neccessary. You will, however, need to modify the shortcode's arguments for <code>WP_User_Query</code>. You can do that by filtering <code>sul_user_query_args</code>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| As of verison 1.5.2 you could simply use the following as your shortcode: | You have to log in to add a translation. | Details | |
Original untranslated
As of verison 1.5.2 you could simply use the following as your shortcode:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.