1

(21 replies, posted in PunBB 1.3 extensions)

YonasH wrote:

I want users to only be able to edit their own posts until there's been a reply or X minutes has passed. And thats it. Once either of those 2 things happen, the user should NEVER be allowed to edit that post again.

+1

RESOLVED.

Got on my server host chat support and they ran some voodoo and fixed it in like 5 minutes.  I was afraid to ask what they did!  HA!

OK, update...

Links WITHOUT "http://" work fine, those WITH "http://" fail...  ???

http://www.google.com

will fail with a 403 error.

www.google.com

will work.

OK, update...

NO links whatsoever, BBCode or not, can be included in a post without getting the 403 error.

Many of my users use photobucket to include images in their posts using img BBCode.  As of a couple of days ago, all was working well...then inexplicably new threads that included img BBCode from PhotoBucket gave 403 Permission Denied errors.  I may have updated a couple of extensions but none that should have an effect on this behavior.  Any ideas what might be going on?

Also, this only affects new posts...older posts that already include img coding are working just fine.

...I just checked my error_log files and they are pretty much filled up with "PHP Warning:  PHP Startup: Unable to load dynamic library" errors, so I'm not discounting something wrong on with the server settings.

Thanks in advance.

6

(61 replies, posted in PunBB 1.3 extensions)

Do you think it might be possible in a future version to list which subforum is being visited by which user?  It'd be kind of handy after posting to see if another user is visiting the forum (or post?), so that you might wait a moment or two in anticipation of a response.

I submitted some CSS bugs for previous versions and had hoped for better when upgrading to 1.3.4.  After some simple restyling of the default CSS for my site, mostly changing the color scheme, I did find the CSS is better overall, but still overly complex.  I especially found the CSS implementation for the admin area pretty inconsistent.  The "Manage Extensions" page was especially bad!!!...and I never did get it quite fixed without breaking other things, too.

I can backtrack and find some specific places, but I propose the follow changes for consideration:

A) Remove all of the CSS classes and ids specific to "admin" and just borrow from the regular pages.  Do people really want to style their admin area so differently from the rest of the site?  It seems like a waste of time and energy on all fronts.  But as it is now, the real waste is actually trying to FIX the bad implementation so the admin area is at least "functional" in appearance.  Let the few people who really want a different-looking admin use a different CSS in their admin template.

If nothing else, consider that EVERY PAGE that loads includes all of this admin-specific CSS styling that isn't even SEEN except in the admin area.  Very inefficient.

B) Simplify the color scheme!  How many shades of blue/gray are really necessary?  Half of them are barely perceptibly different.  Load Oxygen_cs.css using the tool below and explain to me why so many *nearly-exact* colors are necessary?

http://www.dagondesign.com/tools/css-co … ment-tool/

Thanks.

The administration area doesn't quite offer the search I am after to delete users by 0 posts and last login more than 1 year ago.  I believe, however, that the last login information for users is stored in the database, so this should be possible using a SQL query in phpMyAdmin or by an extension.

If someone has some help or input to offer, I would appreciate the time it would save me to figure it out.  smile

This extension concurrently logs a user into PunBB and ZenPhoto.  It is extremely bare-bones and has limited testing, but seems to be working on my site.  Open config.php to read more and to configure it.  It will NOT work until configured properly.

http://punbb.informer.com/wiki/_media/p … extensions

10

(0 replies, posted in PunBB 1.3 discussion)

Suggestion...

The find users section in the Users administration tab should include an option to search by last visit in addition to those already offered ("More posts than", etc.):

Last visit before:
Last visit after:


I would like to prune some of my users that have 0 posts and last logged in before, say, one year ago.  I can use a database query through phpMyAdmin, but this should really be available through the forum already I think.

I'm quite new to PunBB, so I just want to make sure I'm on the right track...

I am looking to synchronize my users of PunBB with ZenPhoto, a picture gallery program.  I first looked at this from the ZenPhoto side and was faced with heavy modifications of core files!  Yuck!  I think with PunBB's hook/extension system, I can accomplish 90% of what I'm after...

Specifically, I would like my extension to do the following:

* Upon PunBB register, add the user to the ZenPhoto database with certain default rights (can upload files, etc.).

* Upon PunBB user deletion, remove the user from the ZenPhoto database.

* Upon PunBB login...

-> check if user is in ZenPhoto database and add if not.

-> update ZenPhoto user password (in case the password was changed by the user since last log in).

-> set additional cookie for ZenPhoto authentication.

-> set additional session for ZenPhoto authentication.

* Upon PunBB log out...

-> unset ZenPhoto cookie.

-> unset ZenPhoto session.


Those are the basics.  One caveat is that ZenPhoto uses a different password hashing (md5?), but I *think* it should be possible to run the user-supplied password through two separate hashes to deal with it?

If I could use include_once() in the extension to pull from ZenPhoto, I could even use their native functions to deal with the password hashing, cookies, and such.


