first of all nice that it goes on that pleased me very much. Basically once the question is a backward compatibility with old versions planned so that you can update. Or is to be seen as a completely new independent version, which will have nothing to do with the old version?
@fschuermeyer Data structure and field types changed and it is not planned to provide an auto migration option from the old version to the new one. Of course you can get paid migration support if needed.
@Cryptospy Cockpit was and still is an Open Source project. If you see that something is lacking, eg documentation, then feel invited to contribute to the project.
One of the reasons for the new pro version is to hire additional resources in the future to keep the docs updated and thrive Cockpits development.
Donations just didn’t work in the past to be able to commit and focus 100% on Cockpit (docs, guides etc).
Hey! Nice job. I have a small problem. Can’t seem to find a way to create a new item in a collection trough the API. Can’t find the endpoint for saving data. Can you point me in the right direction please?
When using a Tags field: If you create an entry with a specific tag then delete that tag from the model it still shows in the json object for the entry. But if you go in an edit the entry, that deleted tag is not visible in the tag list and the only way to remove it from the json object is to update the tag field, which requires you to add or remove tags from the actual tag field.
Consider: Showing tags in the field that are not in the model with a different background color to indicate they are old/deleted/invalid. That way we can hit the (X) to remove and actually trigger that update, if we desire that content to be removed.