Boîte à outils

Profile: thomasD-2

thomasD-2

Fils de soutien créés au cours des 30 derniers jours : 0

Sujets de forum favoris

This user has no favorite topics.

Sujets de forum créés

Visualisation de 8 sujets : 1 à travers 8 (sur 8 au total)

Status	Sujet	Supporter	Voix	Publications	Nouveauté
	Recaptcha is missing in Firefox browser Commencé par : thomasD-2 in: Toolset Professional Support		2	3	Il y a 3 années et 4 mois thomasD-2
	Toolset blocks v1.3 fatal error related to Class 'Toolset_Relationship_Role' Commencé par : thomasD-2 in: Chat Support		1	2	Il y a 4 années et 3 mois
	Plugin Update not possible Commencé par : thomasD-2 in: Toolset Professional Support		2	2	Il y a 5 années et 9 mois Christian Cox
	POST_PARENT_TITLE doesn’t work after migration to Types3 and new relationships Commencé par : thomasD-2 in: Toolset Professional Support Quick solution available Problem: POST_PARENT_TITLE doesn't work after migration to Types3 and new relationships Solution: This is known issue to us and the fix will be published with next release of forms. You can find proposed solution, in this case, with the following reply: https://toolset.com/forums/topic/post_parent_title-doesnt-work-after-migration-to-types3-and-new-relationships/#post-918816 Relevant Documentation:		2	12	Il y a 6 années et 5 mois thomasD-2
	Form notification to email from parent post field no longer working after Types 3.0 update Commencé par : thomasD-2 in: Toolset Professional Support Quick solution available Problem: I have a Form that triggers an email notification. I send the notification to an email address that is stored in a parent post's custom field, by using the CRED API cred_notification_recipients. Since updating to Types 3.0, the email notifications are not sent as expected. Solution: Update the code to work with the new Post Relationships API, and ensure the child post status is not "private". add_filter('cred_notification_recipients', 'modify_recipients', 10, 4); function modify_recipients($recipients, $notification, $form_id, $post_id) { // Check notification name matches target notification if ( isset($notification['name']) && 'Mail an Veranstalter' == $notification['name'] ) { // Add email recipient $parent_id = toolset_get_parent_post_by_type( $post_id, 'veranstaltung' ); $email_of_organizer = get_post_meta($parent_id, 'wpcf-veranstalter-email', true); $recipients[] = array( 'to' => 'cc', 'address' => '$email_of_organizer', 'name' => '', 'lastname' => '' ); } return $recipients; } Relevant Documentation: https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/#toolset_get_parent_post_by_type		2	5	Il y a 6 années et 6 mois thomasD-2
	CRED form editor doesn’t show my custom post types in dropdown for post types Commencé par : thomasD-2 in: Toolset Professional Support Quick solution available Problem: The 2 post types that I created are: - Anmeldungen - Veranstaltungen They don't show up in the dropdown selector on the post forms page. When I try to edit the post form "Anmeldung", I can't save the settings, as the relation to the post type "Anmeldung" gets lost. Interesting observation: I can create new custom post types that show up correctly (e.g. the "TestbeitragstypenTD" that I created today). So the problem is related specifically to my 2 post types that I had created a few weeks ago. I had edited the form several times over the past weeks without any problems. Unfortunately there ist ongoing activity and data input on the production website, so I need a solution to repair the problem without redefining all the data structure. Solution: Q1) The 2 post types don't show up in the dropdown selector on the post forms page. Since you setup those two post types as not "publicly_queryable", so CRED will not be able to edit/create those post, for example you can try this: Edit the post type "Anmeldungen", in section "Options", enable the option "publicly_queryable", and test again. More help: https://codex.wordpress.org/Function_Reference/register_post_type#publicly_queryable publicly_queryable (boolean) (optional) Whether queries can be performed on the front end as part of parse_request(). Q2) form "Anmeldung", I can't save the settings, as the relation to the post type "Anmeldung" gets lost. Same as above, you will need to enable the option "publicly_queryable" for post type "Anmeldungen", and test again. Relevant Documentation: https://codex.wordpress.org/Function_Reference/register_post_type#publicly_queryable		2	5	Il y a 6 années et 9 mois thomasD-2
	CRED form ist losing settings and notifications after Save Commencé par : thomasD-2 in: Toolset Professional Support Quick solution available Problem: I was editing an existing CRED form that was working for many years. After saving the form, CRED had lost important settings, esp. the relationsship to the post type, the notification after submitting the form and all email notifications. This happened again and again. I was using CRED 1.9.2. In the support thread I saw a similar problem that was resolved with the latest CRED version 1.9.5, so I made an update. But now I have this error: /wordpress/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/classes/cred-editor-addon.class.php" doesn't exist! Solution: The problem you mentioned above is abnormal, in case it is a compatibility problem, please try this: 1) Make sure you are using the latest version of Toolset plugins, you can download them here: https://toolset.com/account/downloads/ For example, you are using Views 2.5, but the latest version is 2.5.2 2) deactivate other plugins and switch to wordpress default theme, and test again Relevant Documentation: https://toolset.com/account/downloads/		2	7	Il y a 6 années et 9 mois Luo Yang
	CRED-notification to email from parent post field Commencé par : thomasD-2 in: Toolset Professional Support Quick solution available Problem: I would like to send a CRED notification to an email address that is stored in a custom field on the CRED post's parent post. How can I access that parent post field in the CRED notification recipients configurations? Solution: The most flexible, preferred method today is to use the CRED API hook cred_notification_recipients to modify the "to", "cc", or "bcc" of the notification email. Within the callback, you can figure out the parent post by calling get_post_meta on the child post, and accessing a hidden field that relates a parent post ID to the child post. The name of that field follows the format "_wpcf_belongs_" + parent post type slug + "_id". So if your parent post type slug is "event", then the postmeta key is "_wpcf_belongs_event_id" and the code is: $parent_id = get_post_meta($post_id, '_wpcf_belongs_event_id', true); Once you know the parent post ID, use it to call get_post_meta again on the parent post to retrieve the email field value. Types fields use the prefix "wpcf-" in the postmeta table, so if your email field slug is "email-address-of-organizer" then the code would look like this: $email_of_organizer = get_post_meta($parent_id, 'wpcf-email-address-of-organizer', true); Now the variable $email_of_organizer contains the email address from the parent post. Use that to modify the code sample on the API documentation page to fit your needs. Relevant Documentation: https://toolset.com/documentation/programmer-reference/cred-api/#cred_notification_recipients Click the orange "+More" button to see a code sample.		2	15	Il y a 6 années et 11 mois thomasD-2

Visualisation de 8 sujets : 1 à travers 8 (sur 8 au total)

Problèmes connus et leurs solutions

Nous documentons les problèmes connus et leurs solutions dans Toolset erratas. Pour gagner du temps, vérifiez d’abord dans cette rubrique si le problème auquel vous êtes confronté est un problème connu. Cette liste est volontairement courte. À chaque publication d’extensions de Toolset, nous nous efforçons de résoudre tous les problèmes connus.

Politique d’assistance

Le personnel Toolset vous guidera volontiers pour utiliser correctement les extensions Toolset, vous fournir les informations dont vous avez besoin, vous aider à résoudre les problèmes et vous conseiller quant aux meilleures pratiques.

Merci de veiller à ce que chaque ticket d’incident ne référence qu’un seul incident.

Pour de plus amples informations, consultez notre Politique d’assistance client en détail.

Vous avez besoin d’une programmation personnalisée pour votre site ? Jetez un coup d’œil à nos partenaires certifiés.