26

(154 replies, posted in Supported extensions)

Is there an option to disable PMs? I didn't find any.

27

(27 replies, posted in News)

I take you went straight to 1.3 because you devs wouldn't want to wait for FluxBB 1.3 anymore, I wonder if you plan to update your code to match FluxBB's in the future, say a v1.3.1, I'm interested in extensions compatibility.

28

(6 replies, posted in PunBB 1.3 additions)

Sorry I don't think I have time for that but I'm translating FluxBB, perhaps those files might help you.

29

(6 replies, posted in PunBB 1.3 additions)

You got an error here.

30

(15 replies, posted in News)

Is RC2 currently used on this domain?

31

(1 replies, posted in PunBB 1.2 discussion)

It will work.

You can with a backup of your 1.2.x forum though.

33

(52 replies, posted in PunBB 1.3 additions)

Anatoly wrote:

We've just invited a dev into the team to deal with markup. It will take some time for her to get involved.

Roger that. Thanks for info.

34

(52 replies, posted in PunBB 1.3 additions)

I lost a bit of contacts with PunBB lately, I was wondering who's the CSS freak in the dev team now, if any.

35

(17 replies, posted in PunBB 1.3 troubleshooting)

Utchin wrote:

style="text-align=centre"

I'm not sure CSS supports centre, you should user center.
Use this code

<div style="text-align: center">google adsense code</div>

36

(17 replies, posted in PunBB 1.3 troubleshooting)

fantasma wrote:

thanks for info but i have resolved with e simply div in main.tpl

<div align="center">google adsense code</div>

XHTML strict doesn't support the align attribute. You should use CSS.

37

(5 replies, posted in PunBB 1.2 discussion)

Extensions.

I think you got it all wrong Smartys, hm2k seems to complain about phpBB3 pointing out a few useless features or missing features that instead PunBB has.

39

(7 replies, posted in PunBB 1.3 troubleshooting)

Paul wrote:

If you just add your stylesheet to the list in Oxygen.php before the IE specific stylesheets then that should do it.

You can also add your own meta tags there since Oxygen.php is included inside the head tag.

40

(26 replies, posted in PunBB 1.3 troubleshooting)

MalZon wrote:

I'm got a phpBB 1.3 forum

Blasphemy!

MalZon wrote:

I fell lika hadicap without PM

You can use the email for the moment.

kierownik wrote:

I do not think they will be included in the download, but they will be official supported.

That's my guess as well, I'm just talking of extensions made by the dev team.

I believe the subject says all, what is the dev team planning as official extension for v1.3?
So far I've read the Private message system and an antispam, will you make a poll extension as well?

43

(26 replies, posted in PunBB 1.3 troubleshooting)

How the 1.2 PM mod can be adapted to 1.3, I guess he's asking that.

44

(3 replies, posted in PunBB 1.3 troubleshooting)

Out of curiosity, why you don't use foreach?

That's pretty normal I believe.

I believe that CSS would be enough since every forum is marked with a different (and progressive) ID.

47

(151 replies, posted in PunBB 1.3 extensions)

Rickard wrote:

We can't do that in functions.php because by the time we include functions.php, the hooks system hasn't been initialized yet. I recommend you use co_common instead.

Gotcha. Thanks.

48

(151 replies, posted in PunBB 1.3 extensions)

A hook in functions.php outside the functions would allow to add custom ones.

49

(19 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

No, it's very simple. You should be able to understand it just by looking at the code. wink
Basically, when POSTing, you need to include a hidden field. The name should be csrf_token and the value should be the output of the function generate_csrf_token. The function takes one parameter, which is the absolute URL of the page you're submitting to.

Thanks Smartys, I was actually using the relative path.

(sidenote: the function's name is generate_form_token, not generate_csrf_token, just for those wondering).

50

(19 replies, posted in PunBB 1.3 troubleshooting)

Smartys wrote:

You can't get around the CSRF check. You need to implement it.

Can you explain how to do that or is too complicated?