Discuss: phpBB 3.0.5 released

[DragonMaster1]

How come we have to go through all this discussion repeatedly about releasing the code changes?

This has happened on each update and eventually they got released because many of us can’t utilize the auto-update.

I have over 100 mods and there is no way it will work automatically.

It would be nice to get a SUPPORT TEAM RELEASE rather than one that a member might throw together.

Why is it SO HARD to supply this also?

Ver 2 was never such a problem with ANY of the updates.

Many of us use beta’s or developmental mods and these will break the auto-update every time.

These updates need to be EASY to do for EVERYONE including people who are unable to use the automatic update as-is.

Personally I feel that I would rather have more updates that are just easier to apply, instead of a huge one that for the more modded boards will break it every time. It takes a heck of a LOT less time to make a smaller update than to completely re-mod your entire board from a base install of the new system

[narqelion]

That is what the auto updater does.

That and many more unexpected little surprises. Fyi...many people with MOD's will not have access to patch and need to use the changed files only package and manually apply the code changes.

[Phil]

The code changes need to be generated and verified mostly by hand, ergo their production is very time consuming. That's why they were discontinued in the first place -- the automatic updater works just fine for 99.99999% of instances (in fact, it does nearly the same thing as the code changes... find the old blocks of code and replace them with the changed version), and that remaining amount should be utilizing the patch files.

Simply put, would you rather the Support Team spend its time creating a code changes package, or supporting the software, especially when there are numerous perfectly viable alternatives to the package. I'd be willing to bet most of the users who are upset about the lack of the package have not actually tried the automatic updater.

As for problems with phpBB2 updates, the code changes package was very frequently mistaken, given the fact it was automatically generated from the patch file (unfortunately, this does not go as well as one would think). It was usually amended some hours after its release (as have been the only attempts at releasing a code changes package for phpBB3).

Style and language changes are made available as they are much smaller and easier to create/test. The main package update is perfectly doable by the automatic updater without issue.

[Brogan]

I'd be willing to bet most of the users who are upset about the lack of the package have not actually tried the automatic updater.

I used it for 3.0.3 to 3.0.4 and it didn't work. This was on a board with very few mods.
I even started a thread about the problems but received no response.

As such I am reluctant to use the automatic updater for this release

Which leaves me with one alternative and that is to go through 14,000 lines by hand applying manual edits.
Hardly an ideal solution.

[Phil]

Make a backup and give it another shot. Generally, the auto updater failing is a sign of the user picking the wrong action to resolve a conflict (mind you, if they aren't capable of working that out they probably can't merge conflicts by hand using a code changes package, either). If you aren't sure of what to use, post in the support forum.

[Brogan]

I'll try the auto updater on my local install, see how I get on.

BTW, is there a list of all changed/affected files anywhere?
I can quickly scan that and see which ones I might have an issue with and do those ones manually or double check them after the upgrade.

[SamG]

Hardly an ideal solution.

There probably is no such thing as an ideal solution for all parties involved when updating user-customized software. The challenge is taking the open source approach to its logical end while still maintaining for all users the ability to update the core.

Since the teams have been kind enough to allow community-submitted code change packages, and if the update system is proving crippled for a significant number of users (I myself have not had the problems reported by some), perhaps a group of users can agree to relieve the teams of the work involved and benefit the rest of community at the same time?

[narqelion]

BTW, is there a list of all changed/affected files anywhere?

Yes, the changed files only package. It should contain the changed files for all previous versions of 3.0.x -> 3.0.5.

[momentum]

Make a backup and give it another shot. Generally, the auto updater failing is a sign of the user picking the wrong action to resolve a conflict....

No. In my case the FTP transfer of changed files simply refused to work, leaving the update incomplete.

Craig.

[ToonArmy]

BTW, is there a list of all changed/affected files anywhere?

Changed files 3.0.4 to 3.0.5:

