2.1.6 - Database error in MySQL

[Volker S]

When attempting to edit a thread using the forum's "Edit" function, a database error occurs.

This error does not occur when editing a thread using the "Quick Edit" function.

[GL700Wing]

When attempting to edit a thread using the forum's "Edit" function, a database error occurs.

This error does not occur when editing a thread using the "Quick Edit" function.

Just letting you know that if you are using the Automatic Attachment Rotation (and Resize) mod and it turns out this error is caused by a bug in the mod I won't be able to fix it until the end of August as I am away on holidays until then.

[GL700Wing]

When attempting to edit a thread using the forum's "Edit" function, a database error occurs.

I can't find an "Edit" function for the standard theme - are you referring to the "Modify" function or are you using a different theme?

This error does not occur when editing a thread using the "Quick Edit" function.

I've just checked on my SMF 2.1.6 forum and I don't get any errors when editing a message using either the "Modify" or the "Quick Edit" functions when the Automatic Attachment Rotation (and Resize) mod is installed and I have tested editing messages with/without image attachments (and also messages with non-image attachments).

Are you able to provide more information about this error and also what other mods do you have installed?

[Volker S]

Yes, it is the Modify function that causes this database error.
Unfortunately, I also got an additional server error 500 when I tried to insert an image using your autorotation (I have logged the errors, but would prefer to switch to the forum for your addon "autorotation").
Since I have backups of 2.1.4 and 2.1.5 from the forum, I wanted to continue with the 2.1.5 backup.
When I tried to access the forum, I got a version conflict (see image). I would have clarified what to do next.
Currently, I have 2.1.6 running again.
I thought you were still on vacation.

[GL700Wing]

Yes, it is the Modify function that causes this database error.
Unfortunately, I also got an additional server error 500 when I tried to insert an image using your autorotation (I have logged the errors, but would prefer to switch to the forum for your addon "autorotation").

This issue is not happening on my test SMF 2.1.6 forum (which was upgraded from SMF 1.1.5) and error 500 is a server-side issue (ie, from your web hosting service) - what version of PHP are you using?

I'll send you the login details for an account on my test forum so that you can confirm for yourself that the mod is working and not generating any errors.

Since I have backups of 2.1.4 and 2.1.5 from the forum, I wanted to continue with the 2.1.5 backup.
When I tried to access the forum, I got a version conflict (see image). I would have clarified what to do next.
Currently, I have 2.1.6 running again.

Not sure how you go about resolving that issue - did you uninstall the SMF 2.1.6 update or just replace the files?

I thought you were still on vacation.

I am (until the end of August) and even though I don't have access to my development environment I will still check and respond to messages if/when I can.

[Volker S]

...and error 500 is a server-side issue (ie, from your web hosting service) - what version of PHP are you using?

I know that error 500 is a server error, but it could also be caused by files (.htaccess or an unsupported program version) located on the server.
The PHP version is 8.3.22 (I recently upgraded from 8.2) – which version do you have?

I'll send you the login details for an account on my test forum so that you can confirm for yourself that the mod is working and not generating any errors.

I believe you that your add-on works. It has worked for me so far.

Not sure how you go about resolving that issue - did you uninstall the SMF 2.1.6 update or just replace the files?

I created a new directory on the server and uploaded the backup via FTP – so I didn't uninstall the update.

Now I have to sleep - perhaps I read you tomorrow again. Thanks for your time.

[Aleksi "Lex" Kilpinen]

Usually, your server would log an explanation to go with that HTTP 500 error in the server's own error log. Have you checked what it says there? Could be a clue worth looking into.

[Volker S]

Thanks for the tip. I think I raised the PHP version too high. I have a lot of PHP warnings from Dokuwiki in the error logs and...

...here is the warning when attempting to attach an image

Code Select Expand

[Thu Jul 03 22:57:07.441951 2025] [fcgid:warn] [pid 4180249:tid 4180249] [client 2001:9e8:489f:6900:9a61:986f:83bc:2fcc:0] mod_fcgid: stderr: PHP Fatal error:  Redefinition of parameter $jpegQuality in /var/www/vhosts/hosting113784.a2f57.netcup.net/httpdocs/joomla/sm_forum/Sources/Subs-Graphics.php on line 415, referer: https://www.jollauser.de/index.php?action=post;topic=403.0;last_msg=2029

[GL700Wing]

The PHP version is 8.3.22 (I recently upgraded from 8.2) – which version do you have?

Normally 8.1 but I've confirmed that this issue does not occur with either 8.2 or 8.3.

[Volker S]

