@jeverdrengen Try checking your log to see if there is any function load errors or compilation errors for your News Function.
If the function responsible for showing a specific news item fails to initialize, C1 won't run in and there won't be anyone to register the PathInfo and in turn you'll see a 404 error.
I could really need a hint to where I can debug this.
The Requested URL(pathinfo) inside the console: http://www.halsnaesskolen.dk:80/Forside/Nyheder/c1mode(unpublished)/c1mode(relative)/2018/10/27/Invitation-til-åben-skole
On the website: http://www.halsnaesskolen.dk:80/Forside/Nyheder/2018/10/27/Invitation-til-åben-skole
If I edit a news item everything works fine. So the data is there!
Could it be a folder permissions issue on the server, added by the webhotel?
@mawtex I have posted the log in a earlier thread: Failed to clean up ghost file 'd:\web\localuser\halsnaesskolen.dk\public_html\App_Data\Composite\DataStores\Composite.Data.Types.IUserConsoleInformation.xml'
And it is not possible to preview the news item but it is possible to edit all of them and see the content. And yes it is the standard news function I have installed. It has been working for almost a year.....
If you want to look at upgrading the compiler used by C1 you should take a look at all instances of the CSharpCodeProvider https://github.com/Orckestra/C1-CMS-Foundation/search?q=CSharpCodeProvider&unscoped_q=CSharpCodeProvider
These should ultimately be changed to use Roslyn - should be enough to change the usages of CSharpCodeProvider to
service.AddTransient<CodeDomProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider>(), that way you're always free to change the compiler being used later from site to site
@burningice2866 Thanks so much for this. I was talking with another developer I work with about this yesterday and he was able to take the uncompiled composite project and found that it was using an old outdated NuGet package that had been replaced for C# 6.0+.
He swapped out the old one with the new one and that got me to where it just seems to be blowing up on C# 7.1+ features.
The .csproj file was so old that it would only open in VS 2015 so he had to rebuild that to even get it to open in VS 2017 so I could actually support C# 7 since
VS 2015 only goes to C# 6 . The last bit he did was he had to update the Rosyln compiler version for the Web project and tweak a couple of other things (not sure what those were) but we are now able to use generated data types without the CMS blowing up due to language version within App_Code.
@jbert50021 is this custom datatype of your a part of your overall navigation and url structure of the website? If so one way is to make the SiteMapProvider, which sitemap.xml is generated from, aware of this datatype and all its urls.
You do this by implementing
ISiteMapPlugin and adding it to the service collection in your ConfireServices method
For starters, you can see how regular pages are handled by the SiteMapProvider since its written as a plugin as well
Hello. I would like to implement PWA features but I have come to the point where I have one last step that needs to be updated in the http response. The
Vary header is added with
* and I can't find where it is added. Also I have tried to remove it using
<remove name="Vary" /> then
<add name="Vary" value="Accept-Encoding" />
What is the best way to organize deploying and synchronizing among dev and production server? Sometimes we do first changes (controls, content, add new types and metadata) on the dev server and some times we modify the production one. Is there any pattern or mechanism to synchronize data on both servers?