Development Discussion Board

As Arty already pointed out, 5.3.23 IS >= 5.3.3. You should review the PHP version history page if you're still confused or insist that it is not.
Why not give an answer instead of pointing me to what I already have stated as knowing? Is this being constructive and useful? :roll:

I could point ...

Arty wrote:5.3.23 is actually newer than 5.3.3. ".23" does not mean ".2.3"

5.3.2x is newer than 5.3.3 I know. That is not the issue as 5.3.2x is not >= 5.3.3.

Perhaps Phar should get a new abacus.

As I say, update to greater than or equal to 5.3.3 and you'll be good to go.

5.3.23 ≠ 5.3.3

Update your php version to >=5.3.3 and you will be good to go.

Are you using >=php 5.3.3 and if so, does Phar appear in your phpinfo() ?

You have composer.phar in phpBB's parent directory?

If not, copy it from the root of the download file into the phpBB's parent folder.

You can have composer.phar in the phpBB3 folder and install by php ./composer.phar install --dev (notice the ./ path instead of ../)

EDIT For clarity:
You ...

A couple of thoughts.

1. Remove read private messages from notifications or at least a Remove button next to Mark read?

2. Remove pagination from Manage notifications when empty which then brings it into line with Manage subscriptions/bookmarks/drafts/attachments?

1. Could you explain that ...

A couple of thoughts.

1. Remove read private messages from notifications or at least a Remove button next to Mark read?

2. Remove pagination from Manage notifications when empty which then brings it into line with Manage subscriptions/bookmarks/drafts/attachments?

Done.

http://tracker.phpbb.com/browse/PHPBB3-11382

EDIT: the missing entry is for sending statistical information after install completes (thanks David).

Using today's build (notifications) ..

Can install on apache.

Can't install cleanly or update on nginx. An install runs up to sub-final when redeclare class phpbb_db_migration_data_30x_3_0_3_rc1 error is thrown.
Ignoring the error, the board seems useable since the database is populated to a point ...

EDIT: yes, running the latest from yesterday.

I'm thinking it is due to rc causing the issue which is why I suggested those changes initially.

Will keep combining rc's into each release to see if I can get a positive upgrade.