how to use it for existing d7 installation

HI igorik,

Thanks for the compliment, a Drupal distro is always installed and maintained on itself.
So you can't install it in a existing Drupal site.

Why do you want to install it in that existing site?
Maybe we can help with integration-tips.

-- Best, Joris

Hi @igorik,

What you might be able to do (I haven't checked the codebase, but I presume this is created using features), is take the features modules from the /profiles/openlucius folder and add them to you sites/all/modules folder. This would give you most of the functionality and you can tweak a few items if needed.

Failing that page (using profile_switcher module) might help you
https://www.drupal.org/node/1858384

Hi Joris,

In my case I managed to link openLucius to my existing site and it works well.

What I want is for my users - who are based on Profile2 - to be able to use the platform without having to reenter all their information.

For the moment only the username is visible, since most of my fields are based on profile2.

Would you have a tip on how I could use profile 2 fields with Openlucius?

cheers.

Anais

Hi Anais,

Thanks for the feedback, there is no out-of-the-box solution for this.
We'll have to take a look for you.

-- Best, Joris

Quite interested in this too.

I have a number of existing sites with quite a lot of individual content and starting out again with migrations would be a major undertaking.

BTW The latest update 7.x-1.6 is fantastic. Well done!

Hi Paul,

First of all, thanks for the compliments :)

Could you please explain a little but more: do you have existing vanilla Drupal sites, that you want to migrate to OpenLucius?
If so, why would you want to do that?

-- Thanks, Joris

I make websites for primary schools and they would really benefit from an intranet facility.

Most school staff have site editor access (via Organic Groups) and many are responsible for maintaining their own classes or departments on the public website.

This is why I was asking about whether openlucius could be bolted on, as I thought it would be easier to manage users and also achieve some UI consistency between the two environments. Also to bare in mind is the onboarding of users, with two quite different systems, but appearing to the average person to be all the same website.

However, since making my earlier post, the more I realise that openlucius will work better as a self-contained installation. The main reasons being a clear separation of content, and far fewer headaches with feature conflicts and updates.

This leaves the questions about user management, UI consistency and onboarding. I realise these are my problems and just hoping you can point me in the right direction.

- How best to have shared users between the two environments?
- How to ensure UI consistency, for example using the same wysiwyg?
- How to explain the difference with Organic Groups and OpenLucius groups?

More generally, I am curious to know how you are managing access control in openlucius? I note that you are not using Organic Groups or the newer Group module.

Hi Paul,

Thanks for all the info, but unfortunately your case is too specific.
We'll have to start a new custom project if we want to help you with this.

I'm afraid you'll have to scratch your own itch here

-- Best, Joris

My gut feeling for this: https://www.drupal.org/project/migrate_d2d

I dont see that the case of MrPaulDriver is too specific. It is one of the very common needs ..the need to plug in a functionality instead of using a completely isolated team system.

With all respect to the work done, the Drupal way" is to NOT create monolithic systems that cannot be applied to existing drupal sites.
The good thing is that is it available as an aegir compatible distribution, but the bad thing is that OL is designed not to be modified at all except from the end user configuration settings.

In order to make OL more friendly for Drupal developers and sitebuilders, I suggest that the custom OL modules that hold everyting together, are step by step replaced by existing contribs of the Drupal community. Thats by the way the only way that an open source project survives, by using and supporting the ecosystem. Otherwise growth and maintenance stops by itself.

7.x is not supported anymore. OpenLucius 2.0 (Drupal 9) is now actively maintained.
So I'm closing this 7.x ticket.