1

(19 replies, posted in PunBB 1.3 extensions)

+1
really easy setup, I hope every mod was an extension!

Many thanks for it!
Oliver

2

(115 replies, posted in Supported extensions)

For 1.3, this works great!
http://mattstypa.com/recaptcha-for-punbb/

HTH
Oliver

3

(8 replies, posted in PunBB 1.3 extensions)

This one worked for me, with reCaptcha.net support
http://mattstypa.com/recaptcha-for-punbb/

Slavok wrote:

I can't reproduce this data loss. I created a db with latin1_spanish_ci collation, wrote a post with message "123á456", and after the migration I do see it. What did I miss?

Hi Slavok,
have you configured your mysql following these screenshots?
http://punbb.informer.com/forums/post/124662/#p124662

Parpalak,
glad to know you will look a the bug next week.

Many thanks to you both
Oliver

If you have been updating punbb 1.2.x in the past, you knew punbb always update the DB but only the data used by punbb installation itself.
Never before punbb modified user data, posts and topics, and that warning of behavior change has never been made.

People use to read documentation prior warnings in a install script.
http://punbb.informer.com/docs/install.html

It would make sense if punbb developers acknowledge the problem and try to find a solution with the community. Also, it will really help to document big changes in the upgrade procedure, like parsing and changing the charset of your posts and topics.

HTH
Oliver

I think the problem is that punbb can not confirm it. so, there is no fix. All we can do is to keep reporting it until they can confirm it.

For me was a big deal, I lost some data because I have a not so recent backup. Nowhere in the upgrade instrucctions were a warning about modifying the DB data. Never before a punbb upgrade has modifyied user DB data sad

Mr.Awesome wrote:

So how can I fix this?

There is no fix from punbb, just revert your DB to a recent backup and stay in punbb 1.2

HTH
Oliver

Many thanks pepak.

What I want is to stop the further data loss that the upgrade script does. The users should be the ones that migrate the data to UTF-8, *not* punbb's upgrade script.

Slavok, please remove the conversion code to UTF-8 in the migration script. It is not fail safe, it is not secure to continue its distribution

Thanks
Oliver

Thanks pepak,
have you done this all manually? There are many many columns in each table.

Should't the "upgrade" script have error checking in such a case?

Oliver

10

(6 replies, posted in PunBB 1.3 extensions)

we should check again all the mysql queries to see if the current queries work.
Seems to me that punbb broke too many things, starting with renaming historical variable names

11

(6 replies, posted in PunBB 1.3 extensions)

Hi Cereal,
thanks for the info.

Could you provide some help on how to provide a login for your users? Should I redirect to the Forum login?

Also, can you update the dokuwiki wiki about punbb:auth? Thanks
Oliver

Slavok, how can we advance in this solution?

Its clear punbb 1.3.2 is causing massive data loss when a forum is not in english.

Many thanks
Oliver

13

(6 replies, posted in PunBB 1.3 extensions)

Great!

just updated:
http://www.dokuwiki.org/auth:punbb

and tested it, work just fine.

Many many thanks Cereal!

Oliver

14

(56 replies, posted in PunBB 1.3 extensions)

may I request this captcha:
http://captcha.ru/en/

It works really fine for the new user.

Thanks
Oliver

15

(6 replies, posted in PunBB 1.3 extensions)

Hi,
I'm testing the integration of dokuwiki with punbb 1.3. It was working on punbb 1.2
http://www.dokuwiki.org/auth:punbb

The problem I get is that in every auth check Dokuwiki does, a punbb page appears asking the user to confirm the action. Something like Vista UAC but worse.

Is there a way to disable this check in punbb? Or is there a way to do auth integration in punbb?

Many thanks
Oliver

16

(58 replies, posted in PunBB.NET discussion)

So why don't you hire two more php devels? I have no problem against ASP, but I only have fear that punbb 1.4 will take the same time to develop that 1.3 did.

If .net developers are not hired, then just ignore this message wink

Can we have a if(defined('DO_NOT_USE_CUSTOM_UTF8')) return; settings?

Also I don't see anything wrong with supporting php4 only with a download plugin or compatibility pack. The idea right now is to only use PHP5 in all new installations.

Forgot to tell that my problem comes with the integration with dokuwiki, something that was broken until yesterday wink

I just posted a patch:
http://www.dokuwiki.org/auth:punbb

Thanks
Oliver

Hi,
I'm running a site that has dokuwiki integrated with punbb.

After upgrading to punbb 1.3, the dokuwiki auth_punbb just broke with this message:

Fatal error: Cannot redeclare utf8_strlen() in .../include/utf8/mbstring/core.php on line 26

So, how can I stop using punbb utf8 functions and instead use only php5 utf8 functions?

Thanks
Oliver

Hi Slavok,
I now have confirmed and reproduced the bug.

I created a topic with this subject:
"Topic 1 áéíóú this is a test"

and after the upgrade, the Topic ended up(I checked in phpmyadmin too):
"Topic 1 "

Please configure any punbb 1.2.x test forum like this, and then upgrade it to punbb 1.3.2 to confirm the bug:

Image 1
Image 2
Image 3

Thanks
Oliver
P.D.: this does not work in punbb.org, how do I post screenshots?

Hi Slavok,
I have a DB dump now, how can I sent it to you?

I have Centos 4.7, Mysql 4.1.22, MySQL charset UTF-8, MySQL tables in charset latin1_spanish_ci

Meanwhile I will do the upgrade again with a small about of data in the DB.

Thanks for your time
Oliver

Slavok wrote:

What DB, version are you using? Could you send us the dump of your database, please?

I was using mysql, just a create an empty DB, install punbb 1.2, insert a text like "123á456" and upgrade to punbb 1.3. You will loss the string "456" in all the text column of your DB sad

Will try to do some dump of the DB

Regards,
Oliver

22

(58 replies, posted in PunBB.NET discussion)

Since there are 2 developers working in punbb.net that are not working on punbb.org, there is the loss for punbb I think. Why have 2 teams while could have one bigger more powerfull team?

Also, punbb 1.3 took so long to launch, and now I don't see a punbb 1.3.3 until maybe the end of 2009. I will rather see more mod finished and maybe an upgrade routine that does not truncate all of your 1.2 forum text in your DB(migration to UTF-8 is broken and should not ship).

Of course there is place for all programing languages, but maintaing 2 code base is like shipping a forum with custom implementation of php5 in php4, a lost of time in my view. "Reuse as much as you can" should be the idea.

Good luck and let see how this evolves

Oliver

hi,
the converstion to utf-8 in the punbb installation/upgrade script delete all the text that comes after an accent (like in áéíóú).

This means that upgrading to punbb 1.3 will mean loss of data. You will end up with text that just stops. Its a problem in the database, I confirmed with pma

Don't know why a forum upgrade has to modify any user data in the database

Don't know why a forum software can not use the official php files, instead of shipping with some copy of php4 files.

Right now I have to rollback and loss hours of work. Punbb migration from 1.2 to 1.3 is not looking any good and sorry about the flame, but I never found any problem with punbb until now, and I start not to like it as I used to ...

It worked like this:
<!-- forum_include "FILE" -->

Many thanks!

It worked like this:
<!-- forum_include "FILE" -->
thanks