Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By bazzly on
I am looking at doing a multiple sites. I believe it is a multiple as the second will run its own modules. I have one domain that the main site will sit on. The second site will be in the "sites" directory of the main drupal site.
So I should end up with http//:mainsite.com/othersite.
Now for the advice....Would that be the best way to go?
My main site will be a blog/content site, and the second site would be a drigg site.
I'm thinking that is why I should go with two sites. (two different module sets)
And my other question....is it possible to have single user log on across the two site? I thought by setting up the database during the second install would have made it work (different prefix so it does not over write) but goes to show what I know. lol
I have read many post about sharing and I have tested a second site install, but could not get single logon to work.
Thanks
Comments
Can someone help me with
Can someone help me with this http://drupal.org/project/singlesignon
So...from the read me says
Installation and activation are simple:
+ Put this file in your modules directory. (Did this on both sites)
+ If you're not also using the "domain" module (I'm not using this)
+ If you haven't done so already, create site sub-directories in the
"sites" directory for each of your domains. Put "settings.php"
files in each of those directories. (ok done)
Edit each of the settings.php files to values appropriate for the given domain. (where would I do that...Is that this part: $cookie_domain = 'example.com'; )
+ Make sure the "$db_prefix" variable is set correctly in each ("$db_prefix" variable being what? How would I know what to set it as?)
settings.php file (see details below). (For the Most part I copied what was written in these directions but changed one thing)
+ Create the site specific and shared database tables defined in the
"$db_prefix" variable (see details below). (So I add that to the settings.php, do I need to add something to the database to?)
+ On each site, starting with the master site: (ok got this part down)
+ Log in as administrator.
+ Enable the "singlesignon" module
(via the checkbox in the administer | modules interface).
+ Enter the URL of the master site
(via administer | settings | singlesignon).
+ Delete cookies from all of your Drupal sites.
This module relies on several tables being shared between the master and
slave sites. Here is an example of the "$db_prefix" variable you need to
establish in all of your "settings.php" files in the "sites" directory.
Each site should have a unique name in place of "somesitename_". While
you can rename "shared_" to something else, the prefixes must be the
same for all sites.
$db_prefix = array(
'default' => 'somesitename_', (so is this the site name or the database name? I placed the database name)
'authmap' => 'shared_', (I left the rest as shared)
'profile_fields' => 'shared_',
'profile_values' => 'shared_',
'role' => 'shared_',
'sequences' => 'shared_',
'sessions' => 'shared_',
'users' => 'shared_',
'users_roles' => 'shared_',
'users_uid_seq' => 'shared_', // for pgsql
);
Sorry if I'm asking a lot, but I'm learning this stuff and every time I google info I get things that contradict each other or is old info. Thanks
_
I'm not sure you actually need 2 sites for this. There's no reason you couldn't simply turn on the blog module on a drigg site.
One other thing-- i'd think carefully about using the drigg module. The maintainer has moved on to other things and it only has a dev version for d6. It would be a waste to invest too much time in a dead end module.
just my $0.02 worth... ymmv.
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz
I was unaware it was a dead
I was unaware it was a dead end. Good to know.
Guess I should stick with Pligg.
I'm wondering how hard it would be to get single sign-on between the drupal site, and the pligg site. I could give the pligg site a different prefix and share the database, but dont think that would help for logon.
Any input...?
Thanks
_
It may not be-- but it sure looks that way at the moment.
As for pligg, sorry I've never used it. But perhaps you'll find some useful info with a search: http://drupal.org/search/node/pligg
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz
So If I were going to stick
So If I were going to stick with drigg...How would I go about using one logon for both sites?
I would like the social site be its own life, thats why I dont want to turn the blog on in drigg.
Thanks
_
I've never done it, but perhaps this handbook page would be helpful: http://drupal.org/node/147828 (its for d5, but from what i see very little, if anything, has changed.
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz
Sorry to keep doing
Sorry to keep doing this....A lot of the information in there is the same as the setup for the module.
Per the modual directions:
"Create the site specific and shared database tables defined in the "$db_prefix" variable"
I think I need to add new tables to the database, because some of the tables needed such as 'default', 'sequences' and 'users_uid_seq' are not in the database.
So I went into phpmyadmin and went to create the table, but it also asks for "Number of fields:"
I think if I add those to the database it should get it to work.
How do I go about adding those three things? Do ya think that is what I need to do?
Sorry again, and thanks
_
It's not that I don't want to help, but as i've never done this i'm working a bit in the dark.
I don't really understand what your question is-- section 2 of the page I link above describes in step by step detail exactly how to set up the db connections, and no, it doesn't look like you should have to create tables manually.
Just follow the step by step in that page and you should be fine.
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz
No I understand that, and
No I understand that, and thank you very much for the time you have given me.
Think I got it....to be continued!
Seems like the directions
Seems like the directions dont work. It looks like this has a better chance of working. http://groups.drupal.org/node/15601
I used the directions, and its a total fail. When I used the link above I was closer, but still failing.
There must be someone out there doing this....I would think. I also read about something called CAS. Could this do the trick? Would openid work?
The thing I'm trying to get working, is...
On the main site users write in their blog. If the user wants to share it, all her/she would have to do is click a button and it would automatically submit it to the social site.
Is there anything available that my do that already?