[Closed] Miscellaneous Issues

[Author]

Posts

[jeremyP-3]

Hey there! Not really sure how to start this off, but I am running into multiple different issues / bugs at the moment. I will do my best to explain what is going on for each, so here goes:

1st Bug: The first issue I am having, is with the view search fields. On the back end, they are being populated with data from my view, but on the front end, they are not displaying at all. I have tried with multiple different fields, and none seem to work. The issue only seems to be affecting filters that deal with the views parent elements, since my taxonomy filter and one of the views custom field filters seem to working okay for now...

2nd Bug: This bug also has to do with the view searching/filter blocks... For this one, any time I add the Distance filter and update the page, my entire view just breaks. Not even filtering, just adding that block to the page and saving presents an error that no posts could be displayed. Even if I revert the changes, and go back to the revision where the view was working before I added the filter, I still get that same error. The only thing I can do to get my view back to normal, is completely deleting all traces of it from my site, and starting from scratch.

3rd Bug: This bug has to do with the map markers. For some reason, the Maps plugin is having trouble pulling addresses from my view. I have everything mapped to the correct field, and the addresses are being displayed correctly in the view, but no markers are displaying on the map.

4th Bug: This last bug is very unpredictable, but can be "fixed" pretty easily. For this one, every once in a while when saving my page that has a table based view on it, all of my columns get scrunched together on the left side of my screen. Have not quite pinned down a more specific cause for this, but switching the view to a "group" and then back to "columns" seems to re-format things correctly. Not a huge deal, but can be a little annoying sometimes.

Side note, I have tried deactivating all unnecessary plugins, along with switching themes, but had no luck. I will attach some screen recordings / pictures in my duplicator file for reference, along with a set of credentials. Hopefully that makes sense! Thanks!

[Jamal]

Hello and thank you for contacting the Toolset support.

I assume that you are talking about the view on the Tickets Map page, right? If not, please let me know what view?

1st Bug, the filters on the frontend will display values from the posts on the results. But, because of the distance query filter on the view, the view doesn't return any results, which means that the filters will remain empty. Check the screenshot of the query filter here hidden link
As soon as I remove the query filter, the view has returned results, and some of the filters were not empty anymore. Check this screenshot hidden link

2nd Bug, I don't see why you would like to add a distance search in the view where the post type of the view does not have any Address fields. You can use distance search only on custom post types that hold an Address field. For example, the Locations CPT has an address field. But the Tickets CPT does not have it.

3rd Bug, As I explained before. The Tickets post type does not have any Address field. Toolset Maps will add markers either from an Address custom field or from {latitude, longitude} tuples.

4th Bug, can you share a screenshot that demonstrates the issue? Can you also tell me what steps should I follow to reproduce this issue?

[jeremyP-3]

Yep! That's the one. Maybe we misunderstood this then. What we want, is use the address of each 'Tickets' parent 'Location'. That way, instead of having to fill out an address field for each new ticket, we could just assign the ticket to an existing 'Location', and have that address already be populated. I think we may have figured out part of the problem though. Once we changed the setting to allow multiple post types in the view, the map markers and the search boxes started working, partially. Now, the table doesn't seem to be displaying correctly though. There appears to be data in it, (amount of rows change when filtering), but all of those rows are blank. I'll attach a screenshot of what's going on now. Also, this might be just because the table is acting wonky right now, but once I have 1 search box filtered, the options disappear for the other boxes. So for example, if I choose a Location from the drop-down, all the options for Technicians disappear, and vice versa. Hopefully what I am doing makes a little more sense now. Thanks!

[jeremyP-3]

Side note, this is what I was talking about in my initial post (bug 4). This bug is very random, and doesnt have a specific trigger (to my knowledge), so it can be a little hard to recreate. When it happened this time, I had just re-built the view, and added some search filters. Once I updated the page and viewed it on the front-end, I noticed that everything had just gotten scrunched as I previously explained. All I had to do to get it back to normal, was changing the views block type to groups. Again, this bug really isnt too bothersome for me, I just thought I might throw it out there, in case anyone else may have been having the same issues... Thanks!

[Jamal]

You said So for example, if I choose a Location from the drop-down, all the options for Technicians disappear, and vice versa. Hopefully what I am doing makes a little more sense now.
In the Blocks-based views, the filters will display only the values that have a post in the results. So, when you choose a value of a filter, the results set will change, and the other filters will display only the values from the result set posts. Does it make sense?

