HKV3 Previews

[GoldenMerc]

Can you have more than one title?
IE being a news reporter and being a DJ?

[Dentafrice]

No, but there can be custom usergroups setup for combinations like that, with specific permissions for each usergroup.

[BoyBetterKnow]

TIS BLUE.



I have a perm_set table. In that table, is: id, features, pages, title.

So it would be setup:

id - 1
features: login_while_offline;manage_users;some_other_featur es;
pages:
title: Administrator

Pages is the field for CMS pages.. so if you had a DJ you could have..

id - 2
features: cat_radio;dj_says;requests;
pages: radio_rules;dj_guide;other_stuff;
title: DJ

id - 3
features: edit_server_info;manage_other_stuff;login_while_of fline;
pages: radio_rules;dj_guide;head_dj_guide;
title: Senior DJ

Nice, then seperate using ; as the delimeter. Nice way

[Dentafrice]

Nice, then seperate using ; as the delimeter. Nice way

Even if there is/isn't a last ; (login_while_offline;blah vs login_while_offline;blah;) it still cleans up the array through the $core->clean_array() method which removes empty array elements.

All it does is get your current features list, and there is a has_feature() function, which just uses an in_array() to determine if the current feature being requested is in the features array that was separated earlier.

Easier and better then other versions of HK which needed the user to logout then login to see updates to his/her level as it was stored in a session ($_SESSION["session_level"]) instead of directly pulled from the database.

[BoyBetterKnow]

Even if there is/isn't a last ; (login_while_offline;blah vs login_while_offline;blah;) it still cleans up the array through the $core->clean_array() method which removes empty array elements.

All it does is get your current features list, and there is a has_feature() function, which just uses an in_array() to determine if the current feature being requested is in the features array that was separated earlier.

Easier and better then other versions of HK which needed the user to logout then login to see updates to his/her level as it was stored in a session ($_SESSION["session_level"]) instead of directly pulled from the database.

Haha we all made the mistake of storing session level and session users at some points It seemed practical haha.

It sounds like a good little project. I'll be honest and say "I think your next one should be to bring back / start a new upload site". It was fantastic.

Good work though.

[Dentafrice]

Haha we all made the mistake of storing session level and session users at some points It seemed practical haha.

It sounds like a good little project. I'll be honest and say "I think your next one should be to bring back / start a new upload site". It was fantastic.

Good work though.

Haha, I think I'm done with the upload business ;P.

I really hardly have enough time for HKV3.

[Blob]

Are you optimizing your code?

Like using $variable . ' hello'; instead of "$variable hello" etc? (To make it faster)

[GoldenMerc]

Caleb is never on msn anymore

[Dentafrice]

Are you optimizing your code?

Like using $variable . ' hello'; instead of "$variable hello" etc? (To make it faster)

Lawl, you speak to me like I just picked up a PHP for dummies book. "To make it faster".

No.. I'm not concatenating my variables to my strings. I am using the curly-brace-variable-inside-double-quoted-string method.

$string = "{$says->username} - {$says->message} :: at the time of death."; 

Caleb is never on msn anymore

Getting on in a sec.

[Blob]

Lawl, you speak to me like I just picked up a PHP for dummies book. "To make it faster".

No.. I'm not concatenating my variables to my strings. I am using the curly-brace-variable-inside-double-quoted-string method.

$string = "{$says->username} - {$says->message} :: at the time of death."; 

Getting on in a sec.

Well how else would you phrase it?

Not making it slower

Making it faster
?