This was bugging me as well.  In the main css file (Oxygen.css) changing

.brd .forum-noview .main-item {
    padding-right: 48em;
    }

from 48em to 28em seems to get it about right.  Maybe it was a typo?

The section below that might need to be changed as well.  Confirmation please smile

.brd .forum-noview .main-item ul {
    width: 47em;
    right: -48em;
    margin-left: -47em;
    }

Thanks for the info.  That was not at all the reason I expected, although it being due to quirky IE behavior is not much of a surprise roll

AracornRed wrote:

why is the users.username field 200 characters when new registrations are limited to 25?

This is technically a bump but I'm really curious as to the answer for the above.  I would like to use the username field in some other tables I am creating to integrate with PunBB, and am wondering if there's any reason not to set those fields to a length of say 50 characters or even 25 (the maximum username length that register.php allows).

I'm having problems when trying to integrate my site with PunBB following the instructions here.  My login form has a hidden field

    '<input type="hidden" name="redirect_url" value="'.$_SERVER['SCRIPT_NAME'].'" />'

and I've altered the logout section of login.php to

    redirect($_SERVER['HTTP_REFERER'], $lang_login['Logout redirect']);

so that logging in and out will return to the previous page, but when I do so from a page outside the forums directory the beginning part of the URL keeps getting doubled up like
http://localhost/mydir/forums/http://localhost/mydir/mypage.php

Should I just remove these two lines from the redirect function at line 864~ of functions.php?  Are they there for a reason?

    if (strpos($destination_url, $pun_config['o_base_url']) !== 0)
        $destination_url = $pun_config['o_base_url'].'/'.$destination_url;

That's true but still concerned about point 2 smile  Is there a noticeable performance difference in using two databases?  What route has everyone here who has "integrated" taken?

I've had PunBB running on my site for a while now on a MySQL database.  I'm currently designing a system separate from PunBB where members can submit reviews and the such to have saved in a database then published to the site - also via MySQL and PHP.  But I do plan to use PunBB's user table and login system, so my question now is, should I set up my site's tables on the same db as PunBB or use a separate one?

I see the advantages of using separate databases being
1) I can back up data from one db easily without necessarily having to transfer the data for the other
2) If I screw up my own system with buggy coding or insufficient security, there's less chance of my PunBB data getting screwed.

But I wonder if there would be significant performance advantages to sharing the same database.  Any advice?

Yes smile

Basically I want everything but alphanumeric characters filtered out when checking.  It's not so much the particulars of the regular expression I'm worried about, it's how to filter characters out of the database variable in the first place.  PunBB uses preg_replace in

WHERE UPPER(username)=UPPER(\''.$db->escape(preg_replace('/[^\w]/', '', $username)).'\')

to filter characters out of the new registration's username variable, but I don't know how to do the same to the database username field.

Thanks for the response.  Even with that change though, if there was an existing member "New Dude", somebody else could still register as "NewDude" or "New_Dude", etc.  Any solution for preventing that as well?

Hi there.  I'm new to PunBB and php, SQL as well so please bear with me here hmm

What'd I'd like is for PunBB to be a little stricter with new member registrations in making sure their user name isn't similar to an existing member's.  Along with being case-insensitive, I want to it to filter out all non-alphanumeric characters from both the users DB's username field and the new registration's username variable, then check them again each other.  So that for example "New Dude" or "New_Dude" wouldn't be able to register if there is already a "NewDude" member, and vice-versa.

I figure I should either change the code in register.php line 128

$result = $db->query('SELECT username FROM '.$db->prefix.'users WHERE UPPER(username)=UPPER(\''.$db->escape($username).'\') OR UPPER(username)=UPPER(\''.$db->escape(preg_replace('/[^\w]/', '', $username)).'\')') or error('Unable to fetch user info', __FILE__, __LINE__, $db->error());

or else add a username_filtered field to the users DB and check against that.  Any suggestions as to which approach would be better?  If it's the former, I would be uber grateful for an example of the code smile

BTW, this is probably a dumb question, but why is the users.username field 200 characters when new registrations are limited to 25?

Adam