21
sockmonkey
Re: Multixoops - With version 2.3.3 - RC
  • 2009/3/3 19:19

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


VERY cool! I've updated to the latest. Had some trouble at first (due to my own goof up), but now I have two fully functional sites sharing the same code!

Is there a plan to be able to set site preferences per domain?

22
wishcraft
Re: Multixoops - With version 2.3.3.2 - RC

Quote:

by sockmonkey on 2009/3/4 5:19:20
...
Is there a plan to be able to set site preferences per domain?


Yeah the concept of having site preferences did occur to me, just examining the prefix_config table there is a field called conf_modid, all though it is not designed for this assignment it can still be used to propogate the domain_id here to multipreferences.

There has been no plan to do this though as it gets a bit messy in cleaning up after a domain deletion and what if there is a module that shares the same domain_id. What are your thoughts?
Resized Image
www.ohloh.net/accounts/226400

Follow, Like & Read:-

twitter.com/SimonXaies
github.com/Chronolabs-Cooperative
facebook.com/SimonSXaies

23
noo-b
Re: Multixoops - With version 2.3.3 - RC
  • 2009/3/4 1:49

  • noo-b

  • Just can't stay away

  • Posts: 456

  • Since: 2007/10/23


this is fantastic so far.....

keep up the good work wishcraft.
I Love Xoops

24
Catzwolf
Re: Multixoops - With version 2.3.3.2 - RC
  • 2009/3/4 1:54

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


I would personally go with having a separate database table for this. This table wasn't designed for this implementation and there is nothing stopping you from doing joins anyway.

25
sockmonkey
Re: Multixoops - With version 2.3.3.2 - RC
  • 2009/3/4 3:37

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Quote:

wishcraft wrote:
Quote:

by sockmonkey on 2009/3/4 5:19:20
...
Is there a plan to be able to set site preferences per domain?


Yeah the concept of having site preferences did occur to me, just examining the prefix_config table there is a field called conf_modid, all though it is not designed for this assignment it can still be used to propogate the domain_id here to multipreferences.

There has been no plan to do this though as it gets a bit messy in cleaning up after a domain deletion and what if there is a module that shares the same domain_id. What are your thoughts?


Personal opinion? I think if a new table was created for the domains (prefix_domains) then you could use the domain ID in the prefix_config table. I.e., add a new column in prefix_config called conf_domain to specify the domain for each configuration setting. But that's just me.

26
wishcraft
Re: Multixoops - With version 2.3.3.2 - RC

Quote:

by catzwolf_ on 2009/3/4 11:54:44

I would personally go with having a separate database table for this. This table wasn't designed for this implementation and there is nothing stopping you from doing joins anyway.


Personally I agree with you catz, i think there should be a prefix_domains in there, I will reconstruct this section, means there will be a new ID called did.

I have taken the day off today as I have been working on this for a couple of days. that means in the prefix_configs there can be a new field called conf_did..

I will meditate on it for a day or two and go back to the ball and chain.
Resized Image
www.ohloh.net/accounts/226400

Follow, Like & Read:-

twitter.com/SimonXaies
github.com/Chronolabs-Cooperative
facebook.com/SimonSXaies

27
wishcraft
Re: Multixoops - With version 2.3.3.4 - RC

Download the latest multixoops http://bin.chronolabs.org.au/multi-xoops-2.3.3.4-RC.zip 2Mbs..

There are some changes in the database you can install or run this SQL Script make sure you put the prefix in for your database.

In this version the domain control has been seperated from the config table and placed in it own group, based on the config table for minor structural changes.

The collaboration part is still there with the sitemap.php and backend.php now using the newfeeds table so modules can collaborate and it isn't only the news that is found on the backend.

The policy ('Access policies') which is basically a firewall that can be set is implemented, this is a modified version of /kernel/policy.php

