not sure what to say about your session question. that's a good one, heh.


nice job tho. if you want to separate each node into more of a site tho, you might want to check out my multisites patch in the XOOPS sf patch tracker. manually patch your files, if you use it, because the patch file isn't quite accurate (was manually edited after the patch file was created)

anyways, using symlinks and my mod, you could have multisites off of a single core install, but each site would have it's own configuration data, and could install it's own modules locally, as well as share modules globally. there's no security checks in place, so i wouldn't give free reign to someone, thinking that all the other sites would be safe.

if you want to go this route, pm me and i'll help ya along, and i'll also give you a copy of my in-action setup (based on 2.0.9 with further changes, whereas the patch is based on 2.0.7.3)

Quote:

i have a multisite hack developed, works quite well for my needs, but i'm more of a hands-on, behind the scenes kinda guy, so constantly changing mainfile.php values and whatnot (which is what my hack requires when a module needs to be shared) works fine for me...

anyways, my modification is already available as-is (it's a patch at the XOOPS sourceforge patch tracker. i would manually apply the patch, as the generated patch might not be accurate), but i'll be releasing a version with admin interface controls, later on



as for XOOPS 2.1/2.2, multi-sites is definitely on the list of things we want to implement. skalpa, mith, myself, and others will be working on this feature, once xoops' 2.1 codebase is more stable

funky, appears to be just the wfdownload index page that is timing out... could be the proxy here at work, because i'm able to view other parts of wfdownloads (such as viewing a specific category, which generates 88 queries btw... wow...)


so the page timing out problem, dunno if it's wfdownloads or the crappy proxy here, but i'm still concerned about reducing the sheer number of queries

EDIT: ***i just verified that the wfdownloads index page is timing out... i logged into the same server that hosts the sites, and used a cmd-line webbrowser, it was unable to display the page as well...


i have no clue what's wrong with wfdownloads, maybe generating too many queries when having to display categories and get download information?

this is really weird, only module i've ever seen have this problem.

v2.05a, latest on wf-projects i believe.

okay, i know wfdownloads had problems when xoops.org installed the module. would you guys like to release the fixes that you implemented into wfdownloads to make it work properly?


i've installed this module on a closed site for testing, and was about to launch the site. but i just found that when the download module index page is viewed (with a whopping 8 downloads in the database), the webpage times out...

viewing the administration index of wfdownloads, reveals over 40 sql queries total, most of which are by wfdownloads... for 8 downloads...


this is ridiculous, so if anyone has any code that they've already fixed, i'd appreciate it, it would save me some work. and no, i'm not waiting for the next release of the module, because i've put off releasing this website for long enough.

Quote:


sure. if my modification were implemented into whatever module you're using, it's just a matter of how the search file were configured (and is just a matter of one line of code in that file, depending on how complex the file is)


just my multisite mod alone wouldn't suffice your needs, because while you'd be able to share modules across all sites, it would be the exact same content being shared. this new modification (the site registry) allows modules to be shared across all sites, but content can be separated per site.

the information is stored in the same database for all sites, which means that all of the information is accessible by all sites.


but anywho, after that wordy explanation, yes, what you want could be done

hehe, i'm getting psyched about my multi-site modifications, so i decided to brag a bit


awhile back, i developed a multisite mod for XOOPS 2.0.7.3 (and submitted it as a patch to the sourceforge patch tracker). once XOOPS 2.0.9 beta became available, i installed 2.0.9, along with my multisites mod, as well as a few other smaller modifications that i've created in the past month or two.

i'm now working on a small network of 6 sites, using my multisites modification, with all sites running off of the same installation of xoops


today, i created a new modification for xoops, by adding a 'site registry' to xoops, where i keep record of all of my multisite sites. each has a unique id, and the sitename, url, and site path is recorded as well. using this registry, and by making a number of changes to WF-Downloads, i can now add Categories and Downloads, and associate each category or download with a specific site, or allow all sites to view the category or download


this is a very useful mod for me, because i can now manage my downloads from any of my network sites, and control who sees what on the frontend. it requires less maintenance, since i no longer have to duplicate category or file entries, and don't have to load up the admin interface for each site, to manage the downloads


i'll possibly be implementing this mod into other Modules as well, such as NewBB, News, AMS, MyLinks, etc etc...

the prospects that this gives me has me all tingly now
lol...


anywho, the network of multisites will be unveiled hopefully before the end of this weekend.

/end brag

bahattee, no. and from the way your post is worded, it seems as if you already know about bbpixel

i have a project open at dev.xoops.org, for a modularized phpbb, but the project is inactive right now and has been for a bit (especially since newbb 2 has improved so much

agreed, mambo block management is definitely superior. devs are working on revamping the XOOPS block system, though, so hopefully it won't be too much longer before we have a more intuitive and comprehensive system in place

Quote:

i saw your implementation of the banner feature, and while i'm not quite aware of how i could make use of it, it's definitely nifty


didn't look at the audience feature yet, haven't have enough time to play