Yes I normally like to lock external API packages to an explicit git tag for that reason. Problem is, there's no working stable version tagged I can lock to without guzzle dependency conflicts in my app. Like you said, I'd either need to go really old with the SDK (to bypass guzzle), or lock myself to this specific commit on development branch, since I've tested and know it works. That said, I just found out I can dump my fork and lock to this specific commit: "constantcontact/constantcontact": "dev-development#d002af0ac2f777bde569e0d0ba567e0133f525ba" Thanks again!
... View more
Currently, we are limiting custom field access to a specific format for validation purposes. As has been mentioned multiple times in the forum and customer communications, we are in the process of upgrading our entire contact management system. There are a lot of changes going on with this migration and upgrade including how custom fields work. As such, they may appear differently in the UI depending on if you are on our new contact management or old. However, to maintain predictability for developers during this migration and upgrade we are requiring a specific format so that we can guarantee that the API does work as expected.
If you run into any unexpected behavior or errors, please let us know. This is a massive migration and while we have done our best to test and predict everything that could happen, as with any massive software migration it's likely we've missed something and will need our communities help to find and fix any of those items.
... View more