-
Notifications
You must be signed in to change notification settings - Fork 28
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
Metafields working on localhost but not on live page #271
Comments
Hi @HeadMathematician |
Hello @patrickdemooij9 |
Hi @HeadMathematician |
Hi again @patrickdemooij9 |
@HeadMathematician I think the reason why this doesn't work is because the App_Plugins on publish should actually be located in the wwwroot, but I am not sure why that isn't done by the package itself. You could try moving it yourself and seeing if that works. |
Hello again @patrickdemooij9 I did what you suggested, App_Plugins is now moved to wwwroot, the localhost version still works as before (haven't noticed something was broken). But we have good news and bad news on live umbraco page. Good news is that now at least I see the edit button, so the metafields is showing signs of life, but bad news is that I have an error which I will attach below causing the issue with listing the metafields properties. You may see how metafields page looks now and the error on the console. |
Hello,
Our company is using Umbraco v9.5.0 and we have installed SEO toolkit for umbraco --version 1.0.0. Everything seems fine (not all is yet tested), however Meta Fields don't have 'open settings' options for the fields on live version e.g. mypage.com/umbraco and on localhost/umbraco it's working perfecly. We have found a way around it if we publish everything on localhost/umbraco and then restart our app on azure, then the changes on the very site are applied but we still don't have those options on our site mypage.com/umbraco.
We even encountered an error on Content -> document -> SEO:
"umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:152 TypeError: Cannot read properties of undefined (reading 'forEach')
at handleResponse (seoSettings.controller.js:48:22)
at seoSettings.controller.js:39:21
at umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:165:235
at m.$digest (umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:176:385)
at m.$apply (umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:180:259)
at k (umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:131:309)
at v (umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:136:422)
at y.onload (umbraco-backoffice-js.js.v22b435b7deae00621b9399792935a966963e9fa8:137:335) 'Possibly unhandled rejection: {}'"
You can see it on the attachments:
So on the localhost everything works regarding meta fields, both document type settings and content meta fields editting.
The text was updated successfully, but these errors were encountered: