Error when trying to post a comment

Update: I managed to narrow down the problem to the Spam add-on. Uninstalling it fixed the issue but as you can imagine, it created another one. ?

Any ideas on how to fix the add-on issue would be appreciated! ?

Thanks for reporting this!

It looks like you’re experiencing the same issue reported on Github Unable to load the requested language file. We are investigating the issue and hope to have a fix available soon.

Try checking what read permissions the file has, then attempt to give it permission 777. This isn’t safe or definitive, it’s just to determine if it’s a file permission issue.

Sure, here are the steps in English:

To read the write permissions of the file /system/ee/language/spam/stopwords.php and change them to 777:

Read the current file permissions:
You can use the ls -l command to view the permissions of the file:

ls -l /system/ee/language/spam/stopwords.php

This will display output similar to the following, where you can see the current permissions:

-rw-r–r– 1 user group 12345 Apr 18 12:34 /system/ee/language/spam/stopwords.php

Here, the write permissions are represented by the characters -rw-r–r–, where the first group of three characters refers to the permissions of the file owner.

Change the permissions to 777: Use the chmod command to change the permissions to 777: chmod 777 /system/ee/language/spam/stopwords.php

After running this command, the permissions of the file will be changed so that anyone can read, write, and execute the file.

Restore the original permissions: If you want to restore the permissions to their original state after performing necessary tests, you can do so using the following command:

chmod <original_permissions> /system/ee/language/spam/stopwords.php

Replace <original_permissions> with the original permissions of the file that you observed in step 1. For example, if the original permissions were -rw-r–r–, you would use: chmod 644 /system/ee/language/spam/stopwords.php

You can also check your server logs, assuming it’s Apache, and see what’s recorded there. Otherwise, you can try viewing the ExpressionEngine logs.

This issue has been resolved now in ExpressionEngine 7.4.9

Thank you for your article, it is very useful