2
Thanks much for the PHP code for this, but how would I implement that within the block I mentioned?
3
I'd like to modify the system_block_newusers.html template to report how many new users have registered in the past 24 hours but am not seeing how to incorporate some type of query to provide the count. Does anyone have an example of this I could pick apart?
4
I have a few home-made modules that I would like to incorporate into my XOOPS site. However, some of the modules are only applicable to certain parts of my site. For example, if my users are using theme "X", I would like them to be able to see a block called "X", but otherwise, do not display that block. Also, on theme "A", I want to have blocks "A","B","C" displayed. Am I better off just writing my own block code and then including these blocks into the applicable theme.html files? OR Which navigation module would serve this purpose?
6
Ah, perhaps I wasn't clear enough..
Yes, I have existing sites, each with their own independent databases and XOOPS installs (see my siggy). My end result would be a shared database for (at least) the users, forums and extended profiles to eliminate the users having to login to each of them with varying usernames and/or passwords.
I believe I'm going to have to try and attempt this in multiple steps:
a) merge the user tables with an integrated "dupe" user check so that the user's statistics can be summed rather than overwritten - perhaps a complex join statement on the users in the case that their username or email addy shows up in multiple databases
b) merge the extended profiles tables using a common format to include any custom fields that may not extend across the different databases
c) combine all the newbb tables into a single database, adjusting userid information so that credit is not lost for posts and the newbb author fields don't lose reference
Ya know, I think I just talked myself out of it.
Yes, I have existing sites, each with their own independent databases and XOOPS installs (see my siggy). My end result would be a shared database for (at least) the users, forums and extended profiles to eliminate the users having to login to each of them with varying usernames and/or passwords.
I believe I'm going to have to try and attempt this in multiple steps:
a) merge the user tables with an integrated "dupe" user check so that the user's statistics can be summed rather than overwritten - perhaps a complex join statement on the users in the case that their username or email addy shows up in multiple databases
b) merge the extended profiles tables using a common format to include any custom fields that may not extend across the different databases
c) combine all the newbb tables into a single database, adjusting userid information so that credit is not lost for posts and the newbb author fields don't lose reference
Ya know, I think I just talked myself out of it.
7
Quote:
Are you implying that the module merges the databases for me?
deepy wrote:
You seem to miss the understanding of the Multisites Module. This tiny little module has gigantic potential, ridiculous enough. Once you start using it, you shall realise how clever people are hanging around in the CORE development and will beginn to appreciate.
Are you implying that the module merges the databases for me?
8
Will msHack 2.2.3F function with 2.2.4 core system?
Has anyone developed a tool to merge existing databases into a single database for users, profiles, groups, ranks, etc..?
Has anyone developed a tool to merge existing databases into a single database for users, profiles, groups, ranks, etc..?
9
This should be incorporated into the next XOOPS version, please.
To fix the minimum password length in the lost password function, add line:
after
Thanks again.
To fix the minimum password length in the lost password function, add line:
$length = $xoopsModuleConfig['minpass']; after
function xoops_makepass($length = 5) {
$makepass = ''; Thanks again.
10
I will test the multi-site hack but it looks to be what I have been searching for!
2) do we have a coder in the house that could show me what lines to add to the template?
3) Adding such info to the topic is a horrid idea - the topic would be huge.
4) I would assume that users would change their password when they gain access, too. But, will they be able to gain access at all if the minimum password length is not adhered to by the lost password code or will it continue to deny them access because of the length!?!? I'm just looking for some uniformity, here. If users are forced to use a specific length, so should the package.
Thanks for your responses.
2) do we have a coder in the house that could show me what lines to add to the template?
3) Adding such info to the topic is a horrid idea - the topic would be huge.
4) I would assume that users would change their password when they gain access, too. But, will they be able to gain access at all if the minimum password length is not adhered to by the lost password code or will it continue to deny them access because of the length!?!? I'm just looking for some uniformity, here. If users are forced to use a specific length, so should the package.
Thanks for your responses.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Dec 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|