Page 2 of 3

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 1:53 am
by PHenry1025
My website host is one of the larger website hosts with thousands of phpBB users so this issue is affecting a lot of people.

My question is if your website host does not use WHM cpanel, how do you change php.ini to increase the execution time?

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 2:22 am
by mp777
PHenry1025 wrote:
Sat Jan 14, 2017 6:50 pm
Release 3.2 totally screwed up my forum.

I had to revert to 3.1.10 with heavy technical support from my hosting company.

Also if the Automatic Update from 3.1.10 to 3.2 is not usable, why is listed as an update option.

I strongly recommend not attempting this update until 3.2 is modified. All the advise given from the experts in these forums do not seem to work.

This is just a technically poor update.
same problem. i was fine using automatic updates up until this point. then the 3.2 update screwed everything up.

nothing pisses me off more than having to update this software. this the achilles' heel of phpbb.

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 2:29 am
by mp777
KevC wrote:
Sat Jan 14, 2017 8:38 pm

As for the original point, as I posted elsewhere earlier, many problems are actually from people who are not using proper diligence before updating. Several have not checked the server requirements, have not checked if their style is compatible or have not checked if their extensions are compatible.
or maybe the real problem is PHPBB IS POORLY DESIGNED AND THE PROGRAMMERS DON'T WANT TO ADMIT IT?

i doesn't take a genius to figure out that this software is poorly designed. but it seems that once pride is on the line, function takes a backseat to covering your ass.

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 8:54 am
by koraldon
KevC wrote:
Sat Jan 14, 2017 8:38 pm
As for the original point, as I posted elsewhere earlier, many problems are actually from people who are not using proper diligence before updating. Several have not checked the server requirements, have not checked if their style is compatible or have not checked if their extensions are compatible. They often haven't made a backup or tested the update on a backup first before doing it on their real board. This means that they're diving straight in and updating a live, working board and get more frustrated when it's offline for more than a few hours while a solution is found.
Why doesn't the phpbb check itself for the requirements? It can easily also warn the user prior to updating that a backup is recommended...
The manual update is primitive and incapable while the automatic update seems broken...
Automatic update need to be fixed and improved - not discarded...

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:05 am
by david63
koraldon wrote:
Sun Jan 15, 2017 8:54 am
The manual update is primitive and incapable
Then update it and submit it for consideration.
koraldon wrote:
Sun Jan 15, 2017 8:54 am
Automatic update need to be fixed and improved - not discarded.
Why should it not be discarded? The only reason for the Auto update is historic from the days of phpBB 3.0 where there were MODs that changed the core code. As one of the philosophies of phpBB 3.1/3.2 is that the core code should not be changed then that requirement has gone.

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:21 am
by koraldon
There should be an easy automatic way to update phpbb.
I would love to learn programming, maybe after the kids get to school :)

And any manual upload cannot incorporate checks for requirements or warnings to users...

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:21 am
by RMcGirr83
david63 wrote:
Sun Jan 15, 2017 9:05 am
As one of the philosophies of phpBB 3.1/3.2 is that the core code should not be changed then that requirement has gone.
Yet users still do it. Imagine the uproar if someone overwrote their board and lost all the edits they had done (without backing up the files first I might add).

One can never please 100% of the people 100% of the time.

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:31 am
by noth
mp777 wrote:
Sun Jan 15, 2017 2:22 am

same problem. i was fine using automatic updates up until this point. then the 3.2 update screwed everything up.

nothing pisses me off more than having to update this software. this the achilles' heel of phpbb.
well I must agree with mp777

all I see is "The installer detected a timeout
The installer has detected a timeout, you may try to refresh the page, which may lead to data corruption. We suggest that you either increase your timeout settings or try to use the CLI."

despite refreshing I never get any further

and in all previous automatic updates this never happened once

updating should be made easy, not a punishment exercise

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:53 am
by koraldon
For reference area51 old discussion on new installer for 3.3 - https://area51.phpbb.com/phpBB/viewtopi ... 81&t=48951

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 9:55 am
by noth
3.3 ? really? what about 3.4? there is no word on that? :shock:

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 12:00 pm
by KevC
mp777 wrote:
Sun Jan 15, 2017 2:29 am
KevC wrote:
Sat Jan 14, 2017 8:38 pm

