Sticky: Sticky element is larger than its container error

[jnkconsult (Jean-Marc Strauven)]

Hello,

the last 30 min, I have this error :

Sticky: Sticky element is larger than its container, cannot create sticky. 
Object { 0: div#mainwp-top-header.ui.sticky, length: 1 }
semantic.min.js:11:218076
    error https://adminwp.xxx.be/wp-content/plugins/mainwp/assets/js/semantic-ui/semantic.min.js?ver=4.2.1:11
    checkErrors https://adminwp.xxx.be/wp-content/plugins/mainwp/assets/js/semantic-ui/semantic.min.js?ver=4.2.1:11
    initialize https://adminwp.xxx.be/wp-content/plugins/mainwp/assets/js/semantic-ui/semantic.min.js?ver=4.2.1:11
    sticky https://adminwp.xxx.be/wp-content/plugins/mainwp/assets/js/semantic-ui/semantic.min.js?ver=4.2.1:11
    jQuery 2
    sticky https://adminwp.xxx.be/wp-content/plugins/mainwp/assets/js/semantic-ui/semantic.min.js?ver=4.2.1:11
    <anonyme> https://adminwp.xxx.be/wp-admin/admin.php?page=mainwp_tab:823
    jQuery 13
Sticky: Sticky element is larger than its container, cannot create sticky. 
Object { 0: div#mainwp-top-header.ui.sticky, length: 1 }
semantic.min.js:11:218076

and I can not more click on the homepage button.

extension installed are :

|Advanced Uptime Monitor Extension |5.2.2 |Licence API active |Ok|
|MainWP Domain Monitor Extension |4.0 |Licence API active |Ok|
|MainWP Maintenance Extension |4.1.1 |Licence d’API inactive |Avertissement|
|Analyse de vulnérabilités MainWP |4.1.1 |Licence d’API inactive |Avertissement|
|MainWP WooCommerce Status Extension |4.0.7 |Licence API active ||

[bojan (Bojan Katusic)]

Hi @jnkconsult

Considering this isn’t a widespread issue, it’s likely related to your particular setup.

Could you please try deactivating all WordPress plugins except for MainWP Dashboard and see if that resolves the issue?

[jnkconsult (Jean-Marc Strauven)]

@bojan
Yes I find it…it’s the MainWP Domain Monitor Extension extension.
When I disable it, everything is OK and when I enable it, I have back the error and no click anymore on the button.

What can I do if i will use this exension ?

[bojan (Bojan Katusic)]

Thanks for trying that.

I can’t reproduce the issue. Domain Monitor Extension is not producing any kind of errors.

Please try accessing the Dashboard in other browsers and in Private/Incognito windows without any browser extensions running.

[jnkconsult (Jean-Marc Strauven)]

I do it…start with a other browse (Firefox) in Private mode, disable all the extension outside MainWP Dashboard and MainWP Child.
Try and everything is OK
I enable only the MainWP Domain and I have the error again…

[jnkconsult (Jean-Marc Strauven)]

I don’t know if that canb help you but when I activate this extension, I don’t see the Mainwp-Woocommerce-Status-Extension widget on the homepage…when I disable the extension, I see the widget of Woocommerce Status.

[jnkconsult (Jean-Marc Strauven)]

I see to that I have a WordPress critical error on the MainWP Domain widget :
" Domain Monitor

Domain Monitor extension.

Une erreur critique est survenue sur ce site. Veuillez consulter la boite de réception de l’e-mail d’administration de votre site pour plus d’informations."

I have try to activate the debug mode of WordPress but I don’t see any error on the screen.

[bogdan (Bogdan Rapaić)]

Hi Jean-Marc,

I just sent you a new version of the Domain Monitor extension (pre-release) so you can test and see if it resolves the problem. Can you check it out and let me know how it goes?

[jnkconsult (Jean-Marc Strauven)]

Yes i will it…But I have try something else… I have, direct in the database, remove all the domains from the MainWP Domain Status .be (I have a error with this due your WHOIS server issue). I have only one .com domain and eveything is ok now again… sure that the issue is coming from the domain’s data.

I will now test your new version, first check only with the .com domain and than, I will fill again all my .be domains and see If the issue is back again.

[jnkconsult (Jean-Marc Strauven)]

I have installed your beta version and eveything is back OK but.
I have 9 domains that I check (8 .be with the WHOIS issue and 1.com)…

but on the widget, I have only…one EMPTY ?? (maybe the issue) and the one .com :

[bogdan (Bogdan Rapaić)]

Yes, the problem with .be TLDs is known and it’s caused by invalid response from the corresponding server.
As soon as there is more reliable one, we will update it.