101

(5 replies, posted in PunBB 1.3 troubleshooting)

Fixed.

102

(3 replies, posted in PunBB 1.3 troubleshooting)

Fixed.

103

(7 replies, posted in PunBB 1.3 troubleshooting)

Hidden from moderators.

104

(11 replies, posted in PunBB 1.3 troubleshooting)

fpouget wrote:

The special character are not converted properly the forum name on the forum table and the Category Name on the category table

Géomatique  --> G

Hmm. It only affects forum names and category names? Usernames, posts, subject etc are converted correctly?

fpouget wrote:

I've too several mistakes on the index.php

Notice: unserialize() [function.unserialize]: Error at offset 7 of 21 bytes in /home/ftp/upload/www/forum2/index.php on line 189

Notice: unserialize() [function.unserialize]: Error at offset 23 of 38 bytes in /home/ftp/upload/www/forum2/index.php on line 189

may be is linked ?

Not linked. The index.php error is because there's something wrong with your array of moderators. Have you had any mod installed that fiddles with the moderators?

Fixed.

106

(1 replies, posted in PunBB 1.3 troubleshooting)

Should be fixed.

Fixed.

108

(7 replies, posted in PunBB 1.3 troubleshooting)

Done.

109

(2 replies, posted in PunBB 1.3 troubleshooting)

Fixed.

1. Will be fixed.

2. Currently it allows for duplicate URLs. We're considering ways to solve the problem.

3. Not sure what you mean by change Atom and RSS to that type. It changes the URLs to the Atom and RSS feeds, but the old URLs still work.

111

(1 replies, posted in PunBB 1.3 troubleshooting)

Fixed.

Hmm. Isn't a default value of NULL equivalent to no default value at all?

113

(7 replies, posted in PunBB 1.3 troubleshooting)

Alright, alright. I'll change it back. I used to have it as a password field and then people complained about that.

Recent topics? Don't we already have that through the quicksearches?

115

(2 replies, posted in PunBB 1.3 troubleshooting)

And a good one at that smile

116

(38 replies, posted in PunBB 1.3 troubleshooting)

I agree that sef_friendly() needs a bit more work. Essentially, we only want A-Za-z0-9 in the URL.

117

(54 replies, posted in PunBB 1.3 troubleshooting)

MattF wrote:
Rickard wrote:

People putting code tags in the description is not something we want.

Just out of curiosity. Why?

Because it's not what the description field is for. If you want fancy markup, add it to the template.

118

(3 replies, posted in PunBB 1.3 troubleshooting)

It's coming. I just haven't finished the server side stuff for the manual checks.

119

(54 replies, posted in PunBB 1.3 troubleshooting)

Yeah, but it's overkill. There are other issues as well. We would only want to support a subset of BBCode. People putting code tags in the description is not something we want.

Settle down people. There's no need to start arguing over this smile It's a minor issue. We'll discuss this internally and see what we come up with.

As an alternative to PunXS, for those of you who won't be able to use it, there'll be an extension that allows you to edit hooks in place without reinstalling the extension all the time.

122

(54 replies, posted in PunBB 1.3 troubleshooting)

elbekko wrote:

Or just allow the use of BBCode in there, problem solved by the mighty parser.

You said it. The "mighty" parser. We don't want to have to fire it up on all pages.

123

(3 replies, posted in PunBB 1.3 troubleshooting)

tongue

124

(4 replies, posted in PunBB 1.3 troubleshooting)

1. Yes. Honestly, I can't remember what database changes we've done in 1.2 -> 1.2.16, but checking for them and applying them if needed in the 1.3 update script should be easy.

The 1.3 update script will convert your 1.2.12 database without problems. Essentially, you could just upload the 1.3 files, paste your config.php from 1.2 into the 1.3 folder and run the update script.

I think my commit regarding the ellipsis caught all of them. There are some code comments that I didn't touch, but all the output should now be correct.

I think for the non-breaking space, we need the numeric entity. If not, I'm convinced language pack authors will just overwrite it with a regular space.

My main issue with apostrophes and quotes is that if we use the "fancy" versions in the language packs, we need to make sure that they're also used in posts. That means translating computerized versions either as the post is inserted into the database or right before display. I'm not sure I like it. There's potential for problems.