Dynamic content in terms of service

Great question. I’m getting ready to release an update to the plugin. If you tell me where in each document(s) you’d like to do so, I may be able to work it in. Please also describe how you’d want to populate the shortcode argument.

For example,

[my_terms_of_service_and_privacy_policy name=”Bob”]

would be hard-coded.

How would you like to pass a dynamic value through?

What I had in mind was to get the values from woocommerce and/or wordpress fields for users and orders. More like:

[my_terms_of_service_and_privacy_policy name={$user_name}, orderNo={$order_no}, productName={product_name}, paymentMethod={$payment_method}]

Does that make sense?

I cannot know how each site would want such a dynamic setup unless those are WooCommerce-specific fields.

I think the best way would be to add a hook so it’d be ready for a programmer do it via PHP.

I’m considering adding a Pro/Paid version and might made an add-on specific for WooCommerce fields if that’s of interest to you and you do not want to figure out the PHP part.

Thoughts?

Those are woocommerce-specific fields. They are also present in email templates sent out to customers and admins alike.
So that’d be very useful indeed.

Would you update this conversation once it’s ready?

Thanks.

I’ll do my best: https://github.com/cliffordp/Auto-Terms-of-Service-and-Privacy-Policy/issues/4

Please how do I edit the content, for Instance delete part of the contents.

As of Version 1.6 from April 27, 2015, the shortcodes allow for filtering.

Search through https://github.com/cliffordp/Auto-Terms-of-Service-and-Privacy-Policy/blob/master/auto-terms-of-service-privacy-policy.php for apply_filters to see where you can inject your own code (e.g. WooCommerce / WordPress username).

However, the actual content (Terms and Conditions, Privacy Policy) is not filterable.
I thought I already had this idea written down, but I guess it was just in my head. Now I’ve added it here: https://github.com/cliffordp/Auto-Terms-of-Service-and-Privacy-Policy/issues/17

Pull requests or paid customizations for the community’s benefit are always welcome!