What is the exact URL of the page where you get this error. Also,your screenshot is incomplete and it doesn't help. We need complete screenshots to,see the context.

This is the link I'll get after clicking edit a blogpost:

http://www.npo-consulting.net/blogs/admin.php?ctrl=items&action=edit&p=347&blog=8&redirect_to=%2Fblogs%2Fadmin.php%3Fblog%3D8%26ctrl%3Dcoll_settings%26tab%3Ddashboard%26show_statuses%255B%255D%3Dpublished%26show_statuses%255B%255D%3Dcommunity%26show_statuses%255B%255D%3Dprotected%26show_statuses%255B%255D%3Dreview%26show_statuses%255B%255D%3Dprivate%26show_statuses%255B%255D%3Ddraft%26show_statuses%255B%255D%3Ddeprecated%26show_statuses%255B%255D%3Dredirected%26type%255B%255D%3Dmeta%26user_perm%3Dmoderate%26orderby%3Ddatemodified%26comments%3D5%26status%3Ddraft%26show_past%3D1%26show_future%3D1%26posts%3D5%23item_347

Following the screenshots

@fplanque wrote earlier:

What is the exact URL of the page where you get this error. Also,your screenshot is incomplete and it doesn't help. We need complete screenshots to,see the context.

Upgrading from b2evolution 6.8.2 to 6.8.5:

This is what I get in remote(hosted) and local virtual machine environments, both MySQL 5.x.x and MariaDB 10.x.x, versions:
mysql Ver 14.14 Distrib 5.6.30, for debian-linux-gnu (x86_64) using EditLine wrapper
and
mysql Ver 15.1 Distrib 10.0.28-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

[Sun Jan 22 01:34:46.607874 2017] [:error] [pid 2568] [client 192.168.x.yz:60504] b2evolution error: Requested File from T_files without ID! in /var/www/domain_com/b2evolution/inc/_core/model/dataobjects/_dataobjectcache.class.php at line 542 / REQUEST_URI: /b2evolution/index.php / HTTP_REFERER: -

The upgrade procedure in those three instances tested -- 1 remote and 2 local VMs -- apparently finishes successfully but error occurs both, before and after database normalization, immediately after requesting Front Page.

Best Professional Regards.

@saunders @nanahuatl can you guys please turn on debug mode so that the error screen will show at what line the error happens as well as the call stack. Please post a screenshot of the call stack (functions called immediately before the error happens). This will help us isolate the error. Thanks.

@fplanque wrote earlier:

@saunders @nanahuatl can you guys please turn on debug mode ..

PHP5.x
In _advanced.php set:
$debug = 1 ;

Subsequently

Backtrace:

debug_die( "Requested File from T_files without ID!" )
File: /var/www/domain_com/b2evolution/inc/_core/model/dataobjects/_dataobjectcache.class.php on line 542
DataObjectCache->get_by_ID( 0, false )
File: /var/www/domain_com/b2evolution/skins_site/_site_body_header.inc.php on line 21
require( "/var/www/domain_com/b2evolution/skins_site/_site_body_header.inc.php" )
File: /var/www/domain_com/b2evolution/inc/skins/_skin.funcs.php on line 2039
siteskin_include( "_site_body_header.inc.php" )
File: /var/www/domain_com/b2evolution/skins/bootstrap_blog_skin/index.main.php on line 36
require( "/var/www/domain_com/b2evolution/skins/bootstrap_blog_skin/index.main.php" )
File: /var/www/domain_com/b2evolution/inc/_blog_main.inc.php on line 890
require( "/var/www/domain_com/b2evolution/inc/_blog_main.inc.php" )
File: /var/www/domain_com/b2evolution/index.php on line 60

Ignored last: 1

Fatal error: Uncaught Error: Class 'xmlrpc_client' not found in /var/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php:99 Stack trace

#0 /var/www/domain_com/b2evolution/inc/_core/_misc.funcs.php(241): b2evonet_get_updates() #1 [internal function]: shutdown() #2 {main} thrown in /var
/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php on line 99

Intalled PHP7 from Debian unstable repos attempting zero in, but I could not even log in as I had this extra issue:

After php7:

Log in to your account

{"salts":[""]}

Fatal error: Uncaught Error: Class 'xmlrpc_client' not found in /var/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php:99 Stack trace

#0 /var/www/domain_com/b2evolution/inc/_core/_misc.funcs.php(241): b2evonet_get_updates() #1 [internal function]: shutdown() #2 {main} thrown in /var
/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php on line 99

Reason I installed PHP7 is because at least another b2evolution instance where I built PHP7 had no issues when gradually upgraded to b2evolution, i.e., delta 6.8.2 to 6.8.3 => 6.8.3 to 6.8.4 => 6.8.4 to 6.8.5

The above PHP5.x (from Debian stable Jessie repositories) and PHP7.x (this last from Debian unstable Sid repositories) can only be upgraded up to 6.8.4 and successfully display the Front Page; notwithstanding both upon upgrade to 6.8.5 the database is modified -- apparently successfully -- but the Front Page throws those initial errors.

@fplanque

