Search options (Page 123 of 307)

Well, I think extern.php is going to stay the way it is and we'll provide other methods for integrating PunBB stuff with other stuff on a site

Then what Dr.Jeckyl said holds true

Keep in mind, of course, that the code is not yet done and we (the developers) won't support any use of it until the beta

There will not be an hdiff or patch from 1.2-1.3 as far as I know, simply because there are too many changes. You'll need to overwrite all your old files and then run the db_update.php script to update your database. All of your mods will be gone (although not any data they may have stored in the database).  As pogenwurst said, mods will need to be rewritten with the new system.

Well, this is a server issue: you'll need to talk to your host about it

Run the following query:

CREATE TABLE pbb_ranks (
                    id INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
                    rank VARCHAR(50) NOT NULL DEFAULT '',
                    min_posts MEDIUMINT(8) UNSIGNED NOT NULL DEFAULT 0,
                    PRIMARY KEY (id)
                    ) TYPE=MyISAM;";

Moved to Troubleshooting, this isn't a bug in PunBB
It sounds like you dropped the table at some point, you'll need to re-create it.

And using debug mode isn't dangerous per-se, all it does is provide more verbose error messages. The reason it's not enabled all the time is because showing the debug messages to random other people is bad from a security perspective.
Oh, and stop using caps

Mmm, that sounds to me like your cache files aren't being written to properly

Enable debug mode, paste the full message

Well, the version currently under development (1.3) allows you to very easily change the path to the cache directory. However, in 1.2, you'll need to manually edit include/cache.php and any files which load cache files (eg: include/common.php, extern.php, etc) to point to the new path. Or you could put PunBB entirely in the cgi-bin and set up a VirtualHost or something like that to point to the PunBB directory

You're not looking at the right query
Your error message "Unable to insert into user statistics"
That query's error message "Could not insert into statistics"

1.3: closed (I'll double check this tonight)