phpBB encountered an error building the container due to an installed extension

[warmweer]

All of your extensions are active, to catch the issue you have to disable ALL of them first.
I'd go to exclude first all of those which aren't in the CDB/validated. I am seeing a bunch of potential culprits there.

Good luck.

Which one?

As 3Di mentioned: disable all of them and then start with enabling the non-validated ones (one by one).
Which ones is up to you to find out (you know where you got them).

[wads24]

All of your extensions are active, to catch the issue you have to disable ALL of them first.
I'd go to exclude first all of those which aren't in the CDB/validated. I am seeing a bunch of potential culprits there.

Good luck.

Which one?

As 3Di mentioned: disable all of them and then start with enabling the non-validated ones (one by one).
Which ones is up to you to find out (you know where you got them).

As I have said I have already disabled all of them and still getting the error.

[kasimi]

• Open board root/phpbb/di/container_builder.php
• Find around line 211

  Code: Select all

  // Don't try to recover if we are in the development environment

• On a new line above, add

  Code: Select all

  throw $e;

Browse to your ACP, you should see the error that's causing the phpBB encountered an error building the container due to an installed extension message to be displayed. Don't forget to undo the edit afterwards.

[wads24]

• Open board root/phpbb/di/container_builder.php
• Find around line 211

  Code: Select all

  // Don't try to recover if we are in the development environment

• On a new line above, add

  Code: Select all

  throw $e;

Browse to your ACP, you should see the error that's causing the phpBB encountered an error building the container due to an installed extension message to be displayed. Don't forget to undo the edit afterwards.

Edit completed.. no other error in admin

Edit undone

[kasimi]

What do you see when you add print_r($e); above that line?

[wads24]

What do you see when you add print_r($e); above that line?

Nothing...

I just see same error after saving a change in admin.

phpBB encountered an error building the container due to an installed extension. For this reason, all extensions have been temporarily disabled. Please try purging your forum cache. All extensions will automatically be re-enabled once the container error is resolved. If this error continues, please visit phpBB.com for support.


Exception:

[david63]

The error message is saying that all your extensions are disabled but the screenshot you posted before is showing them as enabled.

See Knowledge Base - Disabling all extensions at once to disable your extensions and then re-enable them one at a time.

[wads24]

What do you see when you add print_r($e); above that line?

Thank you kasimi. He found an edit I did Drop the admin login box.

He removed the edit that I did and the error went away.

THank you again kasimi !

[RMcGirr83]

Which just goes to prove that one shouldn't install extensions that haven't been validated on here.

[shortmort37]

Thank you kasimi. He found an edit I did Drop the admin login box.

He removed the edit that I did and the error went away.

THank you again kasimi !

I'm having this same problem in my desktop test environment. The link you provide above no longer resolves. Can you clarify what you did to resolve your problem?

[wads24]

Thank you kasimi. He found an edit I did Drop the admin login box.

He removed the edit that I did and the error went away.

THank you again kasimi !

I'm having this same problem in my desktop test environment. The link you provide above no longer resolves. Can you clarify what you did to resolve your problem?

Yes, I had commented out the admin log in on admn/index.php

Code: Select all

// Have they authenticated (again) as an admin for this session?
// if (!isset($user->data['session_admin']) || !$user->data['session_admin'])
// {
//	login_box('', $user->lang['LOGIN_ADMIN_CONFIRM'], $user->lang['LOGIN_ADMIN_SUCCESS'], true, false);
// }

I did this so that I didn't have to log in again under admin link.
I changed back to...

Code: Select all

// Have they authenticated (again) as an admin for this session?
if (!isset($user->data['session_admin']) || !$user->data['session_admin'])
{
	login_box('', $user->lang['LOGIN_ADMIN_CONFIRM'], $user->lang['LOGIN_ADMIN_SUCCESS'], true, false);
}

[shortmort37]

Um... OK. But, why did that manifest as an issue with an installed extension? Were all bets off at that point?

[wads24]

Um... OK. But, why did that manifest as an issue with an installed extension? Were all bets off at that point?

I did both at the same time, and so it didn't have to do with the extension. I just removed that edit and the error went away. I did read also that it may be due to permissions also.

[kasimi]

When commenting out that piece of code, the user session is missing the session_admin flag, causing the page_header() function to be called in some cases, even though in the ACP, the adm_page_header() is expected to always be called. If there happens to be a problem building the container, the adm_page_header() function adds details about the problem to the template variable CONTAINER_EXCEPTION, otherwise it sets it to false. In the template, the CONTAINER_EXCEPTION value is compared strictly to false. However, since page_header() is mistakenly called, that template variable doesn't get set at all and therefore evaluates to null, causing the strict !== false check to pass even though there hasn't been any problem.

TLDR: The error was displayed even though there was no problem with any extension or file permission.

The error message is saying that all your extensions are disabled but the screenshot you posted before is showing them as enabled.

If there's an exception while building the container all extensions are skipped so even if they show as enabled, you can trust the error message that the container was built without them.

[shortmort37]

TLDR: The error was displayed even though there was no problem with any extension or file permission.

I seem to have gotten myself in the same pickle; I've been operating with this complaint for many months, but apparently innocuously. I thought that if I upgraded my desktop test environment from 3.2.1 to 3.2.3, it might disappear, but no such luck.

I have a mod that permits mp4s to play natively as attachments, as well as treat pdfs as images (preparing a thumbnail), but I don't know enough (yet) to write an extension. I've been tracking the changes I've made to 12 files, and I think I've put back the canonical source in an attempt to diagnose - but to no avail.

I created a test environment on my hosting site that manifests the same problem - http://59plymouth.net/59test - and I've disabled all the extensions, and deleted all the data. I've even removed the code from the /ext directory, but the complaint persists - e.g., if I go into Attachment Settings in the ACP and click submit without making a change, I get the error.

I inserted print_r($e); in 59test/phpbb/di/container_builder.php as suggested, but when I repeat the steps that produce the complaint in the ACP, I don't see the print message - just the complaint. Any advice as to how to further diagnose would be much appreciated.

Dan