doffine
Forum Replies Created
-
Hi @boaz,
unfortunately the new version 2.2.5 didn’t fix the problem :-(.
No matter if we use the little “X” in the top right of the nag window or if we use the “Hinweis ausblenden” (in German) button – the nag window is back the next time we load the dashboard front page.
Same problem here in several installations…
Forum: Plugins
In reply to: [Timed Content] Auto p tag around [timed-content-server] ShortcodeHi Arno,
perfect – now it works without any additional
ps. Thanks for your quick fix!Forum: Plugins
In reply to: [Timed Content] Auto p tag around [timed-content-server] ShortcodeHello Arno,
well, this is perfect! Thank you for your versed reply… we are looking forward to the update. Until then we just passivated the
pvia additional CSS “display: inline”.Thanks again and many greetings!
Forum: Plugins
In reply to: [Timed Content] Auto p tag around [timed-content-server] ShortcodeHi Arno,
thank you very much for coming back to us.
One way to reproduce the problem is to just use a blank, new WordPress 4.9.8 and set up a new page with the following content…<a href="https://www.wordpress.org">Test</a>[timed-content-server hide="2019-SEP-12 16:00:00 Europe/Berlin"]<a href="https://www.wordpress.org">wordpress.org</a>[/timed-content-server]<a href="https://www.wordpress.org">Test2</a>You will see a
paround all three links. One could guess now that allptags are produced by WordPress p adding automatic. But when you install a plugin like “Toggle wpautop”, “Disable WPautop”, “Remove Wpautop” or “Manage WPAutoP” and disable auto p, theparound first and third link disappears, but not theparound timed-content-link.Forum: Plugins
In reply to: [Compliance by Hu-manity.co] Bug: Cookie expiry “infinity” does not workWe ask ourselves why no one reacts to this clear bug – especially not the developers…?
Ah – perfect, thanks!
I just restored Duplicator Pro backups from last night on both “PHP-Warning-Shops”, re-updated WordPress and WooCommerce to the newest versions. I also let PHP 7.1 be running. And I cannot explain why, but now it all works. No more warnings – although WooCommerce is again 3.3.1 and PHP stayed 7.1.
Hello Vasyl,
we did send you the wp_options database to your e-mail account yesterday, but you dind’t answer so far.
We also have the plugin “Google Analytics for WordPress by MonsterInsights” running. When we disable that the Warning disappears and all seems to be ok again. So you indeed should talk to MonsterInsights about that.
Now the important question – please answer it:
Does that mean, that the “clear indicator that your system role list is corrupted” you state above is not the problem but the other plugin – and our role list is NOT corrupted then?
Then we just would replace the “Google Analytics for WordPress by MonsterInsights” Plugin with another one similar and that’s it.
Thank you a lot in advance for your answer!
Matthias
Same problem on dashboard as above here:
————————————
The first argument should be either a string or an integer in /<PATH>/wp-content/plugins/advanced-access-manager/Application/Core/API.php on line 218Warning: array_key_exists(): The first argument should be either a string or an integer in /<PATH>/wp-content/plugins/advanced-access-manager/Application/Core/API.php on line 218
————————————Other installations of the plugin on the same server with the same WordPress version 4.9.2, the same PHP version 7.1 and the same MySQL Server version 5.5.58 don’t throw this error.
Re-Installing of the plugin doesn’t help. The error comes back after re-installing.Hi pavloborysenko,
why don’t you change this code in your plugin and release a new version?
If we change the code this change will be overwritten by future updates of your plugin.
We think you should take care that your plugin doesn’t cause any Warnings, shouldn’t you?Same problem here – “Jquery(…).backstretch is not a function”. We had to downgrade (but only on some WordPresses) to get it working again. At this moment we have four WordPresses with Maintenance active. Two of them had the problem in v3.5, two not. WordPresses are 4.8 in all four cases.
@danieliser, it fixed our issue, too. Great work, thank you!
@danieliser – we cannot confirm that, but you are right: In our installation we had also click triggers, but since we don’t use other triggers we cannot say if it affects only click triggers. Nice to hear you are already fixing the problem. We’ll stay tuned and look what the next version brings.
We just downgraded Popup Maker to version v1.5.2 again since we cannot do debugging on the back of our customers. v1.5.2 works again.
When I look on your page enchante.website and try the popup I find exactly the same error as we have it here (on your page it is “too much recursion jquery.js:3:11968”). So we simply seem to have a bug in the new plugin version.