Problem: After moving my site's WordPress installation to the root directory, my site key no longer works and I see an error message that the Toolset plugins cannot connect to Toolset.com. In the installer support page, I see that the site key does not match the current site URL.
Solution: Delete the old site key from @https://toolset.com/account/sites and generate a new registration key. Unregister the Toolset software and then re-register with the new key.
Problem: I would like to add some non-Toolset blocks to a post, but the changes I make in the post editor are not reflected on the front-end of the site.
Solution: Check to see if a Content Template is assigned to the post. If so, you may need to make changes in the Content Template instead of the post editor to see those updates on the front-end of the site. The Content Template design overrides the post content in the post editor.
Problem: I am using the cred_save_data Forms API with new and edit post Forms that create or edit child posts in a O2M post relationship. The Form contains a post relationship field where I have defined the parent using a URL parameter. I get a 500 error when submitting the Form with AJAX.
Solution: Do not rely on the $_GET superglobal to access values in URL parameters. AJAX submissions do not have access to the parent page's URL params in $_GET. Instead, it is better to use a hidden field in the Form using the URL parameter option to store the parent page's URL parameter value in the Form. Then you can access that value in a cred_save_data hook in the $_POST superglobal instead. This approach will work well in either AJAX or standard Form submissions.
It is also important to note that the post relationship managed in the Form will not be available to the Post Relationships API during a cred_save_data hook. Relationships are not established by the time the hook fires, so you would have to get the relationship field value directly from $_POST in a cred_save_data hook. Or, use a cred_submit_complete hook. Post relationshps are available in the Post Relationships API at the time of cred_submit_complete.
Problem: On my Map View, I would like to display different marker icons depending on whether or not the post has a specific term from a custom taxonomy.
Solution: Use map marker shortcodes and conditional shortcodes with the has_term function to display different markers based on the has_term function.
Problem:
The user would like to disable the title that appears when we hover on a map marker.
Solution:
If we don't set a title for the marker, it will take the post's title by default. There is no way from the user interface to disable this feature. But we can remove the title using custom Javascript code, such as:
