I have several Manatee.Trello clients who have recently been broken without any changes on their end. They did note, however, that when they disabled the Custom Fields power up, it started working again.
The error that the API is returning is “invalid value for plugins.” I don’t have any request information, but as I mentioned, it was working up to a few days ago.
Has anything changed in regard to power ups or custom fields in the API?
One user noted that it started working for them when they disabled requesting plugin data. Maybe something changed around this parameter?
I don’t believe that we’ve recently shipped any changes related to plugins nor Custom Fields.
Digging through our codebase, I can’t find that error message invalid value for plugins. Does Manatee.Trello do any capturing of errors that would generate that error message?
It looks like we shipped a change where we started enforcing a validator on that parameter. The valid values are: none, enabled, available, all.
What I’ve not figured out yet is why this was previously working because that validator is very old.
Would that call actually include the plugins? I would expect us to have not been returning any sort of plugins. Or, if they were being returned, I think it was the default. But I wouldn’t expect the query parameter to have had any impact on whether they were there or not.
I was able to get a version of the server running locally for the commit prior to the one that introduced the validation checking and I confirmed that a call to /1/boards/{idBoard}/?plugins=true did not return any plugin information. However, it did return a 200 because we ignore unknown query params and values.
On the upside, you can now get plugins as a nested resource via query params and we’ll actually return the filtered plugins you ask for.