Regarding the issue with the table, I can't really see why, as It does not happen on the copy you have provided. Without seeing it closely, I can't really tell.

On the other hand, I can suggest using the legacy editor to build this table view. Using HTML and shortcode may be more smooth for creating a table-based view. You can activate the legacy editor in Toolset->Settings->General(tab)->Editing Experience. Then, you can create a view in Toolset->Views(you will need to refresh the page to make this menu item appear).
Check the available views shortcode here https://toolset.com/documentation/programmer-reference/views/views-shortcodes/

Let me know if you need further help with that.

However, for support rules, we are able to handle only one issue at a time. This helps us to bring you a better service and also helps other users to find all the information here exposed. For that reason, I have to kindly ask you to mark this ticket as resolved if you don't need further help and open a new ticket for any other question/issue.

[jeremyP-3]

I am still having some issues though... I can either have my table displaying correctly, or my map markers / filters. Not both. For my view, whenever I 'allow multiple post types', my map markers and filtering options display, but my table starts acting weird. On the other hand, if I have my view set to only allow the 'Tickets' post type, my table will display correctly, but my map markers, and filtering options disappear. I will attach some screenshots for reference. To recreate my issue on the site you have, all you have to do is change the content selection to allow multiple post types for the view. If you aren't able to do that, I can send you a WeTransfer link to the most recent version of the site if you give me a good email address to use...

For the screenshots, 'Capture' + 'CaptureBackend' are when the view allows multiple post types. 'Capture2' + 'Capture2Backend' are when the view only allows the Ticket post type.

[Jamal]

I don't think you want a table view to query posts from Tickets, Locations, and Technicians. Especially, because they do not share the same data model(Tickets do not have a location field, Technician does not have a status or a type).

I think, I understand now what you want to achieve, please correct me if I am wrong.
Based on the following:
- 3 custom post types: Location, Ticket, and Technician.
- 2 one-to-many relationships: Location<>Tickets and Technician<>Tickets.
You want to:
1. Display a list of tickets posts in a table with the following details:
- Location name: Single line field from the parent Location post.
- Location address: Address field from the parent Location post.
- Type: Select field in the current Ticket post.
- Status: Select field in the current Ticket post.
- Technician name: Either the title or custom fields(first, last names) from the parent Technician post.
2. Filter the table/view with:
- Ticket status.
- Ticket type.
- Location name.
- Location address (distance search).
- Technician name.
3. Display markers on the view coming from the parent Location post.

Is this correct? Please correct me if I am wrong
===========================================================================

If I understood what you need to build correctly, I am afraid, it can't be built entirely because of the following Toolset limitations:
1. It is not possible to filter/search a post type(Ticket) using a custom field in a related post(Location, Technician): This means, that distance search can't be implemented. And it also means that you can't filter by the location single line field(Location name), or the Technician custom fields(first, last names).
2. It is not possible to filter using more than ONE relationship unless you are using hierarchical one-to-many relationships(for example Country>State>City). This means, that you will be able to filter, either by the parent location, or the parent technician, not both. If you choose one of them, you can only filter by the parent post title and not a custom field.
3. The view block, cannot pull markers from the related posts of a view's posts. But we can work around this using the Toolset Maps shortcodes https://toolset.com/documentation/programmer-reference/maps/maps-shortcodes/#wpv-map-render

If I understood well what you are looking to achieve, I think that the easiest way to do it would be to implement the following changes:
- Change one or both of the parent post types to taxonomies instead of post types.
- Attach the address field in the Ticket post type. You can implement some custom code that will always sync the value of address from the assigned Location(be it a post or a taxonomy term).
Let me know if you need any questions about this approach

Otherwise, this will need heavy custom coding(PHP, HTML, CSS, Javascript) to implement the filters and the view's query arguments. Please note that custom code is beyond the scope of the support forum. We do help sometimes our users with easy-to-implement custom code solutions. But this use case is more complex and will need an experience WordPress developer.
https://toolset.com/toolset-support-policy/
https://toolset.com/contractors/

I hope I understood what you want to achieve. I also hope my answer explains the current Toolset limitations and that my suggested solution makes sense to you. Let me know your feedback.