joaquinferrero

My recommendation is to find a hosting that does support .htaccess files in an Apache environment. The reason is that WordPress uses the mod_rewrite module to modify all requests and route them to index.php. Naturally, using Apache to use this module is not a requirement, but a recommendation, as stated in the readme.html file.

All fine with WordPress v6.7.1 and google-sitemap-generator v4.1.21

Thanks!

Confirmed. Writing to .htaccess stopped.

Plugins installed:

+---------------------------------+----------+-----------+---------+
| name                            | status   | update    | version |
+---------------------------------+----------+-----------+---------+
| easy-paypal-donation            | active   | none      | 1.4.2   |
| tinymce-advanced                | active   | none      | 5.9.2   |
| call-now-button                 | active   | none      | 1.4.10  |
| classic-editor                  | active   | none      | 1.6.4   |
| cmp-coming-soon-maintenance     | active   | none      | 4.1.13  |
| contact-form-7                  | active   | none      | 5.9.8   |
| contact-form-7-simple-recaptcha | active   | none      | 0.1.6   |
| woo-coupon-usage                | active   | none      | 5.15.0  |
| duplicate-page                  | active   | none      | 4.5.4   |
| elementor                       | active   | available | 3.17.0  |
| gdpr-cookie-compliance          | active   | none      | 4.15.2  |
| jetpack                         | active   | none      | 13.7    |
| creame-whatsapp-me              | active   | none      | 5.1.7   |
| liquid-custom-builder           | active   | none      | 1.4.0   |
| liquid-import-export            | inactive | none      | 1.1.0   |
| loco-translate                  | active   | none      | 2.6.11  |
| mce-table-buttons               | active   | none      | 3.3     |
| object-cache-4-everyone         | active   | none      | 2.2     |
| wp-user-avatar                  | active   | none      | 4.15.12 |
| really-simple-captcha           | active   | none      | 2.3     |
| redux-framework                 | active   | none      | 4.4.18  |
| google-site-kit                 | active   | none      | 1.133.0 |
| revslider                       | active   | none      | 6.6.15  |
| updraftplus                     | active   | none      | 1.24.4  |
| woocommerce                     | active   | none      | 9.1.4   |
| woocommerce-paypal-payments     | active   | none      | 2.8.3   |
| woo-redsys-gateway-light        | active   | none      | 6.1.2   |
| wp-sitemap-page                 | active   | none      | 1.9.4   |
| google-sitemap-generator        | inactive | none      | 4.1.21  |
| wordpress-seo                   | active   | available | 23.2    |
| 1and1-subdomain                 | must-use | none      | 1.1.0   |
| object-cache.php                | dropin   | none      |         |
+---------------------------------+----------+-----------+---------+

Themes installed:

+-----------------+----------+--------+---------+
| name            | status   | update | version |
+-----------------+----------+--------+---------+
| medcaline       | active   | none   | 1.0.0   |
| twentytwentytwo | inactive | none   | 1.8     |
+-----------------+----------+--------+---------+

The sitemap.xml file is not generated.
Plugin version 4.1.21. PHP v7.4.30. WordPress 6.6.1

• This reply was modified 7 months, 1 week ago by joaquinferrero.

I can confirm it: the activation of this complement has as a collateral effect the update (access, opening in writing mode, closing) of the file /.htaccess, in each visit to the website, causing a decrease in performance.

[19/ago/2024 11:17:53] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:17:53] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:17:54] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:17:54] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:17:55] IN_MODIFY /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:17:55] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:17:55] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:18:16] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:18:16] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:18:25] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:18:25] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:18:58] IN_MODIFY /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:18:58] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:18:58] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:18:58] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:18:58] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:20:42] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:20:42] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:20:42] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:20:42] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:23:26] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:23:26] * /var/home/fluircentro.es/www/.htaccess is closed
[19/ago/2024 11:23:26] IN_CLOSE_WRITE /var/home/fluircentro.es/www/.htaccess
[19/ago/2024 11:23:26] * /var/home/fluircentro.es/www/.htaccess is closed

The way to mitigate low performance is to remove writing permissions to .htaccess file. There is no bugs in the error.log file in doing so. Obviously, it is not the ideal solution because WordPress requires that said file to have writing permits.

It is very curious. Sometimes the .htaccess file is rewritten in English, and other times in the language of the website.

# BEGIN WordPress
# Las directivas (líneas) entre ?BEGIN WordPress? y ?END WordPress? son
# generadas dinámicamente y solo deberían ser modificadas mediante filtros de WordPress.
# Cualquier cambio en las directivas que hay entre esos marcadores serán sobrescritas.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

# 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.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

No rewriting rules are written in the file, at least apparently we have seen. Only the previous text is shown.

These are the variables defined in the WordPress Options Table:

sm_beta_banner_discarded_count
sm_beta_banner_discarded_on
sm_cpages
sm_hide_auto_update_banner
sm_options
sm_rewrite_done               
sm_show_beta_banner
sm_status
sm_user_consent

• This reply was modified 7 months, 1 week ago by joaquinferrero.

Linux Debian v9
Apache v2.4.25 webserver
Fast-CGI for PHP v7.0, v7.3 and v7.4
Exim4 mailserver
Wordpress v5.7.1 with contact forms:
acumbamail-signup-forms
contact-form-7

4- Adding an add_action() to functions.php, like this thread:
https://www.ads-software.com/support/topic/ehlo-protocol-issue/