Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Umbraco Deploy #232

Open
robertjf opened this issue Sep 18, 2023 · 3 comments
Open

Add support for Umbraco Deploy #232

robertjf opened this issue Sep 18, 2023 · 3 comments

Comments

@robertjf
Copy link
Contributor

robertjf commented Sep 18, 2023

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.

@patrickdemooij9
Copy link
Owner

Good point. I really need to get back to #175. That also probably needs to have the same changes done as you suggest here.

@robertjf
Copy link
Contributor Author

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 (vendrhub/vendr-deploy#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)

@aguyfromdenmark
Copy link

To us, this is pretty much a must have feature. So +1 on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants