Moved to Troubleshooting then wink

4,302

(1 replies, posted in PunBB 1.2 troubleshooting)

Do what the error says: chmod the cache folder so PHP can write to it (and remove any existing .php files in it)

Well, there are a couple possible issues there: before I list them though, I'd like you to show the output of the following SQL statement:

explain SELECT u.email, u.title, u.url, u.yahoo, u.location, u.use_avatar, u.aim, u.msn, u.signature, u.email_setting, u.num_posts, u.registered, u.admin_note, SUM(r.rep_plus) AS count_rep_plus, SUM(r.rep_minus) AS count_rep_minus, u.reputation_enable, p.id, p.poster AS username, p.poster_id, p.poster_ip, p.poster_email, p.message, p.hide_smilies, p.posted, p.edited, p.edited_by, g.g_id, g.g_user_title, o.user_id AS is_online FROM posts AS p INNER JOIN users AS u ON u.id=p.poster_id INNER JOIN groups AS g ON g.g_id=u.group_id LEFT JOIN online AS o ON (o.user_id=u.id AND o.user_id!=1 AND o.idle=0) LEFT JOIN reputation as r ON (r.user_id=u.id) WHERE p.topic_id=101 GROUP BY p.id ORDER BY p.id LIMIT 2000,25;

http://dev.mysql.com/doc/refman/5.0/en/ … y-log.html

In MySQL 5.0, queries that do not use indexes are logged in the slow query log if the --log-queries-not-using-indexes option is specified. See Section 5.2.2, ?Command Options?.

That's not nearly enough information to figure out the problem wink
For one thing, is PunBB the only thing running on the server? If not, then it could very well be something else on the server.
If PunBB is the only possible cause, then you'll need to track down which queries are doing full table scans. If you're using MySQL 5.0, you can log queries that don't use indexes: otherwise you'll have to find some other way (maybe just the normal slow query log with you running the queries through EXPLAIN to find the issue?)

Use the one that comes with the mod? Ask someone more familiar with the mod for help?

try adding $lang_common to the global bit

F.M: You're going to need to enter some SMTP details for PunBB to use in Admin Options.

Install isn't going to "detect" an old database: its purpose is to install a new copy. Edit the config.php you have so that the details match your old install (I think from your description you just need to change the db_prefix)

Moved to Modifications

4,311

(9 replies, posted in Feature requests)

Paul wrote:

Moved it back. It was a definite feature request and multiple classes doesn't help in this case though a sneaky use of descendant selectors might ie. putting classes on the tr and on the td which should give an infinite variety.

My bad then smile

4,312

(9 replies, posted in Feature requests)

http://css-discuss.incutio.com/?page=MultipleClasses
It is possible to do, moved to Modifications

Not a problem smile

Lets say you were adding it to the essentials section. You would find the extract elements call it uses, which is

$form = extract_elements(array('timezone', 'language'));

And add the new field to it

$form = extract_elements(array('timezone', 'language', 'email_setting'));

Make sure to remove it from where it currently is as well! smile

Did you add email_setting to the extract_elements call in the right case?

Yes: that doesn't mean the arcade.php you changed to is made for that setup

Yeah, like I said, that arcade.php isn't made for this version of this mod

FIND

$result = $db->query('SELECT COUNT(game_id) FROM '.$db->prefix.'arcade_games') or error('Unable to fetch total game count', __FILE__, __LINE__, $db->error());

REPLACE WITH

$result = $db->query('SELECT COUNT(*) FROM '.$db->prefix.'arcade_games') or error('Unable to fetch total game count', __FILE__, __LINE__, $db->error());

Again though, that script looks like it wasn't written for the current version: it might not work at all

4,318

(13 replies, posted in PunBB 1.2 troubleshooting)

Yours:

/****************************************************************/
/* 5. POST STATUS INDICATORS */
/****************************************************************/

/* 5.1 These are the post status indicators which appear at the left of some tables. 
.inew = new posts, .iredirect = redirect forums, .iclosed = closed topics and
.inormal = everything else. By default only .inew and .inormal are visible.*/

