The issue here is that the user wanted to know when will Toolset be fully compatible with bootstrap 4
Solution:
Unfortunately I dont have an estimate regarding when this will happen but if you're using our views plugin then you can manually import the bootstrap css and then add the classes to the view items when you a displaying them on the frontend and this should work.
Problem: We need to create a series of events with a booking form for each event that allow the possibility to have a maximum number of people and close the booking until that number is reached. The user data shall be stored somewhere to be used and exported by our client.
Solution: This is a complex process that cannot be addressed sufficiently in one ticket. The following steps must be investigated:
- It sounds like you need an Event custom post type, so you should explore how to create an Event custom post type that captures all the necessary event information.
- It sounds like you need allow Users to associate themselves with any Event, so you should explore how to associate Users with a custom post type using CRED. One way to do this is to use a repeating custom field that stores the User ID of each User associated with the Event.
- It sounds like you need to stop Users associating themselves with an Event based on the number of other Users associated with the Event, so you should explore how to use the cred_form_validate API to validate form submissions based User associations.
- It sounds like you need to be able to export data from the system. Toolset isn't designed to export data, but Views is designed to display formatted lists of data. So if copy+pasting from a View is sufficient, this might be feasible. Otherwise, you'll need to look for other 3rd-party tools to generate export files.
Problem:
Client wants to store related posts in a custom field and to then be able to output content of those related posts when viewing the first post (a simple bespoke solution that doesn't involve post relationshipts).
Solution:
Store the related post IDs in repeating numeric fields, i.e. add as many as there are related posts.
Then in the Content Template for this post type, to display content from the related posts use the wpv-for-each shortcode to loop over the numeric fields which store the post IDs which can then be used as the id attribute of the shortcodes used to output the required fields.
The issue here is that the customer wanted to know if it was possible to change the order of how the post relationships are displayed on the Parent Post on the backend.
Solution:
Unfortunately this functionality is not available on our current production version of our Types plugin. However in our Types Beta plugin you are able to do this but its not recommended to use Beta plugins for Live websites.
Problem: I would like to know if I should use the new M2M beta plugins now, or continue using the production versions. I am creating a new site. I would like to choose the safest option, and I would like to know about backwards compatibility.
Solution: The safest solution is to wait until the new relationship production versions are released, since beta plugins are more prone to errors and less complete. However, new features in the beta plugins are not available yet in the production versions so you will not be able to take advantage of key improvements, like repeating field groups and more robust relationship filters in Views. When the new relationship features are released in the production versions, a migration process will be offered that will migrate existing relationships into the new relationship structure. This will help ensure existing content works in the new relationship structures. Once migration happens, there is no reversal process so at that point any new relationship data added to the system will not be backwards compatible. If any custom code is put in place that queries those old relationships, some manual code changes may be necessary as well.
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
