Open robertjf opened 11 months ago
Good point. I really need to get back to https://github.com/patrickdemooij9/SeoToolkit.Umbraco/pull/175. That also probably needs to have the same changes done as you suggest here.
Possibly one of the biggest hurdles is the fact that content is stored in the database - Matt Brailesford may have an approach to this that could work - see https://github.com/vendrhub/vendr-deploy - there's an issue (https://github.com/vendrhub/vendr-deploy/issues/1 - Deploy Stock Values) that talks about data in databases but is unresolved, so not sure if he got it working.
How hard would it be to reconfigure SEO Toolkit to store data in a property on the document itself instead? Even if we somehow "hid" that property from the standard editor and placed it in the Content App where it currently is... Of course, the configuration will still need to be deployed (which still exists in database)
To us, this is pretty much a must have feature. So +1 on this.
To be truly useful on an Umbraco Cloud instance, we need an Umbraco Deploy plugin to be able to transfer both the SEO Node data and the configuration across from one instance to another.
To support this, we will need to modify the database tables and any reference to the integer-based NodeId to use the Guid-based Key instead, as there will be conflicts/inconsistencies in the integer-based NodeIds from one instance to another.
Currently, if we implement SEO Toolkit on an Umbraco Cloud project, we need to copy over any configuration as well as any metadata if we restore or push nodes between instances.