Correct. Nice idea smile

Russia.

From the bug report:

oo wrote:

I have found and uninstalled the extension

YonasH's repository
Created by YonasH.
Version v1.0.
Stick all updates in extension list. Checks for updates of my extensions and let you to automatically install them.

YonasH, consider this report, please smile

Fixed.

479

(1 replies, posted in PunBB 1.3 bug reports)

Fixed.

480

(56 replies, posted in PunBB 1.3 extensions)

oliversl wrote:

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

It works really fine for the new user.

This script is not released under GPL. We have to get in contact with the author of this script and to discuss license details.

481

(56 replies, posted in PunBB 1.3 extensions)

It should be noted that captcha is shown on the login page form after 5 login fails.

I've just tested PunBB and pun_antispam. Everything works fine. Are you sure you are using the last version of pun_antispam and PunBB?

482

(17 replies, posted in PunBB 1.3 troubleshooting)

MattF wrote:

If an internal zone is set up incorrectly, that is not for PunBB to decide. A domain should be in the form of *.*. Only localhost is exempt from that rule.

I think it's not only a question "how an internal zone should be set up", but it's also a question "how an internal zone of real users is set up". For example, IE6 doesn't follow standards, but this fact doesn't mean that Oxygen style must be free of hacks for IE6. I still doubt that we have to allow only URLs like *.*.

MattF wrote:

Btw, in reference to your earlier post, sloppy, (or none, in this case, it seems), input validation is *never* a feature request. It is a bug.

Sure. Probably, I've interpreted terms in a slightly different way.

483

(17 replies, posted in PunBB 1.3 troubleshooting)

If Messenger really looks like an e-mail, its validation can be easily added.

But I have an objection about the 'website' field. Forum can be installed for users of a LAN. Users may write there simply their computer names. A computer name doesn't have a form like '<something>.com' and will fail a validation.

484

(17 replies, posted in PunBB 1.3 troubleshooting)

There is a check for the url field: http://punbb.informer.com/trac/browser/ … e.php#L924

What do you mean saying 'validation'? It's easy to add an regex and a message 'invalid url'. If you mean this I'll add it to feature requests.

485

(2 replies, posted in PunBB 1.3 discussion)

We have released PunBB 1.3 and will support it for a long time.

PunBB 1.3 has a hotfix system. Hotfixes are released as fast as possible after security bugs are reported.

486

(5 replies, posted in PunBB 1.3 extensions)

AdsBB wrote:

hook editor extension where you just select the appropriate hook and add the code directly

This idea has already been implemented in Anycode Tool extension smile

Ok, I'll try to do this next week.

Posts and topics processing is required because 1.3 uses UTF-8. Also its parser works in a different way.

oliversl wrote:

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

Actually there is no instruction of upgrading from 1.2 to 1.3. The instruction is here:
http://punbb.informer.com/wiki/punbb13/ … _punbb_1.2

It's our oversight if people use old documentation instead new one. We'll move all docs to wiki.

The issue has already been acknowledged:
http://punbb.informer.com/wiki/punbb13/ … 1.3.2_bugs
However, we have no precise description of the issue (due to a lack of repeatability) and consequently can't suggest a fix.

oliversl wrote:

Nowhere in the upgrade instructions were a warning about modifying the DB data.

Seems like the warning is there.

490

(20 replies, posted in PunBB 1.3 extensions)

Yes, this template must work for PunBB 1.3.

You may see the code of manifest.xml of any official extension as an example. I'd advice to look into pun_bbcode manifest.xml, because it's quite simple.

491

(2 replies, posted in PunBB 1.3 troubleshooting)

Check the config.php file in the forum directory. Absolute URL of your forum is stored there.

492

(32 replies, posted in PunBB 1.3 discussion)

Have you got the desirable results?

Could you shortly describe here the list of changes (or post diff) you have made, please? Maybe this will help somebody else.

By the way, what about banning the range of IP adresses? Seems like this feature must be disabled while moving to md5(IP) values.

493

(20 replies, posted in PunBB 1.3 extensions)

Yes, there is a lack of documentation at the moment. We have to fix it.

Read about extensions developing for FluxBB. Extension developing for PunBB is very similar.

Also you can read about hooks here: http://punbb.informer.com/forums/topic/ … are-hooks/

494

(4 replies, posted in PunBB 1.3 discussion)

I completely agree.

But it is logical that a new markup (or maybe some kind of template system) will be adopted in the next version of PunBB. To change the markup of 1.3 means at least to cause a headache to extension developers. Personally I'd like to fix all bugs of 1.3 and to start developing of a new version.

495

(32 replies, posted in PunBB 1.3 discussion)

PunBB has some features based on users' IP. For example, moderators can ban users by IP. I think replacing IP with an indentification code isn't quite a simple task. Do a search of 'IP' text over all forum files to find where processing of IP is, if you want to make changes by yourself. Or maybe someone of community members will help you.

496

(2 replies, posted in PunBB 1.3 discussion)

Thanks, I have applied your solution.

I should like to draw the attention of creators of language packs to the recent changes in the file lang/English/topic.php. Please, make the necessary changes to your language packs.

It's a markup problem, not only CSS. Consider the new fix: http://punbb.informer.com/trac/changeset/1080

Fixed.

Fixed.

500

(4 replies, posted in PunBB 1.3 discussion)

No markup changes are planned for PunBB 1.3. We've had enough while adopting Paul's markup for PunBB 1.3 final release.

However, the markup contains several bugs. We'll fix them.

We don't plan to import code changes from FluxBB 1.3 except certain bug fixes.