thalakus

Hi @kharisblank
thank you for your solution!
Will this be implemented in the next update? Because the text boxes are really standard without a defined border so it should all be contained by Sydney, no?

Hello there,
thanks for the super fast response!
I might have found the reason:
The arrow is just indicating that this is the person to which it’s sent.
And in the Mail header the forwarding might have come due to the contact form 7 that sends one message directly to me and one copy to the customer. Maybe that is the forwarding.

Since it works fine, I think I better don’t try to fix something that’s not broken ??

I thank you very much!!
Have a great weekend!

Appreciate it! Thank you!

is the way via user.ini the best method on a apache server or is there something more reliable? – not having any issues, just like to know the best practice
Thank you very much!

Hi Dragos,
thanks for your feedback! Glad to hear that my page won’t explode :))

So I’m keeping calm and looking forward the fix ??

have a great day!

Thank you very much for your reply!
It’s okay then ??

Hi there,
thank you very much for your response!
Indeed I can’t see it now too. Yesterday it showed the notice but maybe it’s gone now.

So for understanding it better: If something isn’t looged in the firewall log, then it can’t be affected by the ninja firewall?

Now I found out that visiting mydomain/en/wp-json/wp/v2/pages/72/ triggers the error.
This is exactly a page of the guestbook.

So might the error lie here that translatepress can’t deal with emojis?

• This reply was modified 2 years, 9 months ago by thalakus.

Hi Kharis,
yes, basically it occurs on all sydney pages that use siteorigin.

You find it for example here:
https://shop.ur-windschott.de/ueber-uns/

I’ve set up a new environment today on local to test the affect of some other setting
But here it’s the same. If I use the SiteOrigin Page builder for the text, it’s shown anyway with a way larger distance than with Sydney 2.0

Do you need further info?
Best regards!!

The preloader can be disabled without plugin or css in customizer-> misc -> toggle off “enable preloader”

Hello @robert681 I got the same error once:
03.02.2022 16:37:40 PHP Warning: Use of undefined constant php – assumed ‘php’ (this will throw an Error in a future version of PHP) in /wp-content/plugins/wp-2fa/includes/classes/Admin/Views/FirstTimeWizardSteps.php on line 94

It’s no problem for me now, so I prefer not to install the plugin manually but only via the official WordPress-updater because it’s more comfortable ??

Since it’s not urgent, I’m just curious: Will this fix be rolled out the next days officially on your plugin?

Have a great start in the new week ??

@kharisblank Thank you for that!

the system-default-font depends on the default font of the Operation-System (like windows 10) or on what does it depend, which font will be shown?

Thank you very much in advance!

It’s the “Hide-Update” button
It’s provided to hide a localized version of the update

@neuronager try a mail of your domain as recipient for testing.
For example [email protected]