As for the original point, as I posted elsewhere earlier, many problems are actually from people who are not using proper diligence before updating. Several have not checked the server requirements, have not checked if their style is compatible or have not checked if their extensions are compatible.
or maybe the real problem is PHPBB IS POORLY DESIGNED AND THE PROGRAMMERS DON'T WANT TO ADMIT IT?

i doesn't take a genius to figure out that this software is poorly designed. but it seems that once pride is on the line, function takes a backseat to covering your ass.
I'm not saying the software is perfect, none is from any maker anywhere. I'm saying people should take sensible steps with something important like a forum before they dive in and update.

The first 3 steps on the update guide page say
-Ensure that your server meets the requirements
-Make a backup of the original files
-Make a backup of the database

You're obviously very angry about it so why not be proactive for the next version on Area51.

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 1:36 pm
by koraldon
noth wrote:
Sun Jan 15, 2017 9:55 am
3.3 ? really? what about 3.4? there is no word on that? :shock:
Frankly I would be happy with 3.3. having only this single feature (built-in updates to core + install/updates of extensions & styles*) and released shortly.
It is correct to not add features to mainteance releases (i.e. 3.2.x)

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 2:49 pm
by lurttinen
PHenry1025 wrote:
Sun Jan 15, 2017 1:53 am
My question is if your website host does not use WHM cpanel, how do you change php.ini to increase the execution time?
I open the php.ini in a text editor. Edit what i want, save it and reload it to take effect.

In some case i might make a quick change to .htaccess to test something and it overwrites php.ini setting.

You don't need a cpanel or any other control panel to maintain a server. :)

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 4:16 pm
by warmweer
lurttinen wrote:
Sun Jan 15, 2017 2:49 pm
PHenry1025 wrote:
Sun Jan 15, 2017 1:53 am
My question is if your website host does not use WHM cpanel, how do you change php.ini to increase the execution time?
I open the php.ini in a text editor. Edit what i want, save it and reload it to take effect.
I have a feeling this answer is nonsensical to PHenry1025, since he could edit his php.ini if he had access to it.
lurttinen wrote:
Sun Jan 15, 2017 2:49 pm
In some case i might make a quick change to .htaccess to test something and it overwrites php.ini setting.
This, on the other hand is a useful answer.

But just in case, I strongly advise PHenry2025 to backup everything he has access to before trying to edit anything like php.ini or .htaccess (in fact just always backup before changing anything).

Re: 3.2 Should be Pulled

Posted: Sun Jan 15, 2017 5:15 pm
by mp777
KevC wrote:
Sun Jan 15, 2017 12:00 pm
mp777 wrote:
Sun Jan 15, 2017 2:29 am
KevC wrote:
Sat Jan 14, 2017 8:38 pm

As for the original point, as I posted elsewhere earlier, many problems are actually from people who are not using proper diligence before updating. Several have not checked the server requirements, have not checked if their style is compatible or have not checked if their extensions are compatible.
or maybe the real problem is PHPBB IS POORLY DESIGNED AND THE PROGRAMMERS DON'T WANT TO ADMIT IT?

i doesn't take a genius to figure out that this software is poorly designed. but it seems that once pride is on the line, function takes a backseat to covering your ass.
I'm not saying the software is perfect, none is from any maker anywhere. I'm saying people should take sensible steps with something important like a forum before they dive in and update.

The first 3 steps on the update guide page say
-Ensure that your server meets the requirements
-Make a backup of the original files
-Make a backup of the database

You're obviously very angry about it so why not be proactive for the next version on Area51.
this amounts to saying: sorry you're not a lawyer, but you should quit your job as a doctor to study for the bar exam so you can help us in the legal profession even though you already have a job.

i try to reasonably educate myself regarding phpbb. but there are obvious limitations. i started from scratch like a lot of people and have learned a lot about editing my forum, but you're asking wayyyyyy too much w/o even realizing it. and the directions are ALL CONVOLUTED. it's already mentioned that there are many ways to update, all with conflicting directions! this is called BAD DESIGN.