I am using October CMS and would like to bind a theme folder to a separate domain.
Will this affect the domain that October CMS is currently on?
Thank you.
Related
I have an ASP.NET MVC 3 website hosted in a shared server.
I want to create a WordPress blog in /blog (www.domain.com/blog).
I've created a Virtual Directory in my admin panel pointing to the blog directory which has all the WordPress files.
When I navigate to www.domain.com/blog, I am receiving the following error message:
Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
So:
Is it possible to have a Wordpress blog (PHP) running in /blog?
Is this approach (Virtual Directory) correct? If yes, how to fix this error?
If it is not correct, how could I get /blog running?
I'd like suggest a different approach, that I did with my project and seems to be a stable solution.
Create an area "Blog" in your existing ASP.NET MVC project.
Use this pretty simple repo to create front end of blog into that area. Ignore admin part.
https://github.com/VJAI/JustBlog
Use Wordpress API's as your data engine to to populate data in your newly created area.
https://developer.wordpress.com/docs/api/
Edit robot.txt of your original Wordpress blog and stop it from being crawled by search engines. If possible put old wordpress blog under maintenance mode as well.
You will have your new blog at www.mywebsite.com/blog
You'll need a virtual application not a directory. Furthermore, your host must have PHP configured properly for IIS; not all do this.
Lastly, you will likely need a web.config file in the blog directory to "undo" any ASP.NET configuration inherited from the root. This will be specific, based on your root app. Give it a try without worrying about this first.
I have an existing grails app with multiple forms. I need a CMS which allows me to add existing grails forms to this cms and assign each form different permissions. I need to be able to change site template css from admin page. Something like dotnet nuke where you can add existing asp.net page and assign permissions to this page and add custom theme.
Features requested:
Integration with Active Directory
Integration with MS Exchange
Set up grails form security policy from protal admin ui
change form css theme from portal admin ui
easy integration with portal
I'm not sure exactly what features it supports, but Weceem is a CMS implemented as a Grails plugin, so that's an obvious starting point.
There is Maglev plugin for Magnolia that you can use, but AFAIK it works only with 4.5.x branch, not with the latest version.
Other then that, if your main requirements are security and being able to pull the theme from CMS, you can deploy Magnolia and your grails app in same web app, configure Magnolia to handle all incoming requests (that's by default) and only configure bypass inside of Magnolia for cms subchain for url where your form is available. This way Magnolia will take care of the URL check the security, make context available for you and you can refer from your form to the theme that is selected by editors in your Magnolia installation. While this description sounds probably a bit convoluted, it's actually very simple to do.
HTH, Jan
I have task to create site that contains some subsites. This subsites will use same database and will have relations. Their domain names should differ. For example, domain is www.mysite.com. Subsites are
www.books.mysite.com
www.blog.mysite.com
www.sport.mysite.com
I need a help about a project structure to start this application. Can anyone give me any idea? Can I create some MVC4 projects in one solution? or can I do this with Domain Routing?
This has been answered elsewhere, but not in great detail, so I'll collate the relevant points here.
A Visual Studio solution has no actual relation to the deployment of the site; it's just a container for various projects. When you deploy these projects, you can define bindings for them in IIS. This is a relatively straightforward process; if you're doing it the simple way from the UI you'll get something like this:
which lets you define which addresses point to where. During development, you'll need similar bindings in your host file to play the part of these IIS bindings for your local machine.
I downloaded Visual Studio Express 2012 RC for Web, created an ASP.NET MVC 4 application, click on F5 and see a basic, functioning site with Database in Chrome:
Now I want to publish this to my web hosting provider (domainbox.de) which has "ASP.NET 1.1 to 4.0", but not to the main site (tanguay.de) but to a sub-directory (e.g. tanguay.de/test).
However, when I right-click on the solution name and choose publish, I can upload via FTP, but it seems to only be giving me the ability to publish to the root of my domain. This is how I remember how ASP.NET 2.0 worked as well--it was impossible to have multiple websites hosted in sub-directories.
How can I publish this site to tanguay.de/test and then create another site and publish it to tanguay.de/test2, etc. Is that possible?
In the Target Location field, you can put the full path to your site, e.g. tanguay.de/wwwroot/test2 (or whatever path it maps to).
I've created a basic website using the Orchard CMS, and attempted to deploy it to my shared host, Softsys, using Web Matrix (via FTP). Currently, the site technically "works", however it looks like all styling has been removed (even from the dashboard).
Is there a step or files that I missed while deploying the site? I know "Web Deploy" is probably the preferred method of deploying, but I'm pretty new to this, and was not sure what the login specifics were, or how to obtain them for web deploy.
Here is a screenshot of what the site currently looks like deployed:
Edit: it turns out that the problem was on my host's side, for some reason the virtual directory was not being created properly - I still am curious what the proper/best practice method to deploying is however.
It looks like you have no theme applied. Check whether you have your theme existing in ~/Themes folder and properly enabled in the admin Dashboard. Maybe the /Themes folder content hasn't been copied?
UPDATE
If your hosting provider allows the option to deploy sites via WebDeploy - that would be the best one.
The easiest and most straightforward way to deploy Orchard site is to:
Have the ASP.NET application properly configured in IIS and accessible. If you use hosting - provider does that for you. If you'd have a dedicated server - you have to set up an application yourself.
Grab the deployment package from Codeplex, or build one from the sources.
Copy the whole package to your site's root (via FTP or WebDeploy).
Run it and proceed with the setup.
Basically - these are the same steps as for every "ordinary" ASP.NET application.
You probably need to set IIS user to have write access to some of the folders: Themes, Media and App_Data.