php version?
mariadb / mysql version?
Version 6.x.x to 7.x.x

Check your log files for reports for the upgrade attempt. Copy and paste here the relevant lines.

I guess PHP version 7.1.33

mariadb / mysql version: How do I get that out? I have attached a picture to the database.

Version 6.x.x to 7.x.x
I gess the latest 6.x.x zu 7.2.2. I can no longer reconstruct that exactly

This log file shows: 2020-12-15-17-54-27-upgrade-log.html -->>see picture
Is that the right LOG file? I am happy to give you more information. You just have to tell me exactly what is needed

Is the MySQL version wrong? I see in phpinfo the number 5.0.12. See the picture.

I guess the provided infos will help the devs to investigate further.

I hope you have a backup of your database and 6.x.x b2e files.
I would "downgrade" back to the status before the upgrade and wait till the bug is solved. This may take time - and meanwhile your blog will be up and running.

When browsing this forum, you'll see, that you're not the only one suffering with the 6.x to 7.x upgrade.

Unfortunately, I didn't do a backup before the update, which was probably a bigger mistake. So far, the updates have always worked well over the past few years. Now I can only hope that something can still be saved. After the error occurred, I backed up everything to be on the safe side so that the repair attempts would not be destroyed again. Even if it is actually too late now.

@egon
1
.via phpMyAdmin can check the database version > settings

2. if the version is 12735 or higher check https://rogerlovejoy.net/blog/b2evo/database-versions for the relevant b2evo version

3. Download the version for your database, delete all files from your install manually via cpanel or such, keep just your /media directory and /conf/_basic_config.php

4. Run /install and if the database wasn't partly corrupted maybe you'll be back to your old site

What version b2evo exactly did you have?

Do you not keep a backup of the b2evo files as well as the database locally?

How did you try the upgrade? From the b2evo auto or manual ftp?

Version info locations: https://forums.b2evolution.net/b2evo-version-and-database-version#c110829

Point 1 & 2: Via phpMyAdmin I only find the information you see in the last picture. I can't fint something like a version number.
Point 3: What do you mean by "Download the version for your database"?

