Problem: I would like to create a field in a CRED form that will display a calculated value based on other form field values.
Solution: CRED does not currently offer a JavaScript API for performing calculations on demand in the front-end form. The cred_save_data API can be used to perform calculations when the form is submitted, but not during the form entry process.
I am afraid the pages cannot be loaded in China mainland. vice verse， if adding that code will strongly slow down my site. the pages will even not be loaded.
Solution:
there is a simple workaround, you can get the visitor IP address, so you can know which country are they from, then check the country value, then display the google map or not, I tested it in your website, with these steps:
1) Install plugin "GeoIP Detection"
2) Dashboard-> Toolset-> Front-end Content
option "Third-party shortcode arguments", fill the shortcode name "geoip_detect2"
3) Use Views shortcode [wpv-conditional] to check the country value, then display what you want, see the example:
Your country is: [geoip_detect2 property="country"]
<hr />
[wpv-conditional if="'[geoip_detect2 property="country"]' = 'CHINA'" evaluate="false"]
Here display the google map
[/wpv-conditional]
[wpv-conditional if="'[geoip_detect2 property="country"]' = 'CHINA'" ]
You are in [geoip_detect2 property="country"], Don't display the google map!
[/wpv-conditional]
Problem: Where can I translate the values of checkbox and select options?
Solution: The values for select field options can be translated in String Translation under the domain "plugin Types". Checkbox option values can be translated in the Translation Editor screen if you have chosen to translate the checkboxes custom field.
I receive this message on a Content Template in the front end when I visit a Post where it is assigned to:
Content not displayed because it produces an infinite loop.
The wpv-post-body shortcode was called more than once with the attribute view_template="your_template" over the post "your_post", triggering an infinite loop.
How to solve it?
Solution
The Post Body is called within the Post Body (Content template called within the same Content Template or post body).
Please head to the Content Template in question and ensure that the same template is not called again within it.
I want to apply the messaging system which the Toolset Classifieds Reference site uses. How can I do that?
Solution
It is not suggested to apply the Messaging system provided for that Reference Site on other but those reference sites.
The Plugin that makes it possible is an AddOn of Toolset (Toolset Classifieds) and it’s using hardcoded values related to the Reference Sites.
You can read a lengthy thread below if you want to dig into this anyway.
Suggested is, to use another Plugin when it comes to social networks like BuddyPress or similar. Toolset is not ideal for chats or instant messaging.
Problem:
How to use wpv-for-each to iterate over repeating fields of a parent post?
Adding the id="$parent-slug" attribute to wpv-for-each doesn't work.
Solution:
It is not possible to set the parent directly on the wpv-for-each shortcode.
You can make this work by creating an unassigned Content Template which uses wpv-for-each and which doesn't include any id attributes, so that the shortcodes use the "current" post for their context.
But you then insert that Content Template into your template for the child posts and this is where you add the id attribute, so that for that nested Content Template its context is the parent post.
Problem:
The new distance filters introduced with Maps 1.4 doesn't work for user meta address fields.
Solution:
Custom search Views are only available for posts, not for users, and so no filters can be added to a Users View, including the distance filter.
Problem: How can I edit multilingual posts with CRED? It seems that I must use the WP admin to handle the translations.
Solution: The plugin that was created to help with this process has been deprecated and we do not have plans to replace it. For now, custom code is required to integrate CRED and WPML.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
