lastuser

["Jason" <judgej (at) xaraya.com>]

Out of curiosity, is there a reason why this information cannot be taken 
directly from the roles tables, instead of via some module variable? If I 
wanted a block to display, say, the latest ten users to register, then how 
would I go about doing that?

-- JJ


"jojodee" <jojodee (at) xaraya.com> wrote in message 
news:ejr3dm$rdj$1 (at) newton.xaraya.com...
> Jalal
>
> This modvar was set for users revalidating emal and for users validating 
> accounts as the two processes were using the same functions in roles.
>
> I separated this out a few months ago in roles and the last user is only 
> set on registration, not on revalidation of email.
>
> The functions are still similar here, but the process of validating 
> accounts and revalidating emails have been mostly separated pending moving 
> to separate apis.  It should be in the current monotone code and also 
> available in the nightly build if you want to grab it..
>
> Jo
>
>
> "jalal" <the.jalal (at) gmail.com> wrote in message 
> news:mailman.159.1163972269.23480.xaraya_devel (at) xaraya.com...
>> On 19/11/06, John Cox <john.cox (at) wyome.com> wrote:
>>>
>>> On 11/19/06, jalal <the.jalal (at) gmail.com> wrote:
>>> > The reason is that when a user validates their joining (via their
>>> > validation
>>> > email) then the last user number is stored. But they also go through 
>>> > the
>>> > same process when they change their email address or password.
>>> >
>>> > This kind of makes it difficult to fix... any ideas on what to do?
>>>
>>> Two things can be done.
>>>
>>> Easy: Remove the call from the template.  Still broken, but at least it
>>> doesn't show it.
>>
>>
>> Yes, that's what I've done for now.
>>
>> Hard: That is just a modvar which is updated, what you could do is 
>> evaluate
>>> the  timestamp of when they signed up before setting the modvar.  If it 
>>> is
>>> within a certain time, set it, if not, then don't.  I believe the date 
>>> is
>>> in
>>> the roles table (been a very long time since I looked).
>>
>>
>> There are a few ways of approaching it.... but all of them require 
>> hacking
>> the core code, rather than an override template.
>>
>> I think there is basic question of whether a module variable called
>> 'lastuser' should be storing the most recently validated user or the most
>> recently joined user.
>> I think it may be simplest to create a file:
>> /modules/roles/xaruserapi/getlastuser.php to pull the data from the
>> database.
>> Or to extend the /modules/roles/xaruserapi/getusers.php to accept 
>> parameters
>> to just get the most recent.
>>
>> Comments?
>> jal
>
> 


_______________________________________________
Xaraya_devel mailing list
Xaraya_devel (at) xaraya.com
http://xaraya.com/mailman/listinfo/xaraya_devel