You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we're adding new post types to the Developer blog (see #68 and #69), we will need more control over the query loops in the various templates to be able to show more than a single post type. This is currently not possible with the existing Query Loop block.
I would like to request that we add my Advanced Query Loop plugin to the site. This would provide the control we need without having to push code. Changes can be more easily reverted and revisioned as part of the content. Additionally, adding items to the main query requires that the homepage template inherit the query which it currently does not.
I understand that there will need to be a code-level review of the plugin and all of the code is available here for review.
There are some controls for creating post meta queries that may cause some concern. To that end I would propose that 1) it's a small user base for this site and we don't use any post meta queries so we can just not use that feature or 2) I can introduce some code-level controls that turn off those features ether via a PHP constants or some other means.
Happy to discuss further and open to other options as well.
The text was updated successfully, but these errors were encountered:
As we're adding new post types to the Developer blog (see #68 and #69), we will need more control over the query loops in the various templates to be able to show more than a single post type. This is currently not possible with the existing Query Loop block.
I would like to request that we add my Advanced Query Loop plugin to the site. This would provide the control we need without having to push code. Changes can be more easily reverted and revisioned as part of the content. Additionally, adding items to the main query requires that the homepage template inherit the query which it currently does not.
I understand that there will need to be a code-level review of the plugin and all of the code is available here for review.
There are some controls for creating post meta queries that may cause some concern. To that end I would propose that 1) it's a small user base for this site and we don't use any post meta queries so we can just not use that feature or 2) I can introduce some code-level controls that turn off those features ether via a PHP constants or some other means.
Happy to discuss further and open to other options as well.
The text was updated successfully, but these errors were encountered: