This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | - |
| - | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: Asia/Hong_Kong (GMT+08:00)
This topic contains 2 replies, has 2 voices.
Last updated by Brad 8 years, 5 months ago.
Assisted by: Luo Yang.
I found an error that would be unlikely to manifest except in the unusual case that a custom field has been created but not yet populated with a value in any post.
When specifying such a custom field as the "order by" field in a View, the result is an incorrect "No posts found" error. The "order by" should not affect the query result, only the ordering of the result.
As soon as I populated a post with a value in the "order by" field (Numeric Rank in my example attached) the query produced the desired result.
