RequireFeaturesallows a module to contribute to services/pipeline to other feature without depending on it
OrchardCore.Feedsis activated it doesn't activate
OrchardCore.Contentis active, then activating
OrchardCore.Feedswill also has services/pipeline related to content management
If your module has dependency of "OrchardCore.Forms" in manifest .cs then you can override using Views/Form.Wrapper.cshtml
So this set me off on the right direction. If I create that file in another one of my modules, it works fine, but in the module that the file belongs in, it refuses to work. Both modules show up in the features section in the orchard admin, and work fine otherwise. Both modules also have
OrchardCore.Forms listed as a dependency, and both are listed as projectReferences in the csproj for the startup project. Any suggestions for me to try?
System.InvalidOperationExceptionbeing thrown in my debug output, but I can't find out why my module's recipe is failing (or if it even is the recipe). It's also weird that when enabling the feature, it is enabled but doesn't even report that there were exceptions. I couldn't find a logging feature either.
var jobs = await Orchard.GetRecentContentItemsByContentTypeAsync("JobPost", 9999);to get all content items of the type "JobPost" on my Razor page (decoupled site). I just recently deleted several test content items that I no longer needed, but they keep showing up when I generate this list of content items. And new content items that I have just created are not showing up. Is there something that needs to get refreshed somewhere in order to get an up-to-date list of these content items?
Module B.FancyFeature. If I don't add Module B as a package reference in my startup project,
Module B.FancyFeaturedoesn't show up in the features list, even if it is listed as a package reference in the Module A .csproj, and Module A has the specific feature I'm using (
Module B.FancyFeature) listed as a dependency. Make sense?