Locally, I can run the site, although at agonizing slow speed (100% cpu usage all the time), and it seems SEO Checker is creating some config files that are 2000+ lines long for each language.
On our live server, the site just completely crashes.
How do I create the configuration file, and what do I need to put in it?
I had a similar issue installing SEOChecker 2.2.4 through nuget. The /App_Plugins/SEOChecker/config/SEOChecker.config file was not added. I had to create it myself. Creating it seems to have solved my problem.
I noticed the config file is included in the installation locally but was not included in the solution itself, so the .csproj was not aware of it, so if deploying by VS solution it would be ignored and not deployed.
Missing configuration file?
We just installed SEO Checker in Umbraco Cloud 7.8.1.
When I try to access the Configuration part of the SEO Checker locally I get the following exception;
Locally, I can run the site, although at agonizing slow speed (100% cpu usage all the time), and it seems SEO Checker is creating some config files that are 2000+ lines long for each language.
On our live server, the site just completely crashes.
How do I create the configuration file, and what do I need to put in it?
Hi Jon,
Sorry to hear config file is causing an issue. If you follow manual installation steps in the user manual all should be good again https://soetemansoftware.nl/seo-checker/downloads
Best,
Richard
Thanks! Found the config file and copied it to the correct location. Seems to have fixed the issues locally.
Hope it will fix the live issues as well. :-)
I had a similar issue installing SEOChecker 2.2.4 through nuget. The
/App_Plugins/SEOChecker/config/SEOChecker.config
file was not added. I had to create it myself. Creating it seems to have solved my problem.I noticed the config file is included in the installation locally but was not included in the solution itself, so the .csproj was not aware of it, so if deploying by VS solution it would be ignored and not deployed.
is working on a reply...