Dimitar Petrov
Forum Replies Created
-
Hello,
Our team is still working on the HTTP/3 implementation after we migrated to our new hosting environment. Below you can find our official statement(within the “UPDATE” box):
https://www.siteground.com/blog/quic/
We cannot provide an ETA, but once we are ready with the deployment we will update the blog post and activate the feature.
Best Regards,
Dimitar PetrovIt seems that I misunderstood the case and you already outlined the issue in your second post. I apologize for that.
I have reported the issue to our developers. It will be reviewed and fixed if possible in the next plugin’s releases.
Thank you for your patience and cooperation!
Best Regards,
Dimitar PetrovThank you for the update. Please note that it is not recommended to post login credentials in this public forum.
I replicated the issue and once I deactivated the SiteGround Security plugin, a Fatal Error was encountered, thrown by the theme. You can check the debug log for the exact error. I noticed that the issue was on line 71 in the theme’s(twentytwentytwo) functions.php file. However, it seems that the file is modified and this is causing the issue with the entire application’s dashboard on my end.
I changed the theme on your test site and confirmed that no such issue was encountered. I would recommend checking theme’s modifications further in order to debug the issue.
Best Regards,
Dimitar PetrovThat’s correct!
If you encounter any issues, please post a ticket from your SiteGround User Area and we will be glad to investigate further!
Best Regards,
DimitarHello @gabe9,
Our in-house developed CDN is compatible with the WebP file format and serves such files as intended.
Best Regards,
Dimitar PetrovThank you for the update.
I was able to find the communication in question and investigated the case. The issue should be caused by a php.ini file containing deprecated PHP variables. You should remove that php.ini file located at the application’s root directory and the issue should be resolved.
Best Regards,
Dimitar PetrovHello @mkp1981,
According to the error, the built-in Rest API of the application does not work as expected. The API in question is required by our plugin. Please check the displayed error messages in order to find the possible reasons for the issue.
If your website is hosted on our end, please post a new ticket from your SiteGround User Area and we will be glad to assist. If not, you should check your .htaccess file for any blocking directives, the installed security-related plugins and ensure that the WordPress core along with all plugins and themes are the latest versions.
Best Regards,
Dimitar PetrovHey @cuser2,
Regarding the email-related question I have posted a ticket on your behalf.
I would kindly ask you to manage that communication via our internal ticketing system as this forum is about our SiteGround Optimizer plugin.
Thank you for your cooperation.
Best Regards,
Dimitar PetrovHello @cuser2,
I have reviewed your case, reported in our Reviews section and the ticket that you opened on our end. However, the ticket has remained unanswered as we were not sure what is the exact site that you were having issues with. Please post a new ticket on our end, explain the issues in detail and we will be glad to assist!
Best Regards,
Dimitar PetrovHello @coachtaiters,
I have replicated the issue and confirmed that it is caused by the Defer Render-blocking JavaScript feature of our plugin. It seems that the pop-up JS is not compatible with the async loading of the scripts.
As I can see the Boom plugin scripts are using the following handlers:
et_bloom-custom-js
et_bloom-idle-timer-js
et_bloom-uniform-jsAnd I tried to exclude them from the Defer Render-blocking feature using a filter, but the issue still persists. It seems that even if these scripts are not loaded asynchronously the sequence of the loading of the others are affecting them.
In this case, you should either deactivate the Defer Render-blocking JavaScript feature of our plugin or contact the team of the Boom plugin if they can assist you with the exact scripts that should be excluded from the ‘Defer Render-blocking’ list.
Best Regards,
Dimitar PetrovHello @guaranis,
I was unable to replicate the issue. I would recommend reinstalling SiteGround Optimizer and checking if your WordPress core files are not modified. The returned error is an indication of an issue with the Rest API of the application, used by our plugin.
If you are a SiteGround customer, you can also open a ticket from your User Area so we can investigate the case further.
Best Regards,
Dimitar PetrovHello @flintstoned,
We do not recommend deactivating the internal WordPress Cron Job script. Please note that many of the optimization features of our plugin rely on this script and if it is disabled, the features will not work.
Best Regards,
Dimitar PetrovHello @jej12,
Would you please confirm that your SiteGround Optimizer plugin is the latest version? I have tried to replicate the issue but to no avail. The $this reference mentioned in the error is used in a Class(object) context.
If your website is hosted on SiteGround servers, please open a new ticket on our end so we can investigate the case further. If not, update this thread with the version of the WordPress application, SiteGround Optimizer plugin, and how you trigger the error so we can reproduce the issue.
Best Regards,
Dimitar PetrovHello @mammadz,
This forum section is about the plugin SiteGround Optimizer. Please post a new support ticket from your SiteGround User Area and request the issue to be checked by our team.
Best Regards,
Dimitar PetrovHello @generosus,
Thank you for the feedback.
As mentioned in the quoted forum thread, we are following the trends closely and once we decide, we will implement the compression into the SiteGround Optimizer plugin. I have also informed our developers for your request so they can be aware of the increased interest in the AVIF file format.
Best Regards,
Dimitar Petrov