I have setup Orchard core 1.2.2 but items under the admin side bar 'Configuration > Recepies' always shows "Nothing here! There are no recipes for the moment."Orchard recipe item
Then I try to add a test recipe with Recipes folder as the instructions of https://docs.orchardcore.net/en/latest/docs/reference/modules/Recipes/ still remain the same result. But the new recipe can show when I build a new sites.However, it still not showing under the admin configuration as before.
orchard recipe during setup
I try to use import JSON thru configuration menus but still nothing showing.
Please advise how I can solve the issues.
Thanks in advance.
I am by no means an expert however I have noticed today that it's better to create the OrchardCore CMS project by entering the commands as follows, which will yield a "more complete" installation/configuration initial page that includes the Recipe dropdown list along with the Default Time Zone dropdown, both of which are missing when adding the OrchardCore.Application.Cms.Targets Nuget to an empty ASP.NET .NET6 app. So the commands are (the --logger serilog is optional):
# mkdir MyCmsSite
# cd MyCmsSite
# dotnet new -i OrchardCore.ProjectTemplates
# dotnet new occms --logger serilog
As a result you will get a CMS site ready to be configured, just run "dotnet run".
You will also have the following project templates available in case you decide to create them later on:
Template Name Short Name Language Tags
------------------------ ----------- -------- --------------------
Orchard Core Cms Module ocmodulecms [C#] Web/Orchard Core/CMS
Orchard Core Cms Web App occms [C#] Web/Orchard Core/CMS
Orchard Core Mvc Module ocmodulemvc [C#] Web/Orchard Core/Mvc
Orchard Core Mvc Web App ocmvc [C#] Web/Orchard Core/Mvc
Orchard Core Theme octheme [C#] Web/Orchard Core/CMS
Source: Code Generation Templates
'Configuration > Recepies' only displays Recipes that are not setup recipes.
Also receipies tagged with hidden are also not visible in admin.
Related
I created a site on dotnest. I want to create a custom theme. The documentation tells me to start the command line interface.
Okay, I get the latest from GitHub and follow the instructions. dotnet run works! Great!
Since I need orchard.exe to create a theme, I change into the correct directory and try to run. Even after building, there is no bin\Orchard.exe in the dotnet core version. I check the source code and all of the Program.cs files start web servers.
How do I run the orchard command line so that I create a theme so that I can install it on dotnest?
As #Hazza mentioned in his comment, DotNest runs on Orchard 1, so you will need to download Orchard 1 from GitHub (https://github.com/OrchardCMS/Orchard/releases/tag/1.10.2) and use its Orchard.exe program to generate a theme project.
DotNest provides further instructions here to create a custom theme for DotNest: https://dotnest.com/knowledge-base/topics/theming/
I am evaluating Orchard 1.9.2 as I am looking for a CMS where I can have a staging area so that users can test and approve content on a staging site before committing changes to live.
I installed 1.9.2 both locally and on Azure, and also the Orchard Deployment module (Wng.Deployment). Setting up and pressing Test on the Sources and Targets tab works, but when I try to create a deployment I get the YSOD
Shape type DatePickerLocalization not found
Source file: d:\home\site\wwwroot\Modules\Wng.Deployment\Views\EditorTemplates\Parts\Deployment.Subscription.cshtml
[OrchardException: Shape type DatePickerLocalization not found]
If I enable the Shape Tracing module, the error message changes but it still doesn't work.
It appears that the Orchard Deployment Module isn't compatible with 1.9.2.
Any ideas on how I can achieve this?
I have a couple of general questions please. Just stepping into Orchard CMS. So apology if they look stupid!
Today I installed a theme called Metro from Theme Gallery. It is visible on theme selection page as well. But where the files and folder structure are got saved in Orchard CMS? I looked into Theme folder but it is not there. I want to see how the structure is placed so that I can create one myself
One more thing. Theme .png file shows a nice layout but when I activate it the layout comes up completely different. Why is this?
And finally, I installed my site using Orchard's web interface and it is running fine. But when I tried to run orchard > codegen theme CreditLine, it said Command codegen doesn't exist.
I then run Setup utility from command prompt (orchard >) and it displayed
A previous Orchard installation was detected in this database with this table prefix.
Which clearly says the setup I did through web interface was successful. But still I am not able to run codegen command or even help codegen. The latter command shows Command codegen doesn't exist!
Orchard version: v.1.10.1.0
1) It should be installed under Themes/TheThemeName, or locally, under src/Orchard.Web/Themes/TheThemeName
2) It could be that you installed an old theme. Not sure because you don't give many details over what goes wrong.
3) You first have to enable the codegen module. Do this by starting up your Orchard, go to modules => Codegen => Enable. Or run in the orchard.exe: feature enable Orchard.CodeGeneration
After a lot of Googling and struggle I found a nice community here where I got my answer!
Orchard Repository on Github defaults to dev branch which I overlooked completely when cloned it for the first time! So I removed everything from my local and cloned the source again but from master branch this time.
No more compilation error or Command Line issue popped up. Orchard.CodeGeneration feature got enabled from CLI this time without a problem. Everything else seems to be working fine as well.
Steps:
1. Removed source from my local which I cloned from dev branch initialy
2. Cloned Orchard from master branch
3. Opened solution in VS2015
4. Compiled, run and setup my first site
5. And finally ran feature enable Orchard.CodeGeneration from orchard command prompt.
So I'm building an MVC6 app in Visual Studio 2015 and have managed to figure most stuff out, however, I haven't yet worked out deployment.
In MVC4 (what I was using before), our process* was publish to a folder, then setup the website in IIS (Right-Click on Sites -> Add Website).
Actually, our process is set it up in IIS and TeamCity, but not for test apps like this :).
I followed this process and obviously it's trivial to setup the IIS website and publish to the correct folder...but that does not actually work for me.
We're running IIS 8 on Windows Server 2012 and we've installed the .Net 4.6 runtime on the server.
The following steps have worked for me and should help you host your project on IIS.
Using Visual Studio 2015 Preview as your IDE,
Create an ASP .NET 5 Starter App.
Check that it is working outside of IIS.
Once complete, publish the application. In this example, I have selected the location C:\PublishWebApp.
3.1. When publishing your application, make sure that you have:
Disabled precompilation
Selected amd64
(See image below)
Upon a successful publish, go to C:\PublishWebApp.You should see the folders approot and wwwroot inside.
Now open the IIS Manager (I am assuming you have the ASP .NET 4.5 feature enabled)
Create a new website.
6.1 : Select the wwwrooot folder as the website's physical path. In this example, it is C:\PublishWebApp\wwwroot.
Check the website to see that it is working. If you encounter any errors, please post them here.
If the precompile option is ticked in the Publish Web Settings window pictured above, then you must
Go to the wwwroot folder of your published web application. In this example, it is C:\PublishWebApp\wwwroot.
Locate web.config.
Inside the folder of your published application, there is an packages folder inside of the approot folder which should contain a folder named after your application, with a folder for the version underneath. Inside that folder should be a folder named root. In web.config, set the value for the key kre-app-base to the root folder. For reference, see the line of code below. In this example, the application name is WebApplication10.
<add key="kre-app-base" value="..\approot\packages\WebApplication10\1.0.0\root" />
I Spent hours on debugging the issue finally got it worked, steps:
1) Publish your MVC6 application using visual studio into file system, make sure you are selecting correct DNX Target version in my case its dnx-clr-win-x64.1.0.0-rc1-update1.
In the output folder map "wwwroot" folder to your applicaiton in IIS (DO NOT Map it to sup-applicaiton, only ROOT application in IIS works with DNX for example "Default Web Site").
I have just spent a day trying to get this working. i found this here (search for posts by GuardRex) invaluable, complete the steps the accepted answer gave, that's the start of it.
Pretty much if you try to add an application to a site there is bunch of workarounds and extra configuration needed that is detailed in the link.
For starters:
1)Make sure you have the HttpPlatform handler installed here
2)Seems obvious but make sure .net5 is installed on your server here
I know this is if you are adding an application to a site, but there's some pitfalls and much needed refinements needed for the deployment process at the moment that everyone should be aware of.
Im new with liferay have a problem with portlet deployment using the plugins sdk,
Platform:
liferay-portal-tomcat-5.5-5.1.2,
liferay-plugins-sdk-5.2.2,
windows vista.
Problem:
I have successfully created a sample portlet with ant and deployed it into the hot-deploy folder. It is automatically picked up by the server but the console messages say that the portlet has been copied successfully and never registers it.. and i cant find it in the add application drop-down menu.. pls your help will be very appreciated.
I don't know if anything important changed in these versions, but you say you're using Liferay 5.1.2 with the plugin environment 5.2.2 - try with matching versions - at least on the second digit.
also, make sure that all required files are available - among them are WEB-INF/web.xml, WEB-INF/portlet.xml.
Create a new sample portlet with "create.bat" in the plugin SDK's portlet folder and deploy this - it should succeed. Then make sure that all config files from the new one are present in your current one.
How did you create your current portlet? What did you do/change?