Am I missing the BIG picture?
]]>I successfully connected AlexaCRM to our CRM (on-premises). Data transfer seems to work, although I only used the deprecated features (msdyncrm_form, msdyncrm_login etc.) and directly pasted that into the edit section of my pages.
The Alexa documentation rather recommends using “Twig” for such things, but I’m a little lost there. I believe I could understand it faster by seeing a concrete example.
For instance, what would I paste in the edit section of a given WordPress page if I wanted to display a list of all contacts (all attributes for now) in the CRM?
Any help would be appreciated!
Lukas
I’m versed enough with ACF and using some of the plugins like CPTUI, and some page builders etc. I’m noticing that w/ACF Extended, you can actually build some page items directly. Unfortunately, I don’t see much by way of tutorials/examples of how to build things with the plugin. Looks like it has MASSIVE options, but for the semi-noobs like myself, I wouldn’t know where to start. Any insight from anyone?
Thanks,
Lyle
]]>EXAMPLE 2
“By pressing “Submit” I confirm and give permission to process my personal data.”
Example 3
“When you submit this website form your personal data will be stored in this website such as your IP address, your e-mail, your text of the comment and data of website form fields. Also, for security reasons and to protect this website from spam, your data will be processed in the CleanTalk Cloud Service and they will be stored in log files for 7 days by default (45 days if the extended package is active). On the expiry of the mentioned period, they will be deleted completely. CleanTalk may use information of spam activity of IP/email addresses to offer proper anti-spam protection to all websites connected to its service. It concerns exclusively those IP/email addresses that are being used for spam mailing.”
at this https://cleantalk.org/publicoffer#privacy
]]>If so, is anyone willing to share url example(s)?
]]>Would you consider providing more examples using code for displaying on the front end?
I guess anything beyond displaying a defined calculated field would need to be coded in its’ own right. Like totaling columns of returned rows.
]]>