sry I am not a developer. I have been using b2e for about 12 years. I gathered some experience, but I am not a developer. And the blog, which shows the bug is a production blog. And as I remember, you advised in the manual not to use debug mode for production blogs.

So I will degrade back to 6.8.3.

Could you please hand the link to the github fix of the security bug? This way I could make the version 6.5.3 save.
I will wait to a really stable version.

Please could you update the demo each time you release a so called stable version? This way I could test it on the demo server before upgrading my blogs.

Thanks in advance
Will

@nanahuatl Thank you.

@saunders You can totally use debug mode on production if you use the recommended method explained here: http://b2evolution.net/man/debugging (which has been available for about 5 years now)

I recommend you do NOT downgrade. We will have those bugs fixed asap.

The bug occurs on every page being edited and saved again - independent whether I choose save&edit or save, whether I choose public, member, etc.pp.
The first screenshot shows the page with debug message.

After saving the error page does not show any debug message! (Second screenshot)

Why shouldn't I restore the backup und fix only the security bug?

Thanks, Will

PS: I checked by installing a new version of 6.8.5 (not upgrading), only taking the old media folder, the basic_conf from config, the EU Consent Plugin and some files eg. notepad.php in the root. The bug persists.
So the bug may be caused by the database?

Why shouldn't I restore the backup und fix only the security bug?

Because there are 5 security bugs at least in 6.8.3 and it's fairly hard to patch them all by hand. The patches are pretty complex.

Here is the fix for the T_files error above. Please apply this to 6.8.5 and let us know if it helps: https://github.com/b2evolution/b2evolution/commit/f82e3bd6ea28d221d3d6dc31d046b0e98bb9b2be

@fplanque and the developers who fixed that bug!

Thanks; that fix works fine!

Regards, Will

@nanahuatl you have reported another bug in this thread

Fatal error: Uncaught Error: Class 'xmlrpc_client' not found in /var/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php:99 Stack trace

#0 /var/www/domain_com/b2evolution/inc/_core/_misc.funcs.php(241): b2evonet_get_updates() #1 [internal function]: shutdown() #2 {main} thrown in /var
/www/domain_com/b2evolution/inc/dashboard/model/_dashboard.funcs.php on line 99

We cannot reproduce this on PHP7. Would you care to investigate a little more in which exact scenario this happens?
(Are you sure your b2evo files are all uploaded correctly?)

@nanahuatl Here's our test:

I had also this problem, with
t_files(don't know why here leter Ti is changet to evonet), after update to latest version. I aplyied the fix mentioned above, it works, but now I don't have a site logo, and when try to acces the settings for logo, I get this error
https://s30.postimg.org/wjdjayiap/scrren.jpg
https://s28.postimg.org/qv26ga5n1/1111.jpg
, and also, when I try to add a site logo to the email messages, it gives the same error
https://s30.postimg.org/9s4gojx9d/screen2.jpg
https://s28.postimg.org/v5gubvaq5/2222.jpg
. And Finally when accesing the private message window it gives another error
https://s30.postimg.org/wuuznpyqp/screen3.jpg
full text of last error:

SELECT ts.tsta_thread_ID AS thr_ID,

                GROUP_CONCAT(DISTINCT ur.user_login

 ORDER BY ur.user_login SEPARATOR ', ') AS thr_read,

                GROUP_CONCAT(DISTINCT uu.user_login

 ORDER BY uu.user_login SEPARATOR ', ') AS thr_unread,

                GROUP_CONCAT(DISTINCT ul.user_login

 ORDER BY ul.user_login SEPARATOR ', ') AS thr_left

  FROM evo_messaging__threadstatus ts

  LEFT OUTER JOIN evo_messaging__threadstatus tsr

                  ON ts.tsta_thread_ID = tsr.tsta_thread_ID

   AND tsr.tsta_first_unread_msg_ID IS NULL

   AND tsr.tsta_thread_leave_msg_ID IS NULL

  LEFT OUTER JOIN evo_users ur

                  ON tsr.tsta_user_ID = ur.user_ID

   AND ur.user_ID <> 1

  LEFT OUTER JOIN evo_messaging__threadstatus tsu

                  ON ts.tsta_thread_ID = tsu.tsta_thread_ID

   AND tsu.tsta_first_unread_msg_ID IS NOT NULL

   AND tsu.tsta_thread_leave_msg_ID IS NULL

  LEFT OUTER JOIN evo_users uu

                  ON tsu.tsta_user_ID = uu.user_ID

   AND uu.user_ID <> 1

  LEFT OUTER JOIN evo_messaging__threadstatus tsl

                  ON ts.tsta_thread_ID = tsl.tsta_thread_ID

   AND tsl.tsta_thread_leave_msg_ID IS NOT NULL

  LEFT OUTER JOIN evo_users ul

                  ON tsl.tsta_user_ID = ul.user_ID

   AND ul.user_ID <> 1

 WHERE ts.tsta_thread_ID = 2263

   AND (ts.tsta_user_ID =1)

 GROUP BY ts.tsta_thread_ID

The error with

T_files

There is no solution for this, at the moment?

@spellbound will be fixed in next release.

This should be fixed in v6.8.6.

Yes, it is fixed in new release. Thank you!

@nanahuatl Thanks for your feeback.