Closed leethomascook closed 7 years ago
After a bit more debugging, it was related to me having set it to use a camelCase JsonFormatter. This had never affected any other plugins though, which is odd.
GlobalConfiguration.Configuration .Formatters .JsonFormatter .SerializerSettings .ContractResolver = new CamelCasePropertyNamesContractResolver();
As a side note, I had to download the source and compile against 7.5.3 to get this to fully work. The version on nuget did not work with 7.5.3.
Hi Lee, thanks for the report. Sounds like we have some issues to deal with in 7.5. What did you have to do to get it to compile against 7.5? If its something you would want to send a pull request for that would be great.
Thanks!
From: Lee Cook [mailto:notifications@github.com] Sent: Monday, October 17, 2016 6:32 AM To: scyllagroup/UmbracoFlare UmbracoFlare@noreply.github.com Subject: Re: [scyllagroup/UmbracoFlare] 404 on /umbraco/backoffice/UmbracoFlare/CloudflareUmbracoApi/GetAllowedDomains (#6)
As a side note, I had to download the source and compile against 7.5.3 to get this to fully working. The version on nuget did not work with 7.5.3.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/scyllagroup/UmbracoFlare/issues/6#issuecomment-254171803, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMKW_W8FlfqMweCEIasS8eReKuA05SyOks5q0069gaJpZM4KYa5q.
Same problem. Get the JS error... Any news on when an updated Nuget package will be done to support v7.5+
Sorry it took so long to get up a new version. I just put up a new version for 7.5.6 on Nuget. Let me know if you are still having the same issues.
Hi,
I have installed this on a 7.5.3 installation and I always get a 404 for this request. I have debugged the routing and it seems to be in the dictionary, which is weird.
This request: /umbraco/backoffice/UmbracoFlare/CloudflareUmbracoApi/UpdateConfigStatus
It does return a response, such as: '{"purgeCacheOn":true,"additionalUrls":null,"apiKey":"xx","accountEmail":"xx@xx.xx","credentialsAreValid":true}
But then i get message of: "We could not validate your credentials.', which somewhat contradicts the response.
Thanks,
Lee