1/3/2024 0 Comments Facetwp fselect![]() This is optional behavior for Easy Pods and Easy Queries, but the only way FacetWP, with or without Clarity, can function. SearchĪll three plugins can function as a search system. ![]() For example, if you have two custom post types on your site: “shirts” and “pants” and used a custom field called “make” to identify their manufacturer and wanted to create a query to show all shirts and pants by the same manufacturer, this would be possible with Easy Queries, but not Easy Pods. The major limitation of Easy Pods, is that it can only query in one content type at a time. In addition Easy Pods has the best support for querying by Pods relationship fields, which is not possible in FacetWP and is not always possible in Easy Queries. In addition, since Pods has the ability to store data in custom tables of your database, Easy Pods has the ability to query this information, where Easy Queries or FacetWP could not. On the other hand, if you extend categories with Pods, then you can create an Easy Pod to query in categories. This means that Easy Queries and FacetWP can search for a post, of one or more post type, based on what category it is in, but it can not search categories directly. WP_Query can query posts based on this data, but can not query them directly. But it also means they can not be used to query any other content type - taxonomies, users, comments, etc. This means that the queries can be run in one or more post types. What Can Be Queriedīoth Easy Queries and FacetWP (with or without Clarity) rely on WordPress’ WP_Query class for their queries. You can see a screenshot of how it was created here. That list is dynamically generated using Easy Queries. Both plugins can optionally use our free plugin Caldera Metaplate when more powerful templating functionality is needed.Įasy Pods relies on Pods Templates for displaying results of Easy Pods queries. That would be of limited use if you didn’t have a way to show the results.īoth Clarity and Easy Queries have an integrated template editor. Results TemplatesĪll three of these plugins use different methods to query for data from the database. Clarity and FacetWP is a search system, if you want to define the content to display from the back-end, not create a search interface, then Clarity is not a good choice.Įasy Queries uses WordPress’ native WP_Query class for its work. If you are looking for a way to create complete faceted search layouts, without writing any PHP, then Clarity and FacetWP are a great option. But, if you already have a custom fields plugin, such as Advanced Custom Fields, installed, or do not need one, then adding Pods, just to use Easy Pods is probably not advisable.Ĭlarity for FacetWP requires FacetWP, which is an awesome “faceted” search tool. This makes Easy Pods an excellent choice for current Pods users, and a potential choice for most users. Since Pods can “extend” any custom post type or taxonomy, as well as WordPress’ user and comment objects, it can be used with most anything. is active and can only be used with Pods content types. Dependent PluginsĮasy Pods only works when Pods, a free content management system. In this article, this article will highlight the differences between these three plugins to help you choose which one is best for you. All three plugins have a lot of similarities in their user interfaces as well. This topic was modified 1 month, 3 weeks ago by sweetrobot.We have created three plugins, Easy Queries, Easy Pods, and Clarity for FacetWP that have many similar capabilities, while each have their unique features. i wanted to see if a solution where both are fully compatible is possible in the first place. If needed, i am not opposed to seeking professional/ developer assistance in the matter. i figure i’d ask here, seeking support from both sides. I would prefer to pursue a solution where both play nicely before throwing in the towel and opting for either resolve. however, in this instance i was told that various object caching plugins tend to prevent fwp from being able to detect the query – and to therefore disable the object cache, or create exclusions. ![]() I reached out to support from fwp, (who have been very helpful in the past). debug is enabled so can prod via the console. example: – select a few filters and it will output the error “FacetWP was unable to auto-detect the post listing”. ![]() It seems there is a conflict with this plugin and facetwp (fwp) which we use for filtering woocommerce products. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |