Community @ The Turning Gate

Something has changed on your side.  Your host has changed something with your PHP setup, and done so with a broken configuration.  As Rod suggested, see our document about module errors.

If you're trying to send yourself the code to set up 2FA, but not receiving anything, another way of finding the link that would have been sent to you is to look at the most-recent log file under backlight/logs/admin/.  All outgoing links related to logins, such as password resets and unlocking links are logged there, for the purpose of getting back into your system if emails aren't getting through.

Please see my email.

Can you email me one of the images that fails to upload?  Also, on the upload screen what does it say for the maximum size of images allowed?  This varies based on your server configuration.

The code above the one you've quoted should include another reference to APHPLugins, so that those few lines look like this:

if (defined('BACKLIGHT_HOOK')) {
	require_once(realpath(BACKLIGHT_HOOK).'/modules/module-designer/application/helpers/APHPlugins.php');
}

class PHPlugins extends APHPlugins

Is that the case?  If not can you add in:

if (defined('BACKLIGHT_HOOK')) {
	require_once(realpath(BACKLIGHT_HOOK).'/modules/module-designer/application/helpers/APHPlugins.php');
}

above the class PHPlugins line and see if that fixes it.

You may need to re-export your theme after making that change.

Hi Oliver, running multiple wordpress sites on the same server as Backlight is an edge case, so not something that we're likely to address within Backlight.

I can think of a couple of options:

1. Export to the one site, and copy over the themes to your other WP site as needed
2. Run a common themes directory symlinked from one or more of your WP installations. (this would require command-line access, which I can help with if you have it).

All good, Kurt?  The other explanation for a missing 'language_code' would be if Backlight 2 hadn't been upgraded to the latest version.

There should be a reasonable fix for that.  Bluehost needs to know that the from address is valid before it sets the 'from' properly in the outgoing email.  To fix this, create an email inbox for that email address in the Bluehost control panel.  You don't actually need to use Bluehost to handle the email, so that address would still operate as it already does.  It's just that Bluehost will know that that is an address you've set up.

Hi Kurt, unfortunately 500 errors alone don't provide any information on the underlying problem.  Can you provide me with FTP access via Email so that I can look into this?

We haven't tested it against 7.3.  If you find something amiss then we'll look into it and fix it.

Hi Kristoffer, since installing Backlight, your host has changed the version of PHP, making it incompatible with what you're running.
I'll need to make some changes to the Cart to make it compatible again.  If you could provide me with FTP access via email then that will help me check that the changes will work.

We have not yet updated the .htaccess file.  It's in our working code and will come along with the next maintenance release.

The only functional change is that it will fix the issue that you've found - that of inadvertently failing to allow real resource files at the top level.
Those lines are currently redundant, so commenting them out as you have done will be fine.

For a technical explanation, there are checks in the .htaccess that will allow real files to be loaded if they exist.  Unfortunately, those checks only apply until the next rule that has an L between the square brackets.  So it's a logic error in our .htaccess file that prevents those resource files from being loaded if they're actual files on disk.