1
sockmonkey
Re: Testing: Multisite Module 1.17 RC for XOOPS 2.3
  • 2009/4/8 14:08

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Excellent! Version 1.18 cleared up my admin problems. I'm able to edit preferences, blocks, modules, etc. Thanks so much for the fix!

There's one final hurdle I can't seem to figure out. Although I'm setting a block as available in site 1, it is showing up in site 2 as well. Same thing with modules. I've set a module as available in site 1, but it shows up in both site 1 and site 2. Am I doing something wrong?

And just now I cleared my cache to see if that was the issue and now the theme set for site 2 is appearing for both site 1 and site 2. Any help you can offer is much appreciated.



2
sockmonkey
Re: Testing: Multisite Module 1.17 RC for XOOPS 2.3
  • 2009/4/3 0:17

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Quote:

wishcraft wrote:

Could you give me your server specs sockmonkey... It was developed on WAMP Server 2, which as far as I can tell is the specifications for writting XOOPS modules...

Sounds like a really strange error...

Certainly. My apologies, I should have started with this info.

XOOPS version: 2.3.3
Apache version: 2.2.11 (Unix)
PHP version: 5.2.8
MySQL version: 5.1.30
Operating system: Linux



3
sockmonkey
Re: Testing: Multisite Module 1.17 RC for XOOPS 2.3
  • 2009/4/2 15:42

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Update:

It seems that when I go to preferences, the 'domain' value being passed in the query string is the URL instead of the domain ID:

http://www.example.com/modules/multis ... ces&op=show&confcat_id=1&domain=http://example2.com

If I replace the domain value with the domain ID then I am able to edit the preferences.

New problem, though, I can edit preferences only for the first domain listed. If I try replacing the domain value in the query string with 2, it still brings up the preferences for domain 1.



4
sockmonkey
Re: Testing: Multisite Module 1.17 RC for XOOPS 2.3
  • 2009/4/2 13:30

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Quote:

wishcraft wrote:
This function is found in the domain.php class library. You will notice the edition in it with the if clause around the error this is all that needs to be done to fix this for fluid transparency. The error is cause by XOOPS referencing for a preference that is not populated in the database yet.
Quote:

if (is_object($confcat))
{
$domcat_handler =& xoops_getmodulehandler('domaincategory','multisite');
$criteria = new CriteriaCompo();
$criteria->add(new Criteria('domcat_name', $confcat->getVar('confcat_name')));
$domcat = $domcat_handler->getObjects($criteria);
}

This cleared up the problem I was having accessing pages other than the top page. Thanks for that. However, I'm still having no luck accessing the preferences for each domain. I still get the 'Forbidden' error.

Sorry I haven't had time to do more testing. Things have gotten rather busy at my workplace.



5
sockmonkey
Re: Testing: Multisite Module 1.17 RC for XOOPS 2.3
  • 2009/3/25 14:34

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


I love the direction you're taking this, wishcraft. The flexibility this affords is fantastic. I'm experiencing a couple problems, though.

First, when I try to set preferences for a domain I get the following error:
Quote:
You don't have permission to access /scms/modules/multisite/admin.php on this server.

All of the rest of the admin tabs work fine, so I don't know why I should have a problem with that one.

Second, when I click on any link on the top page of either of the two domains I have in the pool I'm getting this error:
Quote:
Fatal error: Call to a member function getVar() on a non-object in /home/sockmonk/public_html/swetnamcentral/scms/modules/multisite/class/domain.php on line 283

I don't know if these are bugs or if I just have something set wrong, but I thought I should Let you know.



6
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. :)



7
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?



8
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.



9
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?



10
sockmonkey
Re: Multixoops - With version 2.3.3 - RC
  • 2009/3/2 20:20

  • sockmonkey

  • Just popping in

  • Posts: 21

  • Since: 2008/6/4 1


Cool, that got my blocks displaying again. Thanks for that. :)

The bad news is that when I set a block to a specific domain it vanishes and doesn't even appear in the Blocks management module. There's no error, the block just isn't there. It's still in the database and if I set it back to '|all' then it reappears.

Also, now the themes don't seem to work for the different sites. They both settle on the default theme instead. Again, no errors coming up, but it isn't behaving as expected.




TopTop
(1) 2 »



Login

Who's Online

53 user(s) are online (29 user(s) are browsing Support Forums)


Members: 0


Guests: 53


more...

Donat-O-Meter

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

Latest GitHub Commits