76

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:
Mpok wrote:
Rickard wrote:

Because those tables don't have any text/varchar fields, only integers.

Yep, i know, that's why i said "it's not a big deal", but for consistency only, i think it can be done anyway...

Agreed, for consistency we should have it (since new tables will have it).

With our setup on a new install, the Online table is the only table that is not utf8_general_ci. It is latin1_swedish_ci. Is this something we have to get our hosting provider to change?

77

(3 replies, posted in PunBB 1.3 troubleshooting)

On a related note, why isn't there a flood protection settings for Guests?

78

(81 replies, posted in PunBB 1.3 troubleshooting)

The issue is on the test server. This may not happen on the live server when upgrading. For now, I will try a backup of it on the live server and report back if any issues. Thanks.

79

(3 replies, posted in PunBB 1.3 troubleshooting)

Yes, the pun_link smile

80

(81 replies, posted in PunBB 1.3 troubleshooting)

Do you need access to the live server or the test server? The test server is a local server using XAMPP.

There is a bug in the breadcrumb URLs in Quote page.

82

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

Is that without calling SET NAMES?

Yes, this line is removed.

83

(3 replies, posted in PunBB 1.3 troubleshooting)

"Search flood interval" is set, but it is not being enforced.

84

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

The current character set is a text field. It's something you set. Change it to UTF-8 and then run it (with the define removed).

Done. Problem persists.

On the test server:
MySQL charset:  UTF-8 Unicode (utf8)
MySQL connection collation: utf8_unicode_ci

Does this make a difference?

Thanks.

85

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

You need to remove the define() line entirely, changing the value to 0 isn't enough.

Removed define().

Smartys wrote:

And when you forced the conversion, you said it was converting from UTF-8?

Enable conversion is checked.
ISO-8859-1 is the current character set.

Sorry for being dense. wink

86

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

Another way that *might* work is to modify db_update.php so it calls SET NAMES (we currently don't if you're upgrading) and ask the script to convert from UTF-8. I don't know exactly how that will work tongue

It appears to not work. I may not be doing it correctly. Here is what I did. In db_updated.php, changed PUN_NO_SET_NAMES from 1 to 0. In the script, forced the conversion.

87

(1 replies, posted in PunBB 1.3 troubleshooting)

In the reports, the URLs are still SEF.

88

(52 replies, posted in PunBB 1.3 troubleshooting)

The navigation links is different with userlist.php.
- Remove : after Pages.
- Bold Pages.

89

(81 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

A. What was the charset used to insert that data into the database/present it in 1.2..

UTF-8 Unicode (utf8)

Smartys wrote:

B. What was the collation of the database tables in 1.2.

utf8_general_ci

Smartys wrote:

C. Did you choose to have the data converted to UTF-8? If so, what collation did you give to convert from?

Tested both ways. Used the default collation. Will redo it again to double check the collation.

Smartys wrote:

If you're using the mysql dblayer, make sure you're using the latest copy from SVN.

Yes, using the latest copy.

90

(81 replies, posted in PunBB 1.3 troubleshooting)

In MySQL, the subject/message are stored as: Happy Valentine´s Day

In 1.2.17, the subject/message are displayed as: Happy Valentine´s Day
In 1.3, the subject/message are displayed as: Happy Valentine´s Day

How to fix?

Thanks.

91

(1 replies, posted in PunBB 1.3 troubleshooting)

Should unverified users be listed in "Newest registered user", in the user list, and be counted in the total number of registered users? Technically, they are not members until verified when "Verify registrations" is enabled. Hopefully, this will deter spammers from creating bogus accounts just to have links to their information without having to verify.

92

(52 replies, posted in PunBB 1.3 troubleshooting)

Please keep the order the same. I prefer the 2nd one. Thanks.

in viewtopic:
Registered
From
Posts

in profile:
From
Registered
Posts

93

(6 replies, posted in PunBB 1.3 troubleshooting)

Please also censor the email link in viewtopic.php. Thanks.

viewtopic.php

URL is not censored for the author's website link.

95

(3 replies, posted in PunBB 1.3 troubleshooting)

We want to remove Jabber, ICQ, MSN, AOL IM, and Yahoo! Messenger. Is it possible to remove these fields from the Identity tab with an extension?

96

(6 replies, posted in PunBB 1.3 troubleshooting)

Censor on email too just in case "Display your e-mail address to other users" is enabled.

Here are the 2 different scenarios:

Log in as a Moderator that only has ban permission. Go to a user's profile. The "Adminstration" tab is not available.

Log in as a Moderator with all moderators permissions. Go to a user's profile. The "Administration" tab is now available.

When "Allow users moderator privileges" and "Allow moderators to ban users" are checked and the other moderator permissions are unchecked, then the Administration tab doesn't appear under Profile. The "Administration" should not be dependent on the other moderator permissions.

If censoring is enabled, apply censoring to the subject.

If linkify is enabled, only hyperlink usernames if the user belongs to a group that has permission to view profiles.

100

(1 replies, posted in PunBB 1.3 troubleshooting)

Censoring is not being applied to Jabber.