I had this problem, managed to fix it somehow (don't remember how), attempted to upgrade my xoops, failed, restored back to 2.3 and this issue is back.

No form of image code will work.

I was originally told to edit the xoops/class/module.textsanitizer.php file and then the Frameworks/textsanitizer/plugins/image.php

My old thread is here:
https://xoops.org/modules/newbb/viewtopic.php?forum=28&topic_id=63252

I tried restoring those two files from my back up, still not working.

Would REALLY like to be able to post images again.

I fixed it by manually replacing the files from my back up folder by folder. The cpanel restore wasn't replacing the files for some reason.

After having to restore my site after a failed upgrade, I have this problem again. I can't get any form of image tag to work on my site

I tried restoring the two files mentioned in this thread from my back up but that didn't fix the problem. Cleared my cache/cookies to make sure. I must have done something else to correct this but I can't find any notes on what I did.

I'm using CBB 3.08

I have another thread where I tried to upgrade from 2.3 to 2.4 and encountered fatal errors. After several days with my site down I decided to restore my full back up. I've done this and I can log in to the site and things seem fine, however I can't access admin.php it's just blank. No users can access the site either because I have it turned off for them.

I went through the attempts to turn on debugging to find the error but I think it may already be on due to #3.
I've cleared cache and cookies, tried a different browser from a different computer.

My site has been down since Saturday, getting a little stressed.

When I run checksum.php it still tells me my files are invalid or missing.

A: To turn on debugging try the following things:
=
1. If you can get to admininstration menu, go to Preferences, select 'Main', and find the section on debugging options. Choose "PHP Debugging" CAN'T ACCESS

2. If you can't get to the administration page, but have access to mysql, try the query "UPDATE xoops_config SET conf_value=1 WHERE conf_name = 'debug_mode'". Be sure to make sure "xoops_config" matches the name of the config table in your installation. (NOTE: This does not work with XOOPS 2.2, see 2a) DOESN'T WORK

2a. In XOOPS 2.2, go to your site's root file "recovery.php" and set the debug settings through the interface here DOESN'T EXIST

3. If you can't get to the administration page, and don't want to mess with mysql, but don't mind messing with PHP, then edit the file "include/common.php". Near line 83, change "error_reporting(0);" to "error_reporting(E_ALL);". ALREADY READS THIS WAY

4. If this still doesn't work, your server or hoster may have turned off debugging in "/etc/php.ini" (linux) or "WIN_DIRECTORY/php.ini" (windows). Make sure there is a line in there "display_errors On". I'VE ENABLED DEBUGGING BEFORE SO I DON'T BELIEVE THIS APPLIES

5. If you don't have access to change this file (e.g. on shared hosting), I HAVE ACCESS

Are the files coming back as INVALID because the database upgrade failed and therefore the files and database don't match?

Going to restore my site from back up when I get home tonight and put off upgrading as long as possible I guess.

I do have a back up but if I revert back I will still need to attempt this back up again at some point so I'd rather solve the problem now.

Ok the first files listed as invalid are the files in the root of my install, for example admin.php

Those files were all replaced, at least three times I've tried overwriting them with the new files in the upgrade. I just tried overwriting the admin.php file with the one from the full package....same error on checksum

I wish upgrading wasn't so complicated. I blow my site up every single time I do this :(

Replace them with what? The files don't exist in the upgrade package. Replace them with files from the full package? This is a huge list, which is why I'm thinking I need to replace all files.

Is this correct or do I need to use the full package and replace all files? It seems that way since I'm getting 'invalid' on files that weren't replaced.

Ok I have tons and tons of invalid files or content invalid files.

I thought that for an upgrade I didn't need to replace ALL files, just the ones in the package to go from 2.3 to 2.4?