[Discuss] phpBB 3.2 Rhea is near - help us test it now!

[naderman]

Please use this topic to discuss the blog post phpBB 3.2 Rhea is near - help us test it now!

[HiFiKabin]

I have had b1 running for 3 weeks now (basically so I can test and adjust my Extensions) and have not had any problems so far. Also KeyCaptcha have ported their CAPTCHA for me so that its works 3.2.x. I have been using it for a week also without error.

One question though. Why oh why are CAPTCHAS that have been 'broken' by bots for years included? They impart a false sense of security to new users who know nothing about CAPTCHAS.

"They are in the package, so they must be good"

Server using php 5.5.33

[david63]

Been using 3.2, with varying degrees of success since a1 as a development tool. Good to see that the install/update has improved in b2.

Found a couple of bugs that have been reported and fixed.

One thing that I have found is that there are several extensions that will not work at all with 3.2 - there are some that will work but may look a bit strange due to moving to fontawsome.

I suspect that the majority of users will not notice very much changed in the "user experience" but there have been some significant changes in the background.

[3Di]

Maybe posting the pre-release here into the Announcements helps to speed up the testings process.

[nextgen]

Maybe posting the pre-release here into the Announcements helps to speed up the testings process.

+1

[RMcGirr83]

Install went without a hitch, update within a local Windows 10 environment (using xampp) failed as the system was unable to delete the files that were no longer needed.

[naderman]

Maybe posting the pre-release here into the Announcements helps to speed up the testings process.

+1

We'll start doing that with RCs for which we offer official support, see our list for where the respective releases are to be published: https://area51.phpbb.com/phpBB/viewtopi ... 99&t=48841

[3Di]

Maybe posting the pre-release here into the Announcements helps to speed up the testings process.

+1

We'll start doing that with RCs for which we offer official support, see our list for where the respective releases are to be published: https://area51.phpbb.com/phpBB/viewtopi ... 99&t=48841

Hi nadermann
I am aware of the link you above posted, I am always lurking here and there.

The problem here is that there is a lack of testers hence you posted this topic, at those times of Olympus I do correctly recall we posted also Betas into the Announcements and that worked very good, see here an example
viewtopic.php?f=14&t=427216 Olympus Beta2

What's the audience of the Blog against the Announcements (no comparison, uh?), the more the better.
I am not arguing your choice, I am trying to give a constructive feedback.

Last but not least:
what do you expect this topic will be for?
To say something like the install has been smooth or so on, bugs report, or what else?

I am here a little bit confused about its purpose.

Thanks for your attention.

[david63]

In the link that was posted above (must admit that having seen it some time ago I had forgotten about it) there is mention of various groups being notified about the different releases but no mention about keeping extension developers informed. As in some releases (3.2 being a notable example) there are some significant changes that affect some extensions could some mechanism be found to keep these people informed?

[HiFiKabin]

I totally agree with you David. Any new version that potentially effects Extensions should be made known to Ext Developers sooner rather than later.

For example, 3.2.x uses Font Awsomness, 3.1.x uses icons therefore any 3.1.x extension that uses icons will not work with 3.2.x (well, it will work but look awful)

[3Di]

I totally agree with you David. Any new version that potentially effects Extensions should be made known to Ext Developers sooner rather than later.

For example, 3.2.x uses Font Awsomness, 3.1.x uses icons therefore any 3.1.x extension that uses icons will not work with 3.2.x (well, it will work but look awful)

There are stickies into the Extension writers forum about that, none of them though still covers the font awsome thinghy AFAIR.

Another point here arises, due to the incoming RHEA, how the forums will be ordered?
Will be the Olympus forums be collapsed into a Forum archive like has been done for 2.0.x?

[RMcGirr83]

There are stickies into the Extension writers forum about that, none of them though still covers the font awsome thinghy AFAIR.

Nor the new file upload ability either I don't believe.

[Kailey]

There are stickies into the Extension writers forum about that, none of them though still covers the font awsome thinghy AFAIR.

They addressed that in phpBB 3.2 Upgrade Notes for Extensions:

Font Awesome (3.2 only)
phpBB 3.2 has replaced almost every icon with a font icon using the Font Awesome toolkit. This has resulted in significant template changes to Prosilver, including many new classes. If your extension makes use of any of Prosilver's icons, or in any way recreates any of Prosilver's template layouts that include any iconography, you should examine if and how your template files may be impacted and need to be adjusted to be compliant with phpBB 3.2. Some backwards compatibility has been retained so, for example, extensions adding links to the nav bars should still work as expected. You may also consider leveraging the new font icons to your advantage as they make it quite easy now to add any of the available Font Awesome icons to improve GUI elements of your extension. For example, if you extension has a "delete" link or button, you could add a nice little Trash Can icon to that link or button.

[3Di]

Thanks kinerity, my memory is getting more older than me

Nonetheless all of this should be (everybody of us is called here) adressed into an outstanding WIKI page at least.

edit: mismatch error

[david63]

There are stickies into the Extension writers forum about that,

But the stickies do not mention the core file changes that affect extensions.