Search options (Page 9 of 19)

Ah. That was the other interpretation that I hoped wasn't it

An easier way to solve this would be:
Forget about the auto-increment.
Get the highest ID before insertion, add 1 and give this id to the new entry for the ID field and the parent field if it's the first in thread. The replies will get that id as parent as well. So all comments in one threads have the same parent ID. Clear?

Now you can use one query, sort by parent and id.
For each row, keep the last id and parent for comparison.
Then create a variable for the padding space.
Now, if in one row the new parent is the ID of the last row then you know you have to add another padding divs to your output.
As long as the parents stay identical keep the number of padding divs.
If the next parent is different without being the id of the previous row then substract one padding div.

Now, ain't that easy?

OK OK, I'll try to write it down but don't blame me if it doesn't work 100%, it's just a sample for what I mean

//Get the highest id
$highest= $db->query("SELECT max(id) as MAXID FROM comments");
$mm = $db->fetch_assoc($highest);
$max = ($mm['MAXID'] + 1);
// Insert one row with a thread starter
$newrow = $db->query("insert into comments (id, parent, text) values (" . $max .", " . $max . ", '" . $text . "'");

//Now get the threads
$all = $db->query("select * from comments order by parent, id");
$padwidth = 8;
while ($sb = $db->fetch_assoc($all)){
  if($all['parent'] == $oldid)  {
    $padwidth += 8;
    $oldparent = $all['parent'];
    }
  elseif($all['parent'] != $oldparent)  {
    $padwidth -= 8;
    }
  echo '<div style="padding-left:' . $padwidth . 'px;">' . $text;
  $oldid = $all['id'];

  
}

Something like this. No warranty. Just a rough sketch...

I am not sure what exactly you mean.

Do you mean you have a table with, say, articles and another table with comments on articles?
In this case you will have a field article_id in your article table and one article_id in your comments table.
So all you do is make a query like this

select * from articles, comments where articles.article_id=comments.article_id

Well, I don't say that anything is non-trivial or bad just because it's used by Americans. That would be slightly stupid.
However, when it comes to integration and world wide standards you always have two options: Either you leave it or one party has to adjust to the other.
If you go for the latter option then who should adjust? The ones with the easier system? (And please don't tell me that by logic and rational argumentation a decimal system is not easier to understand, use, compute...) Or the ones who want to keep their system because... well, because what? They are used to it? Even though they only make up for 5% of the world population?

OK, then go and consider the cost for the other 95% of this planet. How do you call that in football if somebody hits their own goal by accident?

But as I mentioned, I think exactly this kind of argumentation without real arguments lead to the world being a difficult place and things will just stay as they are...

Now, that is one useful mod!

Thanks, I will definitely give it  a try.

Heheh... that'll teach them...

That sounds tricky.
I found this in login.php

    if (!$authorized)
        message($lang_login['Wrong user/pass'].' <a href="login.php?action=forget">'.$lang_login['Forgotten pass'].'</a>');

The function message calls header.php which includes main.tpl, and I think you shouldn't change that.
So you will have to make an extra function like message() but with your own template instead of main.tpl or you have to tweak the message function itself.

I also don't get this completely.
There is nothing but the lang files and the only untranslatable stuff there are the array keys.
Why do you have to hide them?
Well, a good guess anyway would be to apply a regex on each line that goes like

/([^=]+)/

which would collect all the array keys.

Or, make a small script that read the lang files and prints only the values.

Something like

$sql = ereg_replace($this->prefix ."users", "YOURTABLEusers", $sql);

Should work .
It must be placed in line 76 of include/dblayers/mysql.php

Replace YOURTABLE with the prefix of the usertable that you want to use.

Well,
although it is really unpolite to laugh at somebody who made an effort to help out others  I agree that this doesn't look user friendly at all.

But then again, if people want it like this, why not?
People want Windows, you know...

Yes, you can, and it is especially useful when you have fields with flags (like status=1, status=2 etc) where the numbers don't reflect the order that you want them to appear.

As far as PunBB is concerned there will be no problem.