Tell us what you are trying to do?
In Divi I added a View module which lists all employees (a CPT) of a selectable company by Toolset's filter features.
The view works fine on the Divi page and the content also gets displayed if JS is turned off.
But the content of this view will not be indexed by any site search plugin I have tried so far, like SearchWP, Relevanssi or Elasticpress.
The content of the CPT employees gets indexed, but not on that page where the view is integrated by Divi. The other content on that page gets indexed.
I really can't see why this is not working. What can I do to solve this issue?
Hello and thank you for contacting Toolset support.
I am not sure to understand what do you mean by the content on that page does not get indexed. Can you elaborate more?
From what I know, the search plugins index the content directly from the database without caring where it is being shown.
We have a current integration with Relevanssi that allows indexing custom fields of selected types(single line, multiple lines, and WYSIWYG). You can read more about it here https://toolset.com/course-lesson/searching-texts-in-custom-fields-with-toolset-and-relevanssi/
I already followed the instructions in your link some days ago - it does not work.
To elaborate a little more what I have done:
1. Created a CPT "employees" with custom fields image, name, job title, email, phone and custom taxonomies (company, industry)
2. Created a Toolset View with filter options (select employee by company). View gets updated by Toolset's ajax functionality.
3. Created a simple WordPress Page "Contacts" using Divi Site builder.
3.1 Added some static content
3.2. Added a Toolset View module offered by Divi and selected the view created in 2. So far, so good, everything works fine.
But: No matter what kind of search plugin I try (Relevannsi, SearchWP oder Elasticpress) the Toolset View content on that "Contacts" page does not get indexed. The CPT itself gets indexed, but that is not my goal, because it links to the individual CPT post (which shall be excluded later). My goal is to have that contacts page indexed with the contacts included, so if you search for "John Doe" the search result shows the Contact page. I hope this makes it more clear.
Thanks
Thank you very much. Indeed, this clarifies what you mean. And that is simply not possible. The search plugins will always index content on the database and will return the post(CPT) instead of returning a page where a view displays it.
In fact, if you reach out to any of the search plugins' support they will tell you the same. The search will return the post(CPT) instead of returning a page where it appears(be it a Toolset view, or simply an archive, or maybe a page created by the theme).
I am sorry, what you want is simply not possible. Even though I am not qualified to talk about these plugins. Their respective support teams are the people that can answer you.
I hope this helps. And I'll remain at your disposal.
No, sorry, but it is possible.
SearchWP's support has resolved this problem yesterday.
Sorry to hear that Toolset offers not a solution for this standard use case.
Well, Toolset was never intended to be a search solution. We rely on the default WordPress search. And we have an integration with Relevanssi.
As I said, I can't speak for any of the search plugins. And I am glad you were able to fix this with SearchWP. Maybe you would like to share the solution here with the Toolset community!
If you don't need any further assistance, I have to kindly ask you to mark this ticket as resolved. Feel free to open a new ticket for any question or issue with Toolset.
All the best,
Jamal
You can close this ticket.
But anyways, I think it would be helpful if Toolset would care more about this use case in future releases, because Toolset Views that can't be indexed if integrated into pages are a real disadvantage.
Thank you for your feedback. However, I am sorry, I won't escalate this further. As I explained, we never intended to be a Search niche product. Honestly, what you are looking for, IMHO, is a very Search niche feature.
However, you can always suggest new features here https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/
Our product managers will then evaluate it and decide if it should be added to Toolset or not.
This concludes that Toolset is and will be a bad solution, if the client wants to have his content indexed on all pages.
I will consider this in my future projects. Thank you for clarifying and your solution-oriented support.
I wouldn't agree. Toolset is an amazing suite of plugins. And it offers a really wide range of features to build advanced websites without programming.
This is what we offer:
- Types: To define a custom data model.
- Views: To customize how this data will be displayed.(Including search, based on WordPress or Relevanssi. We just delegate it)
- Forms: To let your users enter/update data from the frontend.
- Maps: To use Maps and distance search.
- Access: To customize WordPress roles and permissions.
- WooCommerce Blocks: To customize how WooCommerce data may be displayed.
- WooCommerce Forms: To let users pay for submitting posts or registering to your websites.
We never pretended that we are a Search plugin. And what you are looking for is very niche. In my opinion, that's why SearchWP found a solution for it.
Why is it very niche, because you want to index dynamically generated content(view) in a static page(URL). This means, that the page is first generated, then indexed. WordPress, for example, cannot do it. Content is indexed directly from the database. Does it make sense?
no solution from Toolset.
