lvnt

Unfortunately that answer will make me remove W3TC

ahah no regrets tho

Hi,

Fyi without any mods I see the same warning. I started seeing the same warning after upgrading from 8.8.1 to v8.8.2
I had to downgrade until Jetpack 8.7.1 for them to go away again.

Hi I was getting the same error when I tried to connect LSCWP with a Redis.
Maybe it’s something about the write permission for wp-config.php
When I added the permission “write” 640 to-> 660 the info error disappeared

define( 'WP_CACHE', true ) ; finally got succesfully added to wp-config.php and info error vanished

Do you think this could be the problem and the soulution?

I’d thought maybe dividing jobs into two parts would help the webpage load smoother, somehow idk. I will do as your suggestion I’ll leave Flying Images alone to do its job.
Thank you for your awesome plugin and for checking the source codes.

What do yo read when you check your page’s source code? ctrl+U on any webpage
They should be like https://cdn.jsdelivr.net/wp/themes/twentytwenty/1.1/style.css

Install Site Health plugin, change to development mode and try again when ‘only’ commonWP is activated. That way you’ll have an idea where to start. Normally plugin should have worked just fine

• This reply was modified 4 years, 10 months ago by lvnt.

It is Native Lazyload from Goggle

Hi @gijo Obviously we can’t use both at the same time ?? it wasn’t what I meant though

* Flying Images is active(All functions are ON except only lazy-loading is turned off)
* Second(other) plugin is used for lazy loading

If you may check the code pls, only placeholder loads from Statically, but website photos are still served from the server disk
src="https://cdn.statically.io/img/mydomain.com/wp-content/plugins/native-lazyload/assets/images/placeholder.svg"
data-src="https://mydomain.com/wp-content/uploads/sites/2/2017/02/Ajams-Real-41-1200x600.jpg"

Rest of the code is here

• This reply was modified 4 years, 10 months ago by lvnt.
• This reply was modified 4 years, 10 months ago by Steven Stern (sterndata).

Hey!
Short story, crackers in Turkey are not crowded groups and they are mostly enthusiastic under 20 yr old youngsters. And they very oftenly use 3rd party codes, which modern servers can easy protect themselves automatically. Hence you’d mostly get no more harm than some extra server traffic load but nothing serious at all. I know because I run my own server and have the same kind of international attacks, including those which come from Turkey as well.

Let’s also put in case that I’m sure most attacks(if there were any) may be coming to your server via international attacks where ‘zombie computers’ are used, because most people here only relies on windows and standard security softwares.

I mean non-sofisticated attacks and zombie computers don’t deserve getting blocked.. or do they?

I hope you will reconsider your block settings considering these facts

Regards

Thanks for quick reply..

Your plugin does what I want for a multisite install. Since I am not a software developer to compare its code with latest versions of WordPress, I wanted to ask if it was still safe to have it.
But since you follow user questions closely and reply very quickly and assure that it works I will install it more comfortably.

King Regards

I think I have the same issue. When I turned on the debug option in wp-config.php I saw this error. I get this same error no matter if the plugin active or inactive (could be an issue to do with the wp multisite install, too idk)

Would you kindly take a look into this situation please?
Could it be so because my website has a different setting than your plugin expects? Where does the plugin stores its data which it has to flush?

Could be irrelevant though, but as I searched online I’ve read an article about some other plugin that its developer was mentioning ob_flush() is not a good option(whatever that means :/ )

Below is the exact error line;

Notice: ob_end_flush(): failed to delete and flush buffer. No buffer to delete or flush in /wp-content/plugins/http-https-remover/http-https-remover.php on line 54

Beside that, plugin has an option to exlude spesific pages/posts. Whenever you use Finale..Woocommerce plugin, exclude that post. That might solve your problem as well.

For once I thought what I would try if same happened to my webpage…

I think Cache Enabler works with jpeg and png alike files. Maybe, if you try SVG images inside your Finale..Woocommerce.. plugin. Because SVG has different structure than a picture file’s structure

Can this be a temporary solution to work with both plugins side by side ..while keeping the benefits of both plugins

Try again now

layoutControls: {
	posterImage: 'https://cl.ly/psyc/download/Valkyrie-poster-player.jpg',
},

• This reply was modified 5 years, 10 months ago by lvnt.

@rustybrisco+1 I think there was a way to add full screen with an edit to javascript. Can someone find a way for this?

• This reply was modified 5 years, 10 months ago by lvnt.

i. I might me wrong here. Hopefully it helps. Try changing Andrew’s solution to this …‘Dancing Script’, cursive !important;

ii. But since you’re trying to do many things at once maybe a plugin is actually what you need in this situation. Dealing with codes doesn’t seem like a fast solution in this situation. Install and if possible, try to observe what’s changed among your themes CSS and functions files. So that you can both solve your problem and learn where to look next time you need another solution.

I’m not sure advising to install a plugin is a correct approach on a support forum, but it’s what I do in general. Installling&observing the changes mostly saved me even more hours, than looking for an answer.