SeoToolkit permission?
# help-with-umbraco
j
I installed SeoToolkit first locally in my dev site and it worked like a charm! Then I published it to live/production and I get these 404 not found problems. Any idea what I can do to fix it? Permission problem? https://cdn.discordapp.com/attachments/1215264233743187968/1215264234196303942/image.png?ex=65fc1e03&is=65e9a903&hm=93614880a892b7c334243657a623fac54ed51f499aea47584c00463c373f93f5&
/App_Plugins/ does not have SeoToolkit locally either so I assume it is located in the DLLs?
@Patrick de Mooij can you help me out please? 🙏🏻
p
Ehmm.. What version are you working with?
j
Latest Umbraco, latest SeoToolkit (13.2.0 & 3.5.0)
@Patrick de Mooij no idea? Running english backoffice both locally and production
p
Sorry, I didn't have notifications enabled so I totally forgot about it, I enabled them now. The issue you linked indeed seems related, though it would only be an issue on Mac or Linux. Is your production machine on Linux?
j
No it is on a windows server.
Something seems to prohibit read access to the static files. Language files seem unavailable as well, names are in [brackets]
It still produces the sitemap.xml file as expected but all backoffice UI is unavailable
One difference is that locally I run IIS Express but on prod server I run IIS
p
I see we had this issue a few years ago as well 😛 https://github.com/patrickdemooij9/SeoToolkit.Umbraco/issues/74
This is what you wrote as a fix the last time:
Copy code
It seems I have managed to solve it now! In my Mac setting I removed all SeoToolkit NuGet packages and then installed the Sitemap package only and published with dotnet publish -c Release and then the files were there in wwwroot/App_Plugins!!
I repeated the same procedure in my Windows setting and voila! the files were there as well!
So it seems like removing and adding the package was the solution (in combination with looking in the correct App_Plugins folder). Big thanks for your effort to help me out, much appreciated!!
j
yeah I know I had some issues before. But this time it is another project and I made a clean install from scratch of SeoToolkit. But I will have a look at it to see if something may be related. Thanks for responding.
But indeed... I repeated the thing with dotnet publish -c Release and there was this SeoToolkit folder in wwwroot/App_Plugins! So what was my mistake here? Did I miss (again) to read some instructions in the docs that this action is required for publishing the files?
p
Did you not use the publish before?
j
Not from command line, only from VS UI
But now when I do it I can see the files getting published. Strange...
Maybe I just confused the App_Plugins folder in wwwroot with the one in the source root. And didn't copy everything. Or it was the reinstall of SeoToolkit that made the difference. I don't know. Most important thing is that it works now. Thank you again so much for your help and patience with me 🙏🏻
p
Happy that it works again 🙏🏻 Even if it is a mystery on what actually happend
e
Having a similar problem. Have a plugin to import some data (works locally, and same logic for other import has been used for customer in a live environment before). Throught I'd continue this thread and see if any of your advice will help 🙂 This is all going to Azure through github actions, and everything is green. Can see the file in the repo of course, but for some reason it's gone when login on to the live CMS. https://cdn.discordapp.com/attachments/1215264233743187968/1216944780391747605/image.png?ex=66023b25&is=65efc625&hm=9cbe0e8a00f0fc22ba3d8f7e58fd0d1fb5db31f83abf278af5fa0889a6b93909&
21 Views