ivandzh

Hello @pinoooo,

The Advanced XSS Protection header addition feature is now being activated via separate PHP function which applies it directly through the application. As a result, no changes to the .htaccess file are being made.

Best regards,
Ivan Dzhangozov

Hello,

I tested the reported contact page through two mobile devices and with different browsers, while temporarily enabling all magnification and optimization features of the plugin, but I could not replicate the described issue.

Can you confirm if there are some specific settings related to the Forminator plugin or other parts of the application which have been changed in order to eliminate the problem? If so, is it possible to temporarily set them in their previous state, as that would help us to investigate the case further?

Best regards,
Ivan Dzhangozov

Hello @devfirst.

The returned 405 error indicates that the specified request was recognized by the server, but the server itself has rejected the method used for the accessed resource.

In order to verify if this is what’s causing the problem, is it possible to provide us with the name of the affected script?

Including any errors reported by the Site Health tool would also be useful, as long as they do not contain sensitive information.

Best regards,
Ivan Dzhangozov

Yes, in this case each activity log will remain available for 4 days after its creation, only then it will be deleted.

In case no specific value is provided, the plugin will use its default value of 12 days. If you decide to use the filter, you can type any value in the range between 1 and 12.

Best regards,
Ivan Dzhangozov

Thank you for the update.

We are glad that the issue has been resolved.

Thank you for the update.

We would recommend opening a ticket through your SiteGround account and provide us with the name of the affected website. This way we can perform further investigation of the issue in greater detail.

Meanwhile, we remain available if you need further assistance regarding another website.

Hello Iain,

The file-based caching feature of the plugin includes several settings which may affect the overall amount of used CPU resources, depending on the content that is being processed. This includes all internal requests made by active plugins and templates.

In case you want to keep the feature enabled, we would suggest to first try deactivating only its user-specific cache generation and content preheating options after which compare the results. If the website you are experiencing problems with is hosted on our servers, we also recommend getting in touch with our support staff by submitting a ticket through our ticketing system.

Best regards,
Ivan Dzhangozov

Hello,

Having the combined CSS marked as render-blocking is completely normal, especially if there is another file in the theme reported as one. In case you enable the feature in order to reduce the number of requests made by your website, it will process the full theme data even though not all code is used on the specific page.

The best course of action would be to compare the results provided by the two reports and decide which settings are the most suitable for the currently used theme.

Hello @jansportw,

It appears that the restrictions are placed by your current hosting provider.

We recommend getting in touch with them in order to verify if the block can be removed.

Best regards,
Ivan Dzhangozov