Any suggestions, code snippets, or links are welcome!

12

(1 replies, posted in PunBB 1.3 additions)

Users of PmWiki may find the following cookbook recipe I wrote up of some help:

http://www.pmwiki.org/wiki/Cookbook/AuthPunBB

13

(3 replies, posted in PunBB 1.3 bug reports)

I've been setting up my forum and have come across a few bugs.  Sorry if these have been posted before.  I'm new to punBB.

Oxygen.css ->

Around line 139

#brd-redirect, #brd-maint, #brd-util {
    margin: 50px auto 12px auto;
    width: 60%;
    }

Shouldn't it be "#brd-main" instead?

Around line 220

.brd .main-head .hn, .brd .main-foot .hn{
    font-size: 1.084em;
    padding-right: 10em;
    }

You probably want to add a space for consistency's sake: ".hn {".

Around line 225

.brd h2.main-subhead {
    border-style: solid;
    border-width: 1px;
    padding: 0 1.417em;
    font-size: 1.084em;
    padding: 0.462em 10em 0.426em 1.417em;
    }

Isn't the first "padding" unnecessary and repetitive?

.brd .extension .options, .brd .hotfix .options {
    border-top-style:dashed;
    border-top-width:1px;
}

You want an extra tab on that last bracket?

Oxygen_cs.css ->

Around line 363

.brd .main-frm .ct-group td{
    background: #FBFBFB;
    }

You probably want to add a space for consistency's sake: "td {".

Around line 371

.brd .main-content .main-item .icon {
    border-color: #EDF1F5 #DDE0E4 #C6CBD3 #BABFC6
    }

.brd .main-content .redirect .icon {
    border-color: #f4f4f4 #f4f4f4 #f4f4f4 #f4f4f4
    }

.brd .main-content .sticky .icon {
    border-color: #D7E5F3 #C3CFDC #9FB3C7 #90A2B4
    }

.brd .main-content .closed .icon {
    border-color: #ACACAC #979797 #898989 #7A7A7A
    }

.brd .main-content .sticky .closed {
    border-color: #D7E5F3 #C3CFDC #898989 #7A7A7A
    }

.brd .main-content .new .icon {
    border-color: #2B75AD #235E8C #1F537B #266799
    }

You probably want these to end with ";".

Just generally with the css files, it seems like these could be tightened up and tidied up a bit.  I get the feeling there is probably double the code necessary, but that's just an impression after playing for a short time.

Parsing routines ->

I can't give a specific file for this, but just explain...  As mentioned in this post, I took something of a roundabout way to convert my phpBB3 board to punBB 1.3.2.  I expected a few glitches.

One of the things that ended up happening is that I got several incorrectly formatted BBC quote tags, like this:

[quote:3943ds]

I think the extra code is inserted by phpBB3 to help match with closing brackets, but what ended up happening once I got to punBB 1.3.2 was that I got a bunch of extra closing "blockquote" tags without matching starting tags.  The formatting broke down completely with this!

I have noticed since that punBB checks that such code cannot go INTO the database through normal posting, but that only checks things on the front end.  In my opinion, the parsing of the code coming OUT OF the database needs a little more robustness.  If the database can store it, the parsing routines should handle it.

That's about all I can offer for now.  I'll post again if I run across anything.

14

(18 replies, posted in Feature requests)

Well, I went ahead and took this route:

phpbb 3 -> smf 1.1.17 -> punbb 1.2.21 -> punbb 1.3.2

Not exactly a pretty process, but the IMPORTANT things (categories, forums, posts, and users) made it through.  Looks like the PMs, avatars, polls, attachments, permissions, and passwords didn't survive; not a big deal to me.  Also, some of the BBC/smiley code in the posts got messed up.  I'll probably try to run some regular expressions through an SQL backup file, then restore to clean up a bit of that.

15

(18 replies, posted in Feature requests)

Thirded.

Just knowing whether there is active work on this or not would be helpful.  I'm no coding genius, but in a pinch I could probably hack up the phpbb2 -> punbb1.3 converter (if there is one?) to do what I need.

If a migration tool is on the horizon, does anyone know what it will do or not?  My phpbb3 forum has some polls, attachments, avatars, BBCode, and such which are of LESSER importance, but the correct post history is pretty important.  If I could get a correctly structured board (categories and forums), post history, and my users back, I'd be happy.

If it isn't already known here, Phpbb3 incorporates a nonstandard password encryption scheme.  So, in the end, any converter will unlikely (or uneasily!!!) be able to convert the passwords.  Users will have to request new passwords after the migration.  I'd be willing to pass on a little bit more information about this if it would help.

(Off-topic -- The forum search on this site seems to work for me intermittently.  Many times it gives me the "no hits" result even when I've tested it with keywords I know to exist on particular forums.  I can't seem to figure out a pattern of when it works and when it doesn't...  I'm using FireFox 3.1b2 on Ubuntu.)