yellowfellow333

Yes, 16.0.2 is fine until the fix is out ??

+1 here.
Massive HTTP 500 & 401 within Elementor so I can’t work. Even WordPress Critical Error messages. Deactivated Yoast and everything was fine again. Hope, there has been no damage done to the database. Rollbacks would cause some work. Plugin update with fix would be best.

Thank you for your quick help.
The dropdown is quite annoying on a big multilanguage site (polylang) but it worked.
Homepage now less than half the code and very good SEO results.

I want to add one point here:
Have real trouble with more than one theme with this menu.

I LOVE the dashboard widgets suite – but in some themes when I activate this plugin, the dashboard widgets suite menue overwrites the main menue irreversible. Only thing that helps is DEactivating DWS and that’s really not, what I want.

Short description:
Of course the list widget is deactivated (in those cases only ‘system info’ is activated) and the main menue is checked as such (DWS is not). Nevertheless that happens (and yes, cleaned cache and so on and the entire site runs very well and error-free).

So the only possible answer is that the list widget is NOT entirely deactivated when it’s deactivated. I would be SO happy, if you could/would fix that.

Best regards

@tillkruess Thank you for these 2 solutions!
Used the manual method to get done already but will check out your 2 asap, too.

I still think, Elementor should deliver that functionality by itself – at least within the Pro version. Until that it’s another page builder downside.

Best regards

You’re welcome. I really like your Plugin and use it on many projects. Only issues with 1&1 so far…

If I can help, just write me!

Has been fixed due to official language update ??

@wfalaa very happy to hear that!
Give that request +1

Just actually I have a project where I’d need exactly this feature:
There are some custom user roles and the one that will work from the backend mostly is slightly below admin and really should see the widget information.

Best would be the widget information without the possibility of accessing the WF settings. That would really be a benefit!

Thanks and best regards

@andreas W.
Super, passt… muss an der Uhrzeit gelegen haben…
Natürlich kann es in der Testumgebung nicht funktionieren, wenn diese nicht HTTPS ist – sonst k?me es ja zu mixed content.

W?re nur sch?n, wenn zudem an Ort und Stelle ein genereller Hinweis analog zu Deinem Post hier stehen würde.

In der Testumgebung wurde auch ein definitiv korrekter Login-Versuch für eine Testzahlung verweigert. Gehe aber mal davon aus, dass dies aus gleichem Grunde geschah und werde live unter HTTPS nochmal testen.

Danke für die superschnelle Antwort!

Hello and thanks a lot for the really quick response (didn’t mention: I love your plugin).

I know about warnings and debug state. Was also wondering why they came from out of nowhere.

Maybe it wasn’t your plugin at all…
Next day the whole website was down (incl. SFTP connection).
Finally it turned out, that the domain lost its IP on the provider side. Fixed that with a workaround until it’s fixed on provider side and tested again: no warnings at all (also running PHP 7.1.10). (Y)

So thank you again and best regards!