djwilko12

Hi
But this topic is related with the original one. That is why i replied here. After your latest release, it broke our sites. Thanks and hope you can find a solution

Same here… sites turns blank! Please try to solve it. It is affecting many sites we manage. We had to rollback to previous version to make the sites available again

ok, thank you very much

Thank you! I tried. But when i go to the https://www.domainname.com/?p=t

Warning: Use of undefined constant t – assumed ‘t’ (this will throw an Error in a future version of PHP) in /home/customer/www/domainname.com/public_html/wp-content/themes/flatsome-child/functions.php on line 3

i changed the real domain with “domainname”

Thank you very much @jetxpert for your help. That code you provided, what does it do exactly?
Regards!

same here! killed all our sites using this plugin! please fix it ASAP!!

Hello
Were you able to check this?

Thanks for your fast reply.
We are using Flatsome.
After the update it stopped working correctly. So we need to go back to the previous version. Could you please recheck? It broke all our previous configurations.
Waiting your reply.
Thanks

Hola!
La última: 4.2.0
Por favor les pedimos revisen! Es muy importante que el plugin pueda estar actualizado y funcionando correctamente.
Gracias

Gracias, vamos a chequear!

Hello!
I have just sent email. Kindly check. Regards!

Thanks for your reply and glad to know an experience plugin developer as you are is taking care of this plugin. This plugin was always full of flaws. Hope you can start solving them one by one.
Back to the point, since the last update, every automatic update had failures. We get the following (in spanish):

No se pudo recuperar la lista del servidor HTTP debido al siguiente motivo ((Código de error de curl: 18)(Código de estado HTTP: 200).
Vista previa no disponible para este problema

Please try to fix it… all our sites that are still using your plugin are having this problem. We cannot work our Woo catalog with FB anymore
Thanks

Dale muchas gracias. Así podemos agregar esta opción próximamente

Thanks Alexander for your fast reply!
Now i noticed that if i activate the plugin for the network, i have no capabilities to manage each site individually. So what would you recommend?

Now i reply your previous message as i still have some doubts:

1- You say that if i activate the plugin for network, then the settings apply to all sites. So in this case if i disable heartbeat, it will be applied to every subiste and there is not way i could change that just for 1 subsite, right?

And If i activate the plugin only on a subsite, then the settings apply only to it.
So, on subsite A, i would be able to disable heartbeat and on subsite B, i can have it enabled?

Am i correct?

2- I tried activating on subsite and never worked… i understand is a virtual file, but when i visit domain.com/robots.txt i should see what i have set on the plugin’s settings, right? For some reason is not working… Could you please check?
The ides here is to be able to generate virtual robots.txt for each subsite independently.

3- I tried it again and it happened the opposite… when i activaed for the network, it didint allow me to do changes on the update settings.
And when i enable it just for 1 subsite, i was able to do changes on the update settings… which is very odd… should be the opposite, because if this happens, some subsites could have contradictory settings. Kindly check

4- Similar to what i asked on point 1. I would like to know whether each subsite can have independent settings when the plugin is NOT network actviated.

5- I saw that on the upper menu of the plugin, it shows CLEAN CACHE and a “%”. Why is that? We already use a cache plugin. Maybe it could generate some conflicts. Kindly explain how this cache works.

Thanks!

Thanks for your reply!
Here are my comments/questions:

1- Every setting on each subsite is independent from the others subsites, right?
2- I tried customizing the robots.txt file on a subsite, but nothing happened… I think the plugin would have handled the robots.txt file for each subsite independetly, right?
3- I saw the plugin allows to set the plugins updates on a subsite basis… but i think that is not ok, because what happens if i set to atuomatic update on site A, and then i set the opposite on subsite B? There would be a conflict… How to handle that?
4- If i set to disable heartbeat on subsite A, will i be able to allow it on subsite B?
Thanks and hope you could reply each point separately.
Regards