Stefan Pejcic

Hello,

I apologize for the delayed reply.

It will, of course, be included in the upcoming release in a few days.

I appreciate your suggestion.

Hello,

Thanks for the information.

I already found that page in your docs before reaching out, and whitelisted all IPs that are used by your domains.

Google SiteKit works without problems and shows all data from the associated GoogleAnalytics account.

I created a simple php script that does curl to all those domains and that works, here you can see the IP from which I am connecting, http status codes for each curl request and the code used: https://password.rs/en/p/9wnb34zxujk

But in your plugin it is reporting that curl error.

How Is this marked resolved??

yes @qtwrk that Is exactly what i mean.

Hello, seems like a same issue https://www.ads-software.com/support/topic/esi-block-is-cached-even-with-public-and-0-set/

Can you please also confirm if crawler is enabled in your case? And if disabled, ESI block is working as expected?

Hopefully it should point the litespeed support team in the right direction, as I reported the issue 7 days ago and still no solution..

On the subdomain I enabled crawler option as well and now on that subdomain the esi block is also cached.. seems like the litespeed crawler option does not respect the esi block settings

Can you please also confirm if this is the case? I gave the steps to reproduce the issue in the original post and provided an export file with the entire litespeed profile settings via the mentioned ticket.

Hello,

It looks like there might be a firewall or rate-limiting by nginx on those api endpoints, as curl from the same server but using another IP works as expected.

• from the main server IP that is shared for majority of cpanel accounts *(shared ip):

[xxxxxx@s30 ~]$ curl --interface 185.119.XX.X0 https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US

^C

• from the same server with another IP dedicated to a single cpanel account:

[xxxxxx@s30 ~]$ curl --interface 185.119.XX.X5 https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US

{"offers":[{"response":"upgrade","download":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2.zip","locale":"en_US","packages":{"full":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2.zip","no_content":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2-no-content.zip","new_bundled":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2-new-bundled.zip","partial":false,"rollback":false},"current":"6.3.2","version":"6.3.2","php_version":"7.0.0","mysql_version":"5.0","new_bundled":"6.1","partial_version":false},{"response":"autoupdate","download":"https:\/\/downloads.www.ads-software.com

Hello again, just published an update that resolves both issues, please update the plugin and let me know if it works for you too.

Thank you once again for reporting it. Cheers!

Hello,

Thank you for bringing it to my attention. I will attempt to replicate the issue and get?back to you as soon as I have a workaround.

Thanks for the response, I did, just wanted to also bring it to your attention.

Thank you for your time.

Hello,

Not right now, but I’m working on adding this feature. I will keep you updated.

Thank you for the review.

updated and works as expected, thank you ????

screenshot

Hello,

The entire error is that from the screenshot: https://pastebin.com/yJv9NpWd

I’ve temporarily disabled all other plugins except this one, still the same, even the tastewp demo instance on PHP 7.4 with WP 6.2.2 shows the same error: https://tastewp.com/create/NMS/7.4/6.2.2/button-group/twentytwentythree?ni=true

To reproduce the error:

1. Add a Button Group block
2. Set link for the first button, exmaple https//google.com and set to open in new tab
3. leave second button to #
4. save and reload the edit page.

Pozdrav Vladane,

This plugin has nothing to do with the debug.log file – as the plugin name suggests error_log File Viewer is intended to work only for the error_log file.

And because on most shared hosting platforms the error_log file is not publically accessible (nor should it be), the plugin has a function that when the download button is pressed, it makes a copy of the error_log file to error_log.txt and allows the user to download that file on demand.

So there is no need to check the WP_DEBUG_LOG path and the file error_log.txt is created on demand – when the button is pressed to download it, and afterward gets deleted for security.

Sorry if the plugin is not doing exactly what you need (download debug_log file), but feel free to fork the plugin and modify it as per your needs to use the debug.log instead. Feel free to contact me if you need any help. ??

Cheers!

• This reply was modified 1 year, 9 months ago by Stefan Pejcic.

It’s also important to note that the API key must have at least view & search permissions set: