76

(12 replies, posted in PunBB 1.2 show off)

Hmm Interesting. caret position function only belongs to IE.... frustrating sad

77

(12 replies, posted in PunBB 1.2 show off)

opera cannot deal properly when input has properties with background-color, border-style. so help line cannot be same with mozilla and ie.

see http://www.webmasterworld.com/forum83/3021.htm.

and I'm searching docs for mozilla & opera in dealing with textarea field. if I succeed, me try to make it  a MOD.

Hello, My site is http://jacobswell.nared.net/punbb.

By this time the homepage is not open yet. just testing for punBB++ now.

I've ported phpBB's post method(? - soooorry, I'm not an American, Can you tell me what should I call?) and a little upgraded it.

- phpbb++ has a bug that when we click the smilies it does not appear in the textarea. iit is now fixed.
- you can use b, u, i, url, img, etc buttons easily like phpBB and more. whenever you click a button, it will be inserted to current cusor position. phpBB has it at the last position. so mine is more useful I think.
- it supports font type, color, size. Just go and test it.

This is the sample picture.

http://jacobswell.nared.net/upload/sample.jpg

Now I'm looking forward to phpBB v.1.2 for the language pack.

It's my fault that I posted. but I think it will help you when you make punbb support sqlite. thanks.

right. it's an punbb+ bug. smile

Another bug with sqlite.

when you log in, the bug is not shown, when you logout, you can find.
the bug is topic name is shown as 0 not a string name.

to avoid this, change like this.
in viewtopic.php(line 106) :

$result = $db->query('SELECT t.subject, t.closed, t.sticky, t.num_replies, f.id, 
f.forum_name, f.moderators, f.closed AS forum_closed, f.admmod_only, "0" 
FROM '.$db->prefix.'topics AS t INNER JOIN '.$db->prefix.'forums AS f ON 
t.forum_id=f.id WHERE t.id='.$id.' AND t.moved_to IS NULL') or error('Unable to 
fetch topic info', __FILE__, __LINE__, $db->error());

difference is between 0 and "0" smile

Hello.

Using SQLite, we will have a bug.
Currently we use addslashes() before we qoute in database queries.
Most of database systems use backslashes for escaping single quotes, but SQLite uses a more single quote. so escaping this('), it should be double single quotes('').

When we use SQLite, and type a single quote in the message field and press submit button, it will show you an error message. I've tested in Win2000 / Apache.

in setup.php, if you add some code for SQLite, it'll reduce the time for building database.

    $now = time();
    if ($db_type == 'sqlite') $db->query('BEGIN');

    // Insert guest and first admin user
...
       (inserting process)
...
    if ($db_type == 'sqlite') $db->query('COMMIT');

    // Check if default avatar directory is writable

84

(38 replies, posted in PunBB 1.2 discussion)

How about MoniWiki?
http://moniwiki.sourceforge.net/wiki.php

Current version support DBA database style only, but We can change it.

It supports index, diff,history...etc.

You can see it here : http://cheekyworks.com/wiki/wiki.php/FrontPage also.

go and test it.

if I misunderstand Paul, forgive me smile see I'm not an english-speaking person.
Actually what I understood is he suggested a solution having the same code, and I just said that would not look fit either.

I'm happy now for Rickard said he will give some thought of it.

as for Korean, 'can' is a sort of a verb and Korean structure has always put a verb at the last in the sentence except when we compose a poem. let's have a string like "you can post". In Korean grammar the meaning of 'can' should be after 'post' for we don't have a word for 'can' for 'can' is like a postfix of a verb. Auxiliary verbs are translated to postfixes of verbs in Korean language.

Great thanks, friends. smile

I found why. it's not the php version problem. it's sqlite problem.

let's see the problem. for instance, we can see this code in index.php

$result = $db->query('SELECT c.id AS cid, c.cat_name, f.id AS fid, f.forum_name, 
f.forum_desc, f.moderators, f.num_topics, f.num_posts, f.last_post, f.last_post_id, 
f.last_poster, f.closed, f.locked FROM '.$db->prefix.'categories AS c INNER 
JOIN '.$db->prefix.'forums AS f ON c.id=f.cat_id'.$extra_sql.' 
ORDER BY c.disp_position, c.id, f.disp_position') 
or error('Unable to fetch category/forum list', 
__FILE__, __LINE__, $db->error());

and if database is sqlite, it wll return array which keys are cid, c.cat_name....
if mysql, we can get array wich keys are cid, cat_name...

and we are accustomed to use mysql so the next code is this :

while ($cur_forum = $db->fetch_assoc($result))
{
    if ($cur_forum['cid'] != $cur_category)    // A new category since last iteration?
    {

?>
    <tr>
        <td class="puncon3" colspan="6"><?php echo pun_htmlspecialchars($cur_forum['cat_name']) ?></td>
    </tr>
<?php

Do you see the problem now? sqlite returns array which keys are 'cid', 'c.cat_name'... so there is no data whose key is 'cat_name'. so blank catalog name ....

actually it's not sqlite problem but php_sqlite problem that cannot handle that, I think. or we have to change like "c.cat_name as cat_name"... smile

I've just installed punbb++ on windows 2000 with the sqlite db option. installation went well. but when I go to the first page there is no forum name, just blank.

So I investigated whether the problem is in sqlite db file or the code, I found it with the code. there is nothing wrong with sqlite db file.

is there any who tried the same?

--; That cannot be applied to my mother lanuage, anyhow.

I really appreciate your concern, any way, Paul.

hmm, Ya. partly right. that can be a litteral translation but that can't be a good translation. wink

english can be ok even when we change structure a little, there are a few languages that cannot be ok.

I can make my own. but that's not the best way, I think. every version-up edition comes out, I'll have to make it.

As you know, we Korean have a lot of board systems because of internet system development, But I'd say all most of them are too heavy and no other language pack.

sometimes we use phpbb because it has Korean languae pack. phpbb uses language structure not word-for-word translation.

Hello, first of all I appreciate your work - punbb. I like it. and have tested in my computer.
I tried to make a Korean translation and found it may be differcult for the language structure. for instance, we can see the same code like this:

$perms = $lang_index['You'].' <b>'.$lang_index['can'].'</b> '.$lang_index['post replies'].'<br>'.... 

but Korean language structure is a little different from english and some other languages which have the same structure. As to Korean style 'can' or 'cannot' should be the last word. I think it will be not just a Korean problem, it'll be also other language problem.

So, the best method when we support other language more perfect, it should be like a sentence. so In my opinion the upper code should be

$perms = $lang_index['can_post_replies'].'<br>'...

Could you consider this problem and make a little change for this?:)