phpBB 3.0.11 Release Candidate 1 published

[bantu]

I really have no intention to spend a lot of time to manually edit these. If you have an idea how to improve the automated tool, I'll happily merge your pull request for the build script.

+1

[Dragosvr92]

@Bantu, no one said that you have to do it. I Dont care for who doesnt want to manually do it.
There must be someone that would be glad to do it.

All they/you would need to do, is manually update their own style, and see if there are stupid finds, or other errors, and fix them.

[bantu]

All they/you would need to do, is manually update their own style, and see if there are stupid finds, or other errors, and fix them.

This is exactly what we do not want to do as it is a waste of time. Manually updating a style based on prosilver or subsilver2 is pointless, because you can just use the patch file and as a result will only have to resolve some conflicts instead of doing everything manually.

@Bantu, no one said that you have to do it. I Dont care for who doesnt want to manually do it.
There must be someone that would be glad to do it.

The MOD format files and the resulting packages are completely auto-generated. So even if there was someone who would do all the work manually, the development team would have to make sure the result actually makes sense and does not sneak in any security issues or something the like. Then we would have to manually generate packages. So, overall and again a big waste of time.

You are however free to find someone who produces MOD format files manually or based on the files we produce and package and publish them wherever they want.

Also, we have the code changes section http://area51.phpbb.com/code-changes/ now which should be sufficient for most use cases.

[Dragosvr92]

Well, after the autopackage is done, some user could test the istructions and update their style.
They will only remove the double finds, and make sure the replacement thing is right. At least someone from the team may be willing to do so.

I did wonder, why dont you set your automatic comparaion tool to generate MODX Files, instead of just a messy text file?

[RMcGirr83]

It would appear that the updater is not working for styles that use template inherits. EG, I use prosilver_se exclusively and when trying to run the update from 3.0.10 to 3.0.11-RC1 I am hit with this error

The file ./../styles/prosilver_se/template/bbcode.html is missing.

..and of course it's missing, the style uses template inherits.

[t_backoff]

At least someone from the team may be willing to do so.

You keep saying this, but every team member that has posted here has stated that they are not willing to do this (add me to that list ). If you're that concerned about it, feel free to do as Nils suggested and improve the automated tool so he can merge your pull request.

[bantu]

Well, after the autopackage is done, some user could test the istructions and update their style.
They will only remove the double finds, and make sure the replacement thing is right. At least someone from the team may be willing to do so.

Still the same problem: Needs manual packaging. Right now I only have to do "cd build; phing" and the packages are ready. And this is how it should be as manual packaging is error-prone.

I did wonder, why dont you set your automatic comparaion tool to generate MODX Files, instead of just a messy text file?

Whether MOD or MODX is used as the "display format" does not matter. The generated changesets will be the same. This is due to how the changes are generated from the diff.

It would appear that the updater is not working for styles that use template inherits. EG, I use prosilver_se exclusively and when trying to run the update from 3.0.10 to 3.0.11-RC1 I am hit with this error

The file ./../styles/prosilver_se/template/bbcode.html is missing.

..and of course it's missing, the style uses template inherits.

Hmm, this is weird. It should not update prosilver_se at all. Is this error during the file update step or right when you start the update?

[Meis2M]

good news thank U

[RMcGirr83]

Hmm, this is weird. It should not update prosilver_se at all. Is this error during the file update step or right when you start the update?

Right when I first click the update link from the ACP. FYI, I do have prosilver uninstalled from the ACP.

[bantu]

Hmm, this is weird. It should not update prosilver_se at all. Is this error during the file update step or right when you start the update?

Right when I first click the update link from the ACP. FYI, I do have prosilver uninstalled from the ACP.

I guess it should also work without having prosilver installed.

Is

The file ./../styles/prosilver_se/template/bbcode.html is missing.

the full error message or is there anything else? Can you enable DEBUG and DEBUG_EXTRA to see whether there is something else?