[Resolved] update from December 19th - issue with a 500 Internal Server Error

Background of the issue:
Hi,

Earlier, I had an issue with a 500 Internal Server Error. I had to change the file permissions for the .htaccess file to 444 to prevent it from modifying the redirects from:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteRule ^en/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^pl/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^ro/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^uk/wp-login.php /en/wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /en/index.php [L]

# END WordPress

to:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /en/
RewriteRule ^index.php$ - [L]
RewriteRule ^en/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^pl/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^ro/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^uk/wp-login.php /en/wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /en/index.php [L]

# END WordPress
I contacted B2B King because this issue occurred at the same time I was installing both your plugin and theirs. They told me it was interesting because they have many websites using WPML and their plugin, and they haven't heard of such an error. However, I sent them links to your forum discussing this issue, and they provided me with the following code:

add_filter('b2bking_flush_permalinks','__return_false');

I added it, and everything worked fine until today when I installed your update from December 19th, and the problem returned despite the active code from B2B King.

I had to restore the .htaccess file and set the file permissions to 444 again — it's really annoying.

How can I fix this?

Symptoms:
I encountered a 500 Internal Server Error. After installing the update from December 19th, the problem returned despite the active code from B2B King. I had to restore the .htaccess file and set the file permissions to 444 again.

Questions:
How can I fix the 500 Internal Server Error after the update?
Why did the problem return despite the active code from B2B King?