I would like to apologize for my lack of independence :-(

Point 4:I prefer to wait because I haven't been able to work through points 1-3.

What version b2evo exactly did you have?
I gess the latest 6.x.x (start bevor update) to 7.2.2 (the goal aber update). I can no longer reconstruct that exactly
I used the automatic installer from b2e.

Via FTP I can see that the automatic installer has created a "Backup" folder. There are two files in this folder: db.zip (179kB) and www.zip (12653kB).
Via PleskDesk I see the database size with 8.93MB and 104 tables.

In my post from Dec 15, 2020 18:15 I posted the picture with the error description. What does the error message and the other information mean?
"MySQL error Row size too large"
Is that a critical mistake?

In the broken installation I find:
conf/_application.php

<?php
/**
 * This is b2evolution's application config file.
 *
 * @package conf
 */
if( !defined('EVO_CONFIG_LOADED') ) die( 'Please, do not access this page directly.' );


$app_name = 'b2evolution';
$app_shortname = 'b2evo';

/**
 * The version of the application.
 * Note: This has to be compatible with {@link http://us2.php.net/en/version-compare}.
 * @global string
 */
$app_version = '7.2.2-stable';

/**
 * Release date (ISO)
 * @global string
 */
$app_date = '2020-10-06';

/**
 * Is this b2evolution PRO?
 * If the PRO modules are available some UI elements will be set up differently.
 * This requires the PHP files for the PRO modules (otherwise there will be errors)
 * @global boolean
 */
$app_pro = false;

/**
 * Long version string for checking differences
 */
$app_version_long = $app_version.'-'.$app_date;

/**
 * This is used to check if the database is up to date.
 *
 * This will be incremented by 10 with each change in {@link upgrade_b2evo_tables()}
 * in order to leave space for maintenance releases.
 *
 * {@internal Before changing this in CVS, it should be discussed! }}
 */
$new_db_version = 16170;

/**
 * Minimum PHP version required for b2evolution to function properly. It will contain each module own minimum PHP version as well.
 * @global array
 */
$required_php_version = array( 'application' => '5.6' );

/**
 * Minimum MYSQL version required for b2evolution to function properly. It will contain each module own minimum MYSQL version as well.
 * @global array
 */
$required_mysql_version = array( 'application' => '5.5.3' );

/**
 * Is displayed on the login screen:
 */
$app_footer_text = '<a href="http://b2evolution.net/" title="visit b2evolution\'s website"><strong>b2evolution '.$app_version_long.'</strong></a>
		&ndash;
		<a href="http://b2evolution.net/about/gnu-gpl-license" class="nobr">GPL License</a>';

$copyright_text = '<span class="nobr">&copy;2003-2020 by <a href="http://fplanque.net/">Fran&ccedil;ois</a> <a href="http://fplanque.com/">Planque</a> &amp; <a href="http://b2evolution.net/about/about-us">others</a>.</span>';

/**
 * Do you want to display the help links to online documentation?
 *
 * @global boolean
 */
$online_help_links = true;

/**
 * Modules to load
 *
 * This is most useful when extending evoCore with features beyond what b2evolution does and when those features do not
 * fit nicely into a plugin, mostly when they are too large or too complex.
 *
 * Note: a long term goal is to be able to disable some b2evolution feature sets that would not be needed. This should
 * however only be used for large enough feature sets to make it worth the trouble. NO MICROMANAGING here.
 * Try commenting out the 'collections' module to revert to pretty much just evocore.
 */
$modules = array(
		'_core',
		'collections',  // TODO: installer won't work without this module
		'polls',
		'files',
		'sessions',
		'messaging',
		'maintenance',
		// 'central_antispam',		// will also require $enable_blacklist_server_API = true;
		'menus',
		'templates',
	);
?>

Ok
One and Two

In the image you will see the info on line 6 of page 2 of the table evo_settings..

Your table may have an alternate prefix than b2evo and the page and number line may differ.

Three:
Once you have the database number the next step is to acquire the version of b2evolution that created that database version.
If the database version is 12735 or higher check https://rogerlovejoy.net/blog/b2evo/database-versions for the relevant b2evo version

However looking at your last post I see the b2evo and database are both up-to date

so can just check the database via phpMyAdmin that it confirms the database version is 16170

Here comes the second page:
'evo_settings': db_version 15000
You probably mean this.

I also find: evonet_last_version_checked b2evo b2evolution 6.11.7-stable 2020-05-01

You may have a partial database update as my records shows the the database version for 6.11.7 is 13320 ~ then version 7.0.0 is 15340

15000 was probably a first test for v7 and the update procedure goes through all database versions one at a time.

You could try and download version 7.0.1 but the problem, after going over your posts more carefully, it shows your MySQL version is too low. You say you have 5.0.12 and specs ask for 5.3.3 as a minimum.

Only just noted that as I was looking at the downloads, sorry I didn't notice sooner :(

https://b2evolution.net/downloads/

Maybe all you need to do is update your MySQL and run the install script option domain.xxx/install/

How do I update the MySQL? I only find the update button from PHP 7.1.33 to 8.0.0.

If you are on a shared server you may have to ask your host to do it. If you are ln dedicated server you will have whm as well as cpanel and you should find in under whm

https://www.eukhost.com/kb/how-to-upgrade-mysql-on-cpanel-server/

Dec 23, 2012

cpanel is supports MySQL 5.5
anything lower than 5.1 is EOL
you can upgrade via MySQL Upgrade in whm

https://forums.cpanel.net/threads/update-mysql.312031/

Who's your host?

I have just described the problem to my hoster.

My hoster reported to me: mariadb 10.3.x is running on the server, i.e. mysql 5.7.

Under phpMyAdmin you can try to fix/repair individual tables.

or go to : evo_blogs > blog_sec_ID

You can also change the type from int(11) as your error shows, to int(10 > mine is int(10)

Make sure you export your database before you make any changes.

https://santhinesh.wordpress.com/2013/02/25/what-does-int11-means-in-mysql/

@egon wrote earlier:

I just tried to update from 6 to 7. Unfortunately it didn't work and I got this error message (see the attached picture). Can you help me?

First of all, even if your database is in a partial upgrade state, make a complete back up of it so that in case the upgrade goes even more terribly wrong you still can recover your original data/collections.

What you experienced is a known issue which has bitten some of us. I solved it by manually hacking the database entries for those sites I support (https://github.com/b2evolution/b2evolution/issues/103). However, please read
https://github.com/b2evolution/b2evolution/issues/105#issuecomment-744033217

for an minor hack...er, more elegant solution, which will potentially solve your upgrade issue. Essentially, the argument is that if you (using a plain text editor) comment out (by inserting two(2) double slashes '//' in front of) line 705 of your b2evolution 7.2.2 source file (line 6 in the sample snippet below):
b2evolution-7.2.2/inc/_core/model/db/_upgrade.funcs.php

original
...

 if( in_array( $fieldname_lowered, $existing_key_fields ) )
{
        if( ! empty( $primary_key_fields ) )
        {
                $column_definition .= ', DROP PRIMARY KEY';
                unset( $obsolete_indices['PRIMARY'] );
        }
}
else

modified before your upgrade attempt:
...

 if( in_array( $fieldname_lowered, $existing_key_fields ) )
{
        if( ! empty( $primary_key_fields ) )
        {
                // $column_definition .= ', DROP PRIMARY KEY';
                unset( $obsolete_indices['PRIMARY'] );
        }
}
else

...

your upgrade will succeed, according to Frank Kloeker https://github.com/eumel8.

Good luck!
P.S. Has anyone heard and/or seen the b2evolution developers!? These last two b2evolution releases, 7.1.7 and 7.2.2 have been...hummm, apparently untested, as some rather ugly bugs like this have slipped through.

Maybe I've now found a solution.
But I'm not sure it's a good solution.
My way: I added an element to the database (see picture). Then I manually performed the 7.2.2 update again.
The update worked without errors and the blog starts.

But it shows a mistake.
When I want to write a post, the error shown in the picture. What should i do now?

You're treading on thin ice:) with database changes and of course they may be overwritten with a full update. Did you check the link to b2evo and relevant database version, if yours say 15000 still you are way out of alignment.

A lot of your database values seem off but one at a time:

First i would remove the [/plugins/_shortcodes_plugin.php] to see if that helps, you may have a number of issues as the database seems very different from mine on 7.2.2

Is it time to reinstall everything?
I could then recreate my posts and relink the used files.
My blog consists of 75 posts, 171 slugs, and 175 files. As a user there is only me. It's not very extensive yet and I could rebuild everything. What do you think about this idea? That way I would have a clean installation and the old paths could be kept. Which version has worked particularly well and which would you recommend me?
For the next few years it will not be good if I tread on thin ice. :-(
I thank you for your help. You are very kind to me.

I am not sure if the following question is allowed in this forum: Is b2evolution still the best choice if I'm looking for software with few problems caused by evil people? I only have posts and files that I want to make available to other users. B2evolution gives me the opportunity to see how often my files have been downloded.

Offtopic: @egon wrote earlier:

I am not sure if the following question is allowed in this forum: Is b2evolution still the best choice if I'm looking for software with few problems caused by evil people? I only have posts and files that I want to make available to other users. B2evolution gives me the opportunity to see how often my files have been downloded.

If less is more for you, then take a look @ http://www.zenphoto.org/
The forum is also "small" and response time from devs and others is pretty short.
I have one project running with it: https://www.bikestation.fi/com/
I would have used b2evolution for that - because B2E comes with more tools - but
I decided for Zenphoto because it comes with perfect EXIF, IPTC and XMP handling - which was a must have there.

@egon wrote earlier:

Is it time to reinstall everything?
I could then recreate my posts and relink the used files.
My blog consists of 75 posts, 171 slugs, and 175 files. As a user there is only me. It's not very extensive yet and I could rebuild everything. What do you think about this idea? That way I would have a clean installation and the old paths could be kept. Which version has worked particularly well and which would you recommend me?
For the next few years it will not be good if I tread on thin ice. :-(
I thank you for your help. You are very kind to me.

I am not sure if the following question is allowed in this forum: Is b2evolution still the best choice if I'm looking for software with few problems caused by evil people? I only have posts and files that I want to make available to other users. B2evolution gives me the opportunity to see how often my files have been downloded.

To the first issue yes reinstalling b2evo 7.2.2 would be practical, you could even open the database.sql file and copy the text fro the replica posts.

To the second it would probably be more fitting to discuss other software and your requirements as a separate topic under https://forums.b2evolution.net/miscellaneous/chat-away/