126

(1 replies, posted in PunBB 1.3 troubleshooting)

I see just

body {
    background: #000;
    color: #fff;
    }

in http://wediction.com/D12WorldNight/styl … gen_cs.css.

I don't think you really need JS. Why not to write just this:

.row  {
    background: #FFFFFF;
    color: #000000;
}

.row:hover {
    background: #CCCCCC;
    color: #000000;
    cursor: hand;
}

...

Fixed.

I'm afraid I can't exactly say what file you have to check. But the issue can be related to the wrong encoding of language files. They must be saved in the UTF-8 encoding without BOM (byte order mark).

I've just registered and logged in. Everything works fine for me. Maybe the page is empty only for admins?

131

(2 replies, posted in PunBB 1.3 bug reports)

Fixed.

Maybe it's because of extensions. Try to disable (not uninstall!) them step by step and see if the bug disappears.

Apparently validEmail() checks if the e-mail is correct.

The forum_mail() function is an improved version of the usual mail() function in PHP. mail() is used in your code:

if(mail($to, $subject, $message, "From: $from  \r\nContent-type: text/html\r\n"))

I think it's OK. So you don't need forum_mail().

As I see, the Ajax request goes to http://keydogbb.info/extensions/ajaxpopform/contact.php, and this url is unavailable.

You have to make a preg_replace call on the page text to replace the <div> content. There are two ways:
1. Put ob_start(); in "in_users_online_pre_online_info_output" and ob_get_clean(); in "in_users_online_end", replace the content and print it again.
2. Replace the content in the $tpl_main string (somewhere in footer.php, I guess).

You can use the forum_mail function.

136

(5 replies, posted in Discussions)

You're welcome smile

137

(6 replies, posted in PunBB 1.3 additions)

Interesting idea. I think pun_quote and pun_pm can be improved to work together.

138

(5 replies, posted in Discussions)

It's in Oxygen_cs.css (line 5).

I'm looking through the source of the page. Seems like you put <!-- forum_head --> in the wrong place. Now it's somewhere in the page text but it must be between <head> and </head> tags.

Actually you do not have to change the body background color. You can put <!-- forum_head --> before other styles (tags <link...>) and the body background color defined in Oxygen style will be redefined in your styles. The place for <!-- forum_head --> just after <head> tag would be nice.

139

(5 replies, posted in Discussions)

Take a look at the main.tpl file. There is a placeholder

<!-- forum_head -->

between <head> and </head>. Seems like it's missing.

Actually this video tutorial is outdated. It's for PunBB 1.2, not PunBB 1.3.

140

(2 replies, posted in PunBB 1.3 extensions)

1. If we use 'global' every hook code will contain 'global $ext_info_stack;'. I think several global definitions in a scope isn't so pretty.

2. One of the developers has already used $GLOBALS['base_url'] in that piece of code.

3. cache_hooks.php contains an auxiliary code generated by the forum script. It's not a problem if this code violates PunBB code style convention.

4. According tests $GLOBALS is a little bit faster.

That's why I've chosen $GLOBALS.

141

(2 replies, posted in PunBB 1.3 extensions)

A bug in the extension system was found. I suggested a fix. I would like to ask extension developers for help in testing. Please, download the last revision of PunBB from SVN and test if your extensions work correctly. Thank you.

142

(4 replies, posted in PunBB 1.3 bug reports)

I've tried to fix it. Please, download the last revision of PunBB from SVN and test it out. Works fine for me.

143

(4 replies, posted in PunBB 1.3 bug reports)

Wow! It's really a bug. Seems it's in the extension system, not in pun_bbcode. The $ext_info_stack variable doesn't contain the info about pun_bbcode since the hook is in a function and $ext_info_stack is a local variable. I think that we can write $GLOBALS['ext_info_stack'] instead of $ext_info_stack in cache_hooks.php. But this suggestion is to be tested.

Fixed.

How exactly do you include extern.php? The symbol '…' in UFT-8 encoding is used in the extern.php. And the encoding of your site is iso-8859-1. That's why this symbol is displayed wrong.

146

(4 replies, posted in PunBB 1.3 bug reports)

The extension system should process extensible extensions correctly. If you open the file "cache_hooks.php" you'll see that some information about an extension is placed into a stack before a hook code of this extension. After the hook the information about a "parent" extension is fetched from the stack. So normally there is no limitation for extensions nesting.

Maybe your extension interfere with the stack somehow and breaks the "$ext_info" variable? Try to reinstall extensions. Also you may send me your extension and I'll try to find out the cause of the bug.

Russian letters are encoded in two bytes in UTF-8, and Russian words are separated by spaces. So your condition will not work for Russian. Maybe we have to make an entry in lang files containing the word separator.

148

(4 replies, posted in PunBB 1.3 troubleshooting)

So, take a look at the line 11 of the correct template. It should be

<div <!-- forum_page -->>

149

(4 replies, posted in PunBB 1.3 troubleshooting)

It looks like the code in the main.tpl template. Check the template in the default location (include/template/main.tpl) and in the style directory (a style can have its own template).

pun_pm 1.2.9 has been released.