1. adm/index.php
2. adm/style/acp_captcha.html
3. adm/style/acp_database.html
4. adm/style/acp_email.html
5. adm/style/acp_forums.html
6. adm/style/acp_permissions.html
7. adm/style/acp_search.html
8. adm/style/acp_styles.html
9. adm/style/install_update.html
10. adm/style/overall_header.html
11. adm/style/simple_header.html
12. download/file.php
13. includes/acm/acm_file.php
14. includes/acp/acp_attachments.php
15. includes/acp/acp_captcha.php
16. includes/acp/acp_database.php
17. includes/acp/acp_email.php
18. includes/acp/acp_forums.php
19. includes/acp/acp_inactive.php
20. includes/acp/acp_jabber.php
21. includes/acp/acp_main.php
22. includes/acp/acp_permissions.php
23. includes/acp/acp_profile.php
24. includes/acp/acp_search.php
25. includes/acp/acp_styles.php
26. includes/acp/acp_users.php
27. includes/acp/auth.php
28. includes/auth/auth_apache.php
29. includes/auth/auth_db.php
30. includes/bbcode.php
31. includes/captcha/captcha_gd.php
32. includes/constants.php
33. includes/db/db_tools.php
34. includes/db/mysql.php
35. includes/db/postgres.php
36. includes/diff/diff.php
37. includes/diff/engine.php
38. includes/diff/renderer.php
39. includes/functions.php
40. includes/functions_admin.php
41. includes/functions_content.php
42. includes/functions_display.php
43. includes/functions_install.php
44. includes/functions_messenger.php
45. includes/functions_posting.php
46. includes/functions_privmsgs.php
47. includes/functions_profile_fields.php
48. includes/functions_template.php
49. includes/functions_transfer.php
50. includes/functions_upload.php
51. includes/functions_user.php
52. includes/mcp/mcp_main.php
53. includes/mcp/mcp_notes.php
54. includes/mcp/mcp_queue.php
55. includes/mcp/mcp_topic.php
56. includes/mcp/mcp_warn.php
57. includes/message_parser.php
58. includes/search/fulltext_mysql.php
59. includes/search/fulltext_native.php
60. includes/session.php
61. includes/ucp/ucp_activate.php
62. includes/ucp/ucp_attachments.php
63. includes/ucp/ucp_groups.php
64. includes/ucp/ucp_main.php
65. includes/ucp/ucp_pm_compose.php
66. includes/ucp/ucp_pm_viewfolder.php
67. includes/ucp/ucp_pm_viewmessage.php
68. includes/ucp/ucp_profile.php
69. includes/ucp/ucp_register.php
70. includes/ucp/ucp_resend.php
71. language/en/acp/board.php
72. language/en/acp/common.php
73. language/en/acp/forums.php
74. language/en/acp/permissions.php
75. language/en/acp/posting.php
76. language/en/acp/profile.php
77. language/en/acp/search.php
78. language/en/common.php
79. language/en/email/newtopic_notify.txt
80. language/en/help_bbcode.php
81. language/en/install.php
82. language/en/posting.php
83. language/en/search.php
84. language/en/ucp.php
85. mcp.php
86. memberlist.php
87. posting.php
88. search.php
89. style.php
90. styles/prosilver/imageset/imageset.cfg
91. styles/prosilver/style.cfg
92. styles/prosilver/template/attachment.html
93. styles/prosilver/template/editor.js
94. styles/prosilver/template/forum_fn.js
95. styles/prosilver/template/mcp_notes_user.html
96. styles/prosilver/template/mcp_topic.html
97. styles/prosilver/template/mcp_warn_user.html
98. styles/prosilver/template/memberlist_body.html
99. styles/prosilver/template/overall_header.html
100. styles/prosilver/template/posting_buttons.html
101. styles/prosilver/template/posting_editor.html
102. styles/prosilver/template/posting_review.html
103. styles/prosilver/template/posting_topic_review.html
104. styles/prosilver/template/simple_header.html
105. styles/prosilver/template/template.cfg
106. styles/prosilver/template/ucp_main_bookmarks.html
107. styles/prosilver/template/ucp_main_subscribed.html
108. styles/prosilver/template/ucp_pm_viewmessage.html
109. styles/prosilver/template/ucp_register.html
110. styles/prosilver/template/viewforum_body.html
111. styles/prosilver/template/viewtopic_body.html
112. styles/prosilver/template/viewtopic_print.html
113. styles/prosilver/theme/bidi.css
114. styles/prosilver/theme/colours.css
115. styles/prosilver/theme/common.css
116. styles/prosilver/theme/content.css
117. styles/prosilver/theme/links.css
118. styles/prosilver/theme/theme.cfg
119. styles/prosilver/theme/tweaks.css
120. styles/subsilver2/imageset/imageset.cfg
121. styles/subsilver2/style.cfg
122. styles/subsilver2/template/editor.js
123. styles/subsilver2/template/index_body.html
124. styles/subsilver2/template/mcp_notes_user.html
125. styles/subsilver2/template/mcp_warn_user.html
126. styles/subsilver2/template/overall_header.html
127. styles/subsilver2/template/posting_body.html
128. styles/subsilver2/template/posting_buttons.html
129. styles/subsilver2/template/posting_review.html
130. styles/subsilver2/template/posting_topic_review.html
131. styles/subsilver2/template/template.cfg
132. styles/subsilver2/template/ucp_header.html
133. styles/subsilver2/template/ucp_register.html
134. styles/subsilver2/template/ucp_zebra_foes.html
135. styles/subsilver2/template/viewforum_body.html
136. styles/subsilver2/theme/theme.cfg
137. viewforum.php
138. viewonline.php
139. viewtopic.php

[ToonArmy]

Make a backup and give it another shot. Generally, the auto updater failing is a sign of the user picking the wrong action to resolve a conflict....

No. In my case the FTP transfer of changed files simply refused to work, leaving the update incomplete.

Craig.

We seem to have a regression there.

[momentum]

We seem to have a regression there.

How so?

Craig.

[Phil]

We seem to have a regression there.

How so?

Craig.

A bug fix committed earlier seems to have broken this for one of PHP's two FTP extensions.

[momentum]

How so?

Craig.

A bug fix committed earlier seems to have broken this for one of PHP's two FTP extensions.

Sorry if I'm confusing the issue, but the failure I was referring to was my own attempted update from 3.0.2 to 3.0.3 about six months back.

I eventually started again with the base package and re-applied all the MODs, exactly as I intend to do this time.

Craig.

[DragonMaster1]

Exactly what I had to do for 302 - 304 and it took a week plus to reinstall my 100+ mods