This project is read-only.


version: 3.0.4
date: July 24 2013
saved by: Yasushi Ogura

01 Overview

01-1. ogEditor - CMS + Editor

OgEditor V3 is XML-based rather than using a database, has been designed specifically with the needs of small business and individual site owner, and offers a lot of powerful design features but simple and limited content management features. OgEditor V3 is free and takes about a few minutes to install.

It offers a complete integration package for ASP.NET

  • CMS Features
    • Admin panel
    • User management
    • File/folder access control
    • Drag and drop uploard of an entire file/folder tree.
    • Html5 package-template registration
  • Design Features
    • Html5 and Css3 designing
    • An entire page editing capabilities including meta tag, header style, and js.
    • Multiple-page editing
    • Integrated file manager with upload capabilities.
    • Auto reformat.
    • Dynamic file editing
    • Visual css and html tag designing


02 Minimum Requirements

02-1. Requirements


  1. IIS
  2. ASP.NET3.5
  3. Ability to set file permissions to include create/read/write (or better) for the user that "owns" the Application Pool for your site (NETWORK SERVICE, typically)

02-2. Cross Browser Compatibility

Compatible with Chrome, Firefox, Safari, Opera, and Internet Explorer 9+

03 Integrating ogEditor into Your Site

03-1. Case 1: Using ASP.NET Web Hosting Provider

Suppose you are using IIS hosting provider.

  1. Sign In from , download the integration package from store on your desktop.
  2. Unpack the content of the zip archive.
  3. Using FTP client, transfer all the contents inside ogEditorV3 folder and place them on the root directory of your site.
  4. Go to http://YOURSITE/ogeditor/index.aspx.
  5. Since it is first time to open OgEditor CMS, your will be asked to create Administrator account.
  6. Enter all the required fields, then press Submit button. New admin account will be created and the page http://YOURSITE/ogeditor/settings.aspx will be displayed. ( refer to the screenshot below ).
  7. Login with admin account. The Admin Panel shown.
  8. Click on "Edit" button.
  9. Click on "Choose Workplace" button then select the workplace for end users. ("/", typically).
  10. Scroll to bottom of the page. Click on "Submit" button to save the change you made.
  11. Click on "Go to Editor" button then Editor page is displayed.
  12. Now, you can browse files with FileManager located in the right side of the editor window.
  13. Click on the file you want to edit.
  14. Press preview button for displaying page preview.

03-2. Case 2: Merging OgEditor V3 CMS with the existing ASP.NET web application.

OgEditor V3 CMS uses the namespace "OgEditorV3.ogeditor". Which means your root project name should be "OgEditorV3". For instance, suppose you have a project called "ProjectA" and a class in a file in the project's folder. Then the correct namespace for that class should be "ProjectA". However, if the class is in a file, which is in a folder "Sub" inside that project, then the correct namespace should be "ProjectA.Sub". Every ASP.NET Web application project starts with a Namespace, by default the same name as the name of the project or application.

So as long as you use "OgEditorV3" as your root project name it is no issue. However, if the original root project name cannot be changed a little extra effort required. Here is the solutions.

  1. You might create sub-project in your root project. I cannot say it is possible since I never tried. But the details can be found here => Part 1 of 3: Creating sub-projects in IIS with Web Application Projects
  2. Or I am plainning to provide another option which is the preparation and delivery of the precompiled package with your root project name as project namespace. Since it requires my little efforts, it costs $10.

For more info please check the links below.

Last edited Aug 6, 2013 at 12:20 PM by yahsushi, version 3


No comments yet.