Moved to Modifications

Adam Atlas: That usually happens when the post count is "off" for some reason (most likely reason: you deleted a user without deleting his/her posts or setting his/her posts to another user).

728

(12 replies, posted in PunBB 1.3 troubleshooting)

I was originally torn between generating a full-blown custom 404 page and doing what PunBB does now. We did it this way for the sake of simplicity with the idea that anyone who wants a custom 404 page can make one via the extension system.

And that link you sent me to just shows the text "Page not found"

729

(26 replies, posted in PunBB 1.3 troubleshooting)

That's exactly what the plan is (to keep it an extension)

730

(1 replies, posted in PunBB 1.2 troubleshooting)

http://punbb.org/forums/viewtopic.php?id=18590

731

(8 replies, posted in PunBB 1.2 troubleshooting)

Write a post on PunRes in the release topic for the version of the modification you actually used. You're more likely to get support that way.

732

(8 replies, posted in PunBB 1.2 troubleshooting)

The topic you just linked to wrote:

This extension allow quickly edit post

Only for punbb 1.3.

You are not using 1.3. Find a modification, not an extension. Do not use 1.3 on production sites. Blah! wink

733

(12 replies, posted in PunBB 1.3 troubleshooting)

Kyle: Good point

734

(8 replies, posted in PunBB 1.2 troubleshooting)

1.2.17 is the official stable release
1.3 is in beta

735

(12 replies, posted in PunBB 1.3 troubleshooting)

I put a hook in rewrite.php specifically because I anticipated people would want more control over their 404s. smile

This may or may not work, but it's the only way I could think of to pull out UTF-8 data from iso-8859-1 without massive changes to the code.
extern.php
FIND

// Load DB abstraction layer and try to connect
require PUN_ROOT.'include/dblayer/common_db.php';

AFTER, ADD

$db->query('SET NAMES UTF8');

737

(3 replies, posted in Programming)

Well, I don't see anything wrong with the upload code offhand, but you are exposing yourself to SQL injects.

738

(5 replies, posted in PunBB 1.2 troubleshooting)

What errors are you getting?
And yes, the forums, topics, posts, etc are in the database.

Moved to Modifications

Fixed

741

(3 replies, posted in PunBB 1.2 troubleshooting)

Until you paste the full error, we can't diagnose the problem
and the Textpattern forums are likely not suffering from the same issue.

DEBUG mode makes the error give more information than just what you have posted.

743

(3 replies, posted in PunBB 1.2 troubleshooting)

Enable debug mode (see the sticky at the top of the forum), paste the full error

Oh, I see now. Yes, this isn't the same thing as splicing your code in, just like you can't do that using includes. Each hook has to be valid PHP in and of itself.
And there shouldn't be any reason to need to do it that way anyway.

That doesn't mean completely disabling the fopen function is something a competent host would do wink

And yes, we reimplemented var_export in 1.2 because we needed that functionality and couldn't get it another way. fopen/fwrite provides equivalent functionality to the function you're talking about, however, and shouldn't be disabled in any case.

To be honest, this is like saying we should be using the ereg functions because some host could disable the preg functions. Yes, they could. If they do, you should find a host that knows what they're doing.

Moved to PunBB Discussion, since this isn't a bug
That's the way the system works. Topics are marked as unread if they have been posted in since your last visit time. In 1.3, we have a system that actually records whether you have read those threads or not and changes the indicators accordingly.

I'm confused. Yes, it's up to you to write valid PHP code. Is there something here I'm missing?

Because file_put_contents is a PHP5 only function.
And I have NEVER heard of a host removing fopen like that. I would get a new host if I were you, it doesn't seem like they know what they're doing.

749

(26 replies, posted in PunBB 1.3 troubleshooting)

Yes, I read it a while ago (and now). wink
These types of topics, however, are much better off when split up logically. Having one topic for requests that affect varying parts of the software (especially when you say in advance that some of the requests make more sense as extensions) can cause people to not respond because they don't feel like responding to a part of it. Also, they tend to reflect the wishes/preferences of the poster rather than things that necessarily need changing. It's easy for good ideas to be lost in them. wink

Now then, the original ideas:
1. Yeah, I think we need to take a look at that
2-6: extension

Second post:
1. Remove all is an extension, I don't see why seeing the subscriptions from the profile is necessary (so extension as well)
2. Maybe for admins/mods
3. extension
4. extension
5. As people said, I think MSN is the more well known term. I happen not to use it though, so I'm not in much of a position to judge.
6. extension
7. extension

1. size would be an extension, list is (I think) still planned for the new parser.
2. probably an extension, although personally I like split/merge functionality
3. extension

http://punbb.org/forums/viewtopic.php?id=11592
So I guess this is where Paul steps in and gives us his expertise on the matter tongue