Here is that sql
#
# Table structure for table `domains`
#
CREATE TABLE `prefix_domain` (
  `
dom_idINT(10unsigned NOT NULL AUTO_INCREMENT,
  `
dom_pidINT(10unsigned NOT NULL DEFAULT '0',
  `
dom_modidsmallint(5unsigned NOT NULL DEFAULT '0',
  `
dom_catidsmallint(5unsigned NOT NULL DEFAULT '0',
  `
dom_namevarchar(25NOT NULL DEFAULT '',
  `
dom_titlevarchar(255NOT NULL DEFAULT '',
  `
dom_valuetext,
  `
dom_descvarchar(255NOT NULL DEFAULT '',
  `
dom_formtypevarchar(15NOT NULL DEFAULT '',
  `
dom_valuetypevarchar(10NOT NULL DEFAULT '',
  `
dom_ordersmallint(5unsigned NOT NULL DEFAULT '0',
  
PRIMARY KEY (`dom_id`),
  
KEY `dom_mod_cat_id` (`dom_modid`,`dom_catid`)
ENGINE=MyISAM;
# --------------------------------------------------------


#
# Table structure for table `domainscategory`
#
CREATE TABLE `prefix_domaincategory` (
  `
domcat_idsmallint(5unsigned NOT NULL AUTO_INCREMENT,
  `
domcat_namevarchar(255NOT NULL DEFAULT '',
  `
domcat_ordersmallint(5unsigned NOT NULL DEFAULT '0',
  
PRIMARY KEY (`domcat_id`)
ENGINE=MyISAM;

insert  into `prefix_domaincategoryvalues (1,'XOOPS_DOMAIN',1);
# --------------------------------------------------------


#
# Table structure for table `domainsoption`
#
CREATE TABLE `prefix_domainoption` (
  `
domop_idmediumint(8unsigned NOT NULL AUTO_INCREMENT,
  `
domop_namevarchar(255NOT NULL DEFAULT '',
  `
domop_valuevarchar(255NOT NULL DEFAULT '',
  `
dom_idsmallint(5unsigned NOT NULL DEFAULT '0',
  
PRIMARY KEY (`domop_id`),
  
KEY `dom_id` (`dom_id`)
ENGINE=MyISAM;
Resized Image
www.ohloh.net/accounts/226400

Follow, Like & Read:-

twitter.com/SimonXaies
github.com/Chronolabs-Cooperative
facebook.com/SimonSXaies

28
sockmonkey
Re: Multixoops - With version 2.3.3 - RC
  • 2009/3/9 14:13

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


No issues upgrading and it seems to be working like a champ. So far I only notice one thing that's odd. When I go to update the system module it tells me 'Could not update System.' Maybe that's just a problem on my end, but I thought I should report it.

I had an idea. It seems plausible enough to me, but I don't want to be presumptuous, so let me know what you think. In order to have greater control over what each domain can or cannot see/do it would be helpful to have a group for each domain. It would be nice if a new group could be automatically created each time a new domain is added. It would be even nicer if anyone signing up for one of the domains could be automatically added to that domain's group.

I don't know. Is this an idea worth exploring or is there a better way?

29
wishcraft
Re: Multixoops - With version 2.3.3 - RC

Quote:

by sockmonkey on 2009/3/10 1:13:15

No issues upgrading and it seems to be working like a champ.


Many thanks for all your testing sock monkey!! The multixoops in this version has all the features discussed including a firewall.

Make sure you set the firewall, I think it needs some form of auto-progation as people are unable to access the domain unless the domain is set!!

They will get a 403 forbidden.
Resized Image
www.ohloh.net/accounts/226400

Follow, Like & Read:-

twitter.com/SimonXaies
github.com/Chronolabs-Cooperative
facebook.com/SimonSXaies

30
sockmonkey
Re: Multixoops - With version 2.3.3 - RC
  • 2009/3/10 16:08

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


No problem at all. I have a vested interest in this project, so testing and providing feedback is the least I can do. And thanks again for all of the work you've put in on this. :)

Login

Username:
Password:

Lost Password? Register now!

Who's Online

43 user(s) are online (17 user(s) are browsing Support Forums)


Members: 0


Guests: 43


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jun 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits