Recent Topics

upgrade 6.9.3 to 6.10.3 problem

Started by on Sep 28, 2018 – Contents updated: Oct 04, 2018

Sep 28, 2018 04:19    

When i tried to upgrade, i got a message that the php-configuration would allow only 1 RAM ..

Ihre PHP-Konfiguration erlaubt es uns lediglich -1 RAM zu verwenden. Das absolute Minimum, das wir benötigen, um b2evolution zu installieren, ist 48M. Bitte kontaktieren Sie Ihren Web-Host oder verwenden Sie einen kompatiblen

i checked with 1&1, it was php 5.6 and it should be at least 80MB RAM.

i changed php version to 7.2. and i got

Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in /myprovider/click-to-help/inc/_core/_class_loader.funcs.php on line 55

Warning: Cannot modify header information - headers already sent by (output started at /myprovider//click-to-help/inc/_core/_class_loader.funcs.php:55) in /myprovider/click-to-help/install/index.php on line 385

Warning: Cannot modify header information - headers already sent by (output started at /myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in /myprovider/click-to-help/install/index.php on line 386

i can't install the upgrade

Sep 28, 2018 12:59

Installed 6.10.3 by manual ftp with no problems and php 5.4.41

Check out the post I linked to before and search for other posts on the issue.

Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in /myprovider/click-to-help/inc/_core/_class_loader.funcs.php on line 55

I had this installing on my local server with php 7.* so please see post #2 on
http://forums.b2evolution.net/using-xampp-on-usb

Sep 28, 2018 13:52

Thanks a lot amoun for spending time & thinking on this.
It seems to be a server problem. the memory limit indeed is set to -1 for the relevant domain.
Am waiting for clarification from 1&1 and will report later

Sep 28, 2018 16:46

No response from 1&1 so far. But setting memory limit higher using a php.ini-file. installation has worked
.. but now i can't log in to the back-office.

i get an

    'Inkorrekten Crumb erhalten! [loginsalt]'-message

i remember having had that also with earlier upgrades and at that timea we had to add/change in _advanced.php the cookie-handling, according to

// When hosting multiple domains (not just subdomains) on a single instance of b2evo,
// you may want to try this:
$cookie_domain = '.'.$_SERVER['HTTP_HOST'];

But in this version the _advanced.php has changed and i wonder if the change still is needed? Or what exactly has to be done ..?

Ahh, I almost forgot: with the incorrect-crumb-message, there come some warnings, as documented below


Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in myprovider/click-to-help/inc/_core/_class_loader.funcs.php on line 55

Deprecated: Function create_function() is deprecated in myprovider/click-to-help/inc/_core/_url.funcs.php on line 817

Deprecated: Function create_function() is deprecated in myprovider/click-to-help/inc/_core/_url.funcs.php on line 818

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 40

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 317

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 318

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 319

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 320

entering back-office for editing ( second level password )


Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in myprovider/click-to-help/inc/_core/_class_loader.funcs.php on line 55

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 317

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 318

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 319

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 320

Warning: Cannot modify header information - headers already sent by (output started at myprovider/click-to-help/inc/_core/_class_loader.funcs.php:55) in myprovider/click-to-help/inc/_core/_template.funcs.php on line 40

Inkorrekten Crumb erhalten! [loginsalt]

Sep 30, 2018 01:33

But in this version the _advanced.php has changed and i wonder if the change still is needed? Or what exactly has to be done ..?

If the change was needed before, it is definitely still needed.

We'll look into PHP 7.2 issues asap.

Sep 30, 2018 13:34

This is because you’re running the upgrade script starting with a database that has already been partially upgraded.

You must restore a clean database backup before you run the upgrade script again.

Sep 30, 2018 20:16

good point, restored database ... brings me to schema version «12320» ( hope this is the right one for 6.9.3.)

A new install-procedure gets stuck at checkpoint 12735 ( see screenshot )

I checked in the database: There are

          postcat_post_ID and     (value 1795)
          postcat_cat_ID -fields   ( value 25)  BUT 
          postcat_order field  IS MISSING

Sep 30, 2018 22:32

Then it means your database restore was not correct.

You are not performing your upgrade on a clean database here. At least, the table T_postcats has not been restored in your case.

If you don't have a clean backup, I recommend installing another older b2evolution DB in parallel, which matches DB version 12735 and copying the missing fields in case of errors like this one. This is 20 times more tedious than restoring a clean backup. So it's only a last resort solution.

In this case you might create postcat_order double NULL and it might allow the script the complete (if you rereun it it will start at 12735 again), IF there are no other discrepancies.

Oct 01, 2018 02:02

DONE!
I am pretty sure, the postcat_order field was not there in version 6.9.3 as i had two backup-files and it was in none.
There were some more issues with custom field names, which we changed in the database ... don't know if they work in future, but the upgrade is done now. Successfully, it says ...
Thanks a lot, Francois!

Oct 01, 2018 02:22

Ok sorry, I answered on a Sunday evening, not sharply focused. There is indeed a bug when you upgrade an older version. Shoot! :/

I am glad you could work it out. We are going to fix the bug! Thanks for reporting and pushing through it!!

Oct 01, 2018 13:50

@ramadama the errors with the -1 memory limit and with PHP 5.2 should only have appeared in b2evo 6.9 but they should not be present in version 6.10.3. Can you confirm? Thanks.

Oct 04, 2018 13:21

I am not sure what to confirm, but i try:

We got told from 1&1 that the setting -1 means unlimited memory. This is how they preset the accounts automatically and normally they get configured later according to the contract conditions - which in our case they had forgotten to do until i asked what -1 meant.

In version 6.10.3 now we see 'unlimited memory' instead of the -1 - but don't know if this is due to changes in b2e or because 1&1 has changed something for our account.

I seem to remember that when we started the upgrade-process, the procedure protested saying not enough memory to run upgrade, and i guess the -1 was not interpreted as 'unlimited'.

Oct 04, 2018 22:45

b2evolution 6.10.3 recognizes -1 as unlimited. b2evolution 6.10.2 did not.

When upgrading to b2evolution 6.10.3, you should not have an error about memory.

This post has 1 feedback awaiting moderation...


Form is loading...

powered by b2evolution free blog software – This forum is powered by b2evolution CMS, a complete engine for your website.