DIV.inew, DIV.inormal, DIV.iclosed, DIV.iredirect {
    FLOAT: left;
    MARGIN-TOP: 0.2em;
    MARGIN-LEFT: 0.2em;
    DISPLAY: block;
    BORDER-WIDTH: 0.6em 0.6em 0.6em 0.6em;
    BORDER-STYLE: solid
}

DIV.searchposts DIV.inew, DIV.searchposts DIV.inormal {MARGIN-LEFT: 0}

DIV.iredirect {BORDER-COLOR: #F1F1F1 #F1F1F1 #F1F1F1 #F1F1F1}
DIV.inormal, DIV.iclosed {BORDER-COLOR: #E6E6E6 #DEDEDE #DADADA #E2E2E2}
DIV.inew {BORDER-COLOR: #0080D7 #0065C0 #0058B3 #0072CA}

/* 5.2 Class .tclcon is a div inside the first column of tables with post indicators. The
margin creates space for the post status indicator */

TD DIV.tclcon {MARGIN-LEFT: 2.3em}

Default:

/****************************************************************/
/* 5. POST STATUS INDICATORS */
/****************************************************************/

/* These are the post status indicators which appear at the left of some tables. 
.inew = new posts, .iredirect = redirect forums, .iclosed = closed topics and
.isticky = sticky topics. The default is "icon". By default only .inew is different.*/

DIV.icon {BORDER-COLOR: #E6E6E6 #DEDEDE #DADADA #E2E2E2}
TR.iredirect DIV.icon {BORDER-COLOR: #F1F1F1 #F1F1F1 #F1F1F1 #F1F1F1}
DIV.inew {BORDER-COLOR: #0080D7 #0065C0 #0058B3 #0072CA}

Yes, there is a difference wink

4,319

(13 replies, posted in PunBB 1.2 troubleshooting)

But I ADDED that line of code (which wasn't present before)!

Yes it was: as I noted, I copy/pasted those two lines from your base.css. Only the second line is in an unmodded PunBB.

About the status notification: I'm still in troubles

Compare your Oxygen_cs.css to PunBB's normal Oxygen_cs.css (near the bottom of the file).

4,320

(13 replies, posted in PunBB 1.2 troubleshooting)

1. Compare your Oxygen_cs.css to PunBB's normal Oxygen_cs.css (near the bottom of the file).
2. The border doesn't appear for me either. I noticed these lines in your base.css

/* 3.1 This fixes bugs in Gecko browsers. */

DIV>DIV>DIV.inbox , DIV>DIV>DIV.block2col {BORDER-BOTTOM: 1px solid transparent}
DIV>DIV>DIV.postfootleft, DIV>DIV>DIV.postfootright {PADDING-TOP: 1px; MARGIN-TOP: -1px}

As compared to only the last line in PunBB's default base.css: I think that could be the issue

As for images, PunBB doesn't use images to show post status, it uses CSS

First question: the actual update statement is on line 855 of an unmodded profile.php
Second question: Take a look at the switch statement that starts at line 671 in an unmodded PunBB.

Yes, you're adding an index: it takes quite a while (and MySQL tends to devote itself to that task, which might cause other things to become slow):)

4,323

(1 replies, posted in PunBB 1.2 bug reports)

Thanks for the report (I've properly closed the tag now). smile
Please keep in mind, however, that we're not officially accepting bug reports for 1.3 yet.

4,324

(16 replies, posted in PunBB 1.2 troubleshooting)

The 350kb value you're quoting is the amount of space your forum takes up CURRENTLY, not the maximum amount of space you can have.

4,325

(16 replies, posted in PunBB 1.2 troubleshooting)

Ok last question, I promise!  Is there any risks for everybody having access to the error information during debug mode?

Well, there's a reason debug information is disabled by default. However, in this case I don't think it should pose much of an issue (since the only error you should be having is related to the one query).

What is a good database size for a forum that will have a large amount of members and posts?  For example, equivalent to the PunBB.org forums.

I'm not sure what you're asking: it depends on how many users/posts, the size of the posts, etc