radiant / radiant-multi-site-extension

An extension for Radiant CMS that lets you serve multiple sites (domains) from a single instance.

Welcome to Radiant

Radiant is a no-fluff, open source content management system designed for small teams. It is similar to Textpattern or MovableType, but is a general purpose content management system (not just a blogging engine).

Radiant features:

• An elegant user interface
• The ability to arrange pages in a hierarchy
• Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org)
• A simple user management/permissions system
• Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters)
• An advanced plugin system
• Operates in two modes: dev and production depending on the URL
• A caching system which expires pages every 5 minutes
• Built using Ruby on Rails
• And much more...

License

Radiant is released under the MIT license and is copyright (c) 2006-2018 John W. Long and Sean Cribbs. A copy of the MIT license can be found in the LICENSE file.

Installation and Setup

Radiant is a traditional Ruby on Rails application, meaning that you can configure and run it the way you would a normal Rails application.

See the INSTALL file for more details.

Installation of a Prerelease

As Radiant nears newer releases, you can experiment with any prerelease version.

Install the prerelease gem with the following command:

$ gem install radiant --prerelease

This will install the gem with the prerelease name, for example: ‘radiant-0.9.0.rc2’.

Upgrading an Existing Project to a newer version

1. Update the Radiant assets from in your project:

    $ rake radiant:update
   

2. Migrate the database:

    $ rake production db:migrate
   

3. Restart the web server

Development Requirements

To run tests you will need to have the following gems installed:

gem install ZenTest rspec rspec-rails cucumber webrat nokogiri sqlite3-ruby

Support

The best place to get support is on the mailing list:

http://radiantcms.org/mailing-list/

Most of the development for Radiant happens on Github:

http://github.com/radiant/radiant/

The project wiki is here:

http://wiki.github.com/radiant/radiant/

Enjoy!

-- The Radiant Dev Team http://radiantcms.org

radiant-multi-site-extension's Issues

How does multi-site extension work?

How does the multi-site extension enforce a relationship between a site and a given set of pages, from the user's perspective?

It is not clear just from looking at the UI ("Sites screen").

Thanks,
Wes

Set up Travis CI hook

I don't have admin access. Could someone please configure the Travis CI hook?

'Page#url should alias default' FAILED

expected #<Page id: 652238563, title: "Home", slug: "/", breadcrumb: "Home", class_name: nil, status_id: 100, parent_id: nil, layout_id: nil, created_at: "2012-05-08 14:43:31", updated_at: "2012-05-08 14:43:31", published_at: "2012-05-08 14:43:31", created_by_id: nil, updated_by_id: nil, virtual: false, lock_version: 0, allowed_children_cache: ""> to respond to :url_with_sites

Travis CI script exits with 0 although there are failing tests

needs to be fixed

undefined method `tab' for

undefined method tab' for #<MultiSiteExtension:0x10344dfa0> /Users/ram/work/projects/git/radiant/vendor/extensions/multi_site/multi_site_extension.rb:28:inactivate'

Add Travis CI support

We should have multi_site added to Travis, with a badge in the readme file

Radiant multi-site flopping between sites and pages not updating upon saving

I'm noticing an inconsistent bug when I'm logged as an admin in radiant. When navigating from page to page, saving documents that re-direct me to it's parent page, switching from tab to tab etc, I often get redirected to the wrong site.

For instance, I'll be working on this page: http://[mywebsite_AAA]/admin/pages/37/edit

I will save it

and upon save, I get redirected here: http://[mywebsite_BBB]/admin/pages?root=37

but instead of being on the [mywebsite_AAA] site, I'll be looking at the ../admin/pages view of the [mywebsite_BBB] site

Any thoughts? This is a fairly serious issue if users outside of my company are working on [mywebsite_BBB] and are getting re-directed to our [mywebsite_AAA] site.

We have also recieved complaints from our customer with admin access to only one of the sites. In this case [mywebsite_BBB]

This is their complaint:
"As we discussed, there is a glitch when attempting to save changes/updates to the website. Eventually I am able to save, but it takes 4/5 times before the system accepts the change."

Ugliness in view

The admin view appears to be referencing old images not available in Radiant 9.1, so it looks ugly.

I have patched the view to clean this up, if someone could give me a couple of tips on the appropriate process to store back the changes.

'Page#url should override slug' FAILED

expected "/"
got "/some-slug/"

'Page.find_by_url should alias methods' FAILED

'Page.find_by_url should alias methods' FAILED
expected Page(id: integer, title: string, slug: string, breadcrumb: string, class_name: string, status_id: integer, parent_id: integer, layout_id: integer, created_at: datetime, updated_at: datetime, published_at: datetime, created_by_id: integer, updated_by_id: integer, virtual: boolean, lock_version: integer, allowed_children_cache: text) to respond to :find_by_url_with_sites

Opening the admin interface should go to the current site automatically.

When you go to the admin interface it is always on the default site. It should go to the current site with the default used in case of failure.