I changed setting the PHP version to 8.1.
That didn't work.

...and now I'm really going to sleep.

[Oldiesmann]

Changing the PHP version won't fix the error. That's a problem with the database query - mysql doesn't know what "thumb" is referring to. Can you attach a copy of Sources/Post.php, or at least the query that appears on lines 697-716? There's no "thumb" in the query in a default installation - just "id_thumb" (used to determine the name of the thumbnail image for any attachments)

[Volker S]

I think it's great that you're trying to help me. I had already secretly prepared myself to reinstall 2.1.5 (which is still database compatible with 2.1.6), but I think I'll have to go back to 2.1.4, as everything still worked there.

Some basic information about how it all started:
The forum (2.1.4) and all add-ons were working. Then there was an update for the add-on "Automatic Attachment Rotation (and Resize)" to 6.26, which I installed, and a day later the forum update to 2.1.5 came out. When I tried to install it, I got errors with ManageAitachments.php and Subs-Attachments.php. That sounded like files from the "Automatic Rotation" add-on, so I looked at the package manager table. It said version 6.24, that it was not installed and could therefore only be deleted. So something must have gone really wrong at some point, because I had actually already installed 6.26.

The developer then got involved (he didn't know about the "uninstallability" of his mod) and, due to the two errors during the installation attempt from 2.1.4 to 2.1.5, recommended that I first uninstall his add-on and then perform the forum update.
I then told him that I was not offered the option to uninstall. (Read more -> here)
He then recommended installing 2.1.5 and then updating the mod. I think that the errors were ultimately implemented because I couldn't uninstall the installed "Autorotation 6.24." It's best to take a look at the link "Read more."

...I'm not going to rush into anything. Thanks again in advance to those who want to help me.

[Volker S]

@Oldiesmann
The error is now displayed in line 734 (see image). It is located in the field variable declaration. This error occurs when I try to start the large editor (Modify). Quick Edit works.
I can't post the code here (not even a section of it) because then I'll run into the forum firewall.
Here's a link to the complete post.php -> Link

[Aleksi "Lex" Kilpinen]

@SleePy Not being able to paste code snippets seems like an issue we should perhaps look at.

[Volker S]

So, I restored SMF to 2.1.4 (with the corresponding database). Unfortunately, resetting to 2.1.5 did not help. The same errors were still there.

Now that everything is working again, I can take my time and manually restore the lost forum posts.

However, the system is not error-free. The modul "autorotation is marked as "cannot be uninstalled" again, and the wrong version is listed there. I will continue the discussion about "Autorotation" in the forum from that Modul once the developer is back from vacation.

PS: I can't post a Picture (.jpg) with the funktion "Click or drag files here..."

Here is the picture:

[Volker S]

The error I received, which was displayed in a very narrow column, began with HTML code. I did not copy everything—at some point below the HTML code, the binary files of the image appeared.

Code Select Expand

Zurück_zu_2-1-4.jpg <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta http-equiv="X-UA-Compatible" content="IE=Edge"><meta name="robots" content="noindex,nofollow"><meta name="viewport" content="width=device-width,initial-scale=1"><style>*{box-sizing:border-box;margin:0;padding:0}html{line-height:1.15;-webkit-text-size-adjust:100%;color:#313131;font-family:system-ui,-apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Helvetica Neue,Arial,Noto Sans,sans-serif,Apple Color Emoji,Segoe UI Emoji,Segoe UI Symbol,Noto Color Emoji}body{display:flex;flex-direction:column;height:100vh;min-height:100vh}.main-content{margin:8rem auto;max-width:60rem;padding-left:1.5rem}@media (width <= 720px){.main-content{margin-top:4rem}}.h2{font-size:1.5rem;font-weight:500;line-height:2.25rem}@media (width <= 720px)


[GL700Wing]

However, the system is not error-free. The modul "autorotation is marked as "cannot be uninstalled" again, and the wrong version is listed there. I will continue the discussion about "Autorotation" in the forum from that Modul once the developer is back from vacation.

This problem is not caused by the 'Automatic Attachment Rotation (and Resize)' (AARR) mod - it's caused by an issue within the database for the Package Manager.

You might need to use the 'Fix Packages' tool to change the installation status of the AARR mod - download the tool here.

[shawnb61]

I've made a few attempts to reproduce the issue following the steps above.  v6.24 of AARR is no longer downloadable, but in all my attempts, starting with SMF2.1.4 & AARR 6.25, I've been able to install/deinstall v6.25, v6.26, & even do the 'upgrade' of v6.25 to 6.26, deinstall 6.26, patch SMF to 2.1.6, reinstall AARR 6.26, & have everything work OK.

You are correct that AARR must be deinstalled before the 2.1.5 is applied.  There are conflicts there.  But an AARR deinstall/SMF patch/AARR reinstall works OK.

GL700Wing is correct that, if you really are on AARR v6.24 and cannot deinstall, fix_packages should help.

But none of this explains the broken 'thumb' query.  AARR does in fact add 'thumb' to the query - that's where that came from - but properly installed there is no error.  Somewhere along the line, that query got mangled.  I suspect that due to some install/deinstall glitch, 'thumb' is now duplicated in the query erroneously.  And because the code is mangled, I strongly doubt 6.24 will deinstall properly.

Not sure what.  Cannot duplicate it.  The more important question is what to do next.

Two possibilities...

#1 = Lite, & #2 = Big Bang.  Both options start from your current 2.1.4/6.24.

#1: Lite, a piece at a time.
- Use fix_packages.php to let pacman know AARR v6.24 is actually installed.  This should give you the deinstall button for AARR 6.24.
- Attempt to deinstall AARR 6.24.  You may get errors, I'm pretty sure Post.php will have errors (due to the mangled query).  Note which files.
- Deinstall AARR anyway.
- Whatever files had deinstall issues, copy fresh source over from the 2.1.4 upgrade package.  So you KNOW it's proper 2.1.4.
- Patch to 2.1.5 & 2.1.6.
- Install AARR 6.26.

The risk with #1 the Lite option is if other packages have updated any files that you just broke that other mod. 

To address that risk, it may help to step thru all your other mods in Package Manager and do a 'List Files', so you are aware in advance of any potential conflicts.  If you see some, deinstall that mod, too, & reinstall after you're on 2.1.6.  Another option is to just deinstall everything first.

#2: Big Bang, refresh the code
- Copy *all* SMF files over from the 2.1.4 upgrade package.
- Use fix_package to remove all hooks & flag all mods as de-installed.
- You are now at vanilla 2.1.4...
- Patch to 2.1.5 & 2.1.6.
- Install AARR 6.26.
- Re-install all your other mods.

We should all do a code refresh once in a while.  It's a good thing.  Like changing your sheets...

The downside of this option is that any manually entered tweaks are lost.  But nobody should be doing those anyway.

If #1 crashes & burns, #2 is the fallback plan.

Before you start, read the entire post above two more times.

[Volker S]

- Use fix_packages.php to let pacman know AARR v6.24 is actually installed.  This should give you the deinstall button for AARR 6.24.

Re #1
Does it matter which version of AARR is actually installed?

I'm pretty sure that this information didn't change when I installed AARR version 6.26.
Even when I updated to 6.25, this version information didn't change.
By restoring the backup, I can't say for sure whether it's still 6.25 or already 6.26.

But none of this explains the broken 'thumb' query.  AARR does in fact add 'thumb' to the query - that's where that came from - but properly installed there is no error.  Somewhere along the line, that query got mangled.  I suspect that due to some install/deinstall glitch, 'thumb' is now duplicated in the query erroneously.  And because the code is mangled, I strongly doubt 6.24 will deinstall properly.

By restoring the backup, these errors no longer occur. Everything appears to be functioning properly.

Thank you very much for your help—it is by no means a given.

[shawnb61]

Yes, it matters, because the deinstall will only work properly for the installed version.

fix_packages may offer a clue.

[Volker S]

All right, I'll report what fix_packages shows me and won't do anything for now if it's not the 6.24 that it shows me in the package manager.
I think I'll get to it next week.
Have a nice weekend...

[shawnb61]

If 6.26 & 6.25 were installed, they should be in the /Packages folder.

If not, they may display properly by copying them to the folder.

[Volker S]

They are not included in this restore. However, I suspect that 6.25 was installed.
I will probably have to look at the jump marks (hooks) of the individual patches from 6.24, 6.25, and 6.26 in the corresponding files to figure it out. But first, let's see what fix_packes says. I can still do that now.
Judging by the images, it appears that 6.26 is indeed installed.

Here is the result of fix_packages (see images):

[Volker S]

According to hook (if I understand correctly), I have AARR v2.26 installed.
The patch for 2.26 states the following in "install-smf21-214.xml":
Since I cannot insert code here, I will summarize it briefly. In the file "Subs-Attachments.php," the variable $fs should be appended.
And that's right: in my file "Subs-Attachement.php", this variable is appended at the end of line 1373 in the variable declaration of 'href'.

[shawnb61]

I'd just copy the 6.25 over to /Packages

[Volker S]

According to the images I posted, 6.25 has been uninstalled and, based on my assumptions, AARR 2.26 has been installed. Here is the image with the attached variable from 2.26.

[GL700Wing]

v6.24 of AARR is no longer downloadable

Attached ...

I'm pretty sure that this information didn't change when I installed AARR version 6.26.
Even when I updated to 6.25, this version information didn't change.
By restoring the backup, I can't say for sure whether it's still 6.25 or already 6.26.

As per the following image the version number changes with each release.
You cannot view this attachment.

Judging by the images, it appears that 6.26 is indeed installed.

AARR 6.26 is not shown on either image - the latest version shown is 6.25 (and it's not compatible with SMF 2.1.5 or later).

[Volker S]

Please take a look at my screenshots. Fix_packages shows me that AARR 6.25 is uninstalled, and according to fix_packages, AARR is not installed at all. When I go to my package manager, version 6.24 is listed as deletable only—so it's not installed either.
And I believe that 6.26 is installed (because of the hook, which I may of course be misinterpreting).

But I have to go now—I'll continue next week.

[GL700Wing]

Please take a look at my screenshots. Fix_packages shows me that AARR 6.25 is uninstalled, and according to fix_packages, AARR is not installed at all. When I go to my package manager, version 6.24 is listed as deletable only—so it's not installed either.

Agreed.

And I believe that 6.26 is installed (because of the hook, which I may of course be misinterpreting).

This is what I disagree with (and I can't see an image showing hooks)  ...

[Volker S]

I've now copied 6.25 and 6.26 into the package folder. Convinced? 
But I really have to go now.

(I guess I misinterpreted the hooks. I thought that when the developers write their code into the original file via XML, that's a hook. But I haven't looked into it yet.)

[shawnb61]

Whichever one deinstalls clean at this point!

[GL700Wing]

I've now copied 6.25 and 6.26 into the package folder. Convinced? 

Sure - but I don't understand why you had removed them because doing so prevents you from uninstalling those versions. 

Also, if you are manually moving mod files in/out of the Packages directory/folder it makes it really difficult for those who are trying to help and support you understand and make sense of the issues you are reporting and the screenshots/reports you are sharing.

Also, when a later version of a mod has been installed the only options you will see for the earlier versions are to list the files and delete the mod.

(I guess I misinterpreted the hooks. I thought that when the developers write their code into the original file via XML, that's a hook. But I haven't looked into it yet.)

Hooks are blocks of code in a custom script file that can be called from the default SMF script files by a mod without the need to actually modify the default files.  Although some mods can be implemented entirely using hooks this is not possible for the AARR mod - it uses a combination of hooks and code edits.

[Volker S]

I also don't understand why installed packages disappear on their own. It really wasn't me, or maybe I've been sleepwalking lately.
Something else:
I just got home, uninstalled AARR 6.26, and declined the question about deleting the package because I wanted to reinstall it later.
Then I installed SMF_2-1-5, followed by SMF_2-1-6 (and reinstalled the current database associated with SMF_2-1-6). Now I wanted to install AARR 6.26, but according to the package manager, it is already installed. This surprises me.

(SMF_2-1-5 is in the package manager three times again, but I am familiar with this error by now).

Thank you to everyone who has posted here.

[GL700Wing]

Then I installed SMF_2-1-5, followed by SMF_2-1-6 (and reinstalled the current database associated with SMF_2-1-6). Now I wanted to install AARR 6.26, but according to the package manager, it is already installed. This surprises me.

I think the process of restoring/reinstalling a database backup after you've already installed 2.1.6 is what's causing you to inadvertently end up with Package Manager issues - try using Fix_Packages to correct the status of the relevant/affected packages.

[Volker S]

I'll show you the status after uninstalling AARR 6.26, updating SMF 2-1-5, updating SMF 2-1-6, and restoring the latest database so that all posts are available in the forum again (see image SMF - Current status.jpg).
Since I hadn't reinstalled AARR (you suspect that it's due to the restored database), I wanted to uninstall AARR 6.26 and then reinstall it.
None of the files passed the uninstallation test (image: Uninstall attempt_AARR.jpg). However, I can work with AARR in the forum.
Should I set it to installed using packages-fix, even though it is installed via the package manager?

€dit:
The image of installed modules from fix_packages tells me that AARR 6.26 was installed on July 3, which was definitely before I updated the forum software and uninstalled AARR. I only did that yesterday evening.

[GL700Wing]

Fix_Packages can only show you the current database information for the Package Manager so this is what was in the database backup you restored (ie, that AARR was installed on 3 July) and when you restored the database you overwrote more recent information (ie, that AARR was installed yesterday).

However, I can work with AARR in the forum.
Should I set it to installed using packages-fix, even though it is installed via the package manager?

Yes.

[Volker S]

Nothing happens because AARR is present on both sides of fix_packages. On the uninstalled and installed sides.
I tried anyway to check the AARR 6.26 module on the uninstalled side and then use "Marked install selected" to move it exclusively to the installed side. Unfortunately, this did not change anything.

Edit: I set the duplicate version that was also in the installed window to uninstalled. The problem remains—I cannot uninstall the AARR 6.26 package—all files fail the test.
As long as both versions (6.26) appear in both the installed and uninstalled windows, something is wrong.

(ie, that AARR was installed yesterday).

I only uninstalled it yesterday (didn't install it) – that came with the database restoration. That's why it says that I installed it on July 3.

[Volker S]

I took a look at my table. There (smf_log_packages), your module 6.26 appears four times but is only installed once (your module is the gray lines). Can you make sense of that?

The time for the installed version is also correct -> 1751566773 translates to Thursday, July 3rd 2025, 20:19:33 (GMT +2)

My mistake—the normal function attachment is installed—as also available here in the forum. So AARR is definitely not installed—only the old table shows that. Then everything is correct, and if fix_packages does not work, I will have to delete the line in the table? Sorry for the back and forth.
However, I am happy to wait for your advice.

[shawnb61]

I'll show you the status after uninstalling AARR 6.26, updating SMF 2-1-5, updating SMF 2-1-6, and restoring the latest database so that all posts are available in the forum again (see image SMF - Current status.jpg).

I think part of the problem is here - that restoring the database is restoring the log_packages table, and bringing the table contents out of sync with the installation state of the packages & the contents of the /Packages folder.  If you're going to do that, you will need to use fix_packages to fix it.

log_packages keeps the install state, and it's also a historical log...  That's why there are multiple entries in there, there's been a bunch of installs & deinstalls. 

I haven't looked at the code, but I suspect:
- The one with the highest installation timestamp (& id_install) for that exact filename (sometimes it detects dupes & renames them...) is the main one.
- I suspect that both fix_packages & the package manager will exclude entries from display depending on the install state & whether the file exists in the /Packages folder.  Because you can neither install nor deinstall them without the file...

So I think you can really confuse the tools if the physical files are out of sync with log_packages, or log_packages has conflicting info, e.g., if an older one is flagged as installed.  And we are seeing that here.

I also don't understand why installed packages disappear on their own. It really wasn't me, or maybe I've been sleepwalking lately.

We have seen similar in the past when a host's security settings are high... Files disappear.  It might be worth asking your host if any files have been flagged for quarantine or removal via any security mechanism.  These sometimes show up in your apache log.


What I would do...  I'd go back to this, to keep all current posts:

I'll show you the status after uninstalling AARR 6.26, updating SMF 2-1-5, updating SMF 2-1-6, and restoring the latest database so that all posts are available in the forum again (see image SMF - Current status.jpg).

HOWEVER...  I'd delete the AARR 6.26 package.  Also, to be safe, I'd delete all references to it in the log_packages table and /Packages folder.  So you don't see it anywhere: not in the package manager, not in fix_packages & not in the /Packages folder. 

So everything agrees it's uninstalled:  the actual source code, the /Packages folder, and the log.

When your DB is current, and everything looks clean, reinstall AARR 6.26.

[Volker S]

The smf_2-1-5 is also listed (at least) twice. Once as installed and once as not installed. Once by Volker (id=1) and once by the system? (id=0).
Is it better to leave it unchanged?

[shawnb61]

The smf_2-1-5 is also listed (at least) twice. Once as installed and once as not installed. Once by Volker (id=1) and once by the system? (id=0).
Is it better to leave it unchanged?

If it ain't broke, don't fix it!

[Volker S]

Finally
I've cleared everything up.

I had to install AARR 6.26 as an emulation of smf_2-1-5, but that's just cosmetic (ARR isn't approved for smf_2-1-6 yet).


Sorry for taking up your time...

[GL700Wing]

I had to install AARR 6.26 as an emulation of smf_2-1-5, but that's just cosmetic (ARR isn't approved for smf_2-1-6 yet).

FYI : The latest release of version 6.26 of the Automatic Attachment Rotation (and Resize) mod was updated on 27 June to support SMF 2.1.6.