budy74
Forum Replies Created
-
Same here with Pro Version 4.4.6, after the update the plugin does not post anymore.
I downgraded to 4.4.3 and it works perfectly… hope developers will fix this!!Same here:
Attempt to read property “ID” on int in […]/plugins/events-manager/em-events.php on line 292PHP Version 8.1.19
Can you please fix this annoying warning?
thanks,
Davide.Sorry guys, I was out of office last week.
I installed the update and I tried to deactivate and reactivate the plugin without any problem. So I think problem is solved for me.
I found another point in your code where the get_users() function is called without parameter causing a potential out of memory error in large users database.
The file is …/admin/class-bp-toolkit-admin.php:874 I don’t know if this could be the @haymondoooo problem.
Hope this helps :))
Thanks @bouncingsprout
The memory issue happened just after clicking the “Activate plugin” link on admin page. Wp returned an error saying it can’t activate the plugin because of system errors. Below that message PHP Fatal Error was reported:
Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 20480 bytes) in […]/wp-includes/meta.php on line 1185
Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 20480 bytes) in […]/wp-includes/plugin.php on line 511
Now I’m testing the plugin functionalities on the front end so if I encounter another problem of this kind I’ll let you know.
Hi, in my case it was enough, but it’s just a temp solution to test the plugin. Future release will overwrite script modifications.
I’m not the plugin developer so you have to wait their answer for your specific problem.I’m sure @bouncingsprout will make you know what’s best to solve your problem (assuming the problem is the same).
Sorry if I answer just now but I wanted to debug this problem deeply since it’s not the first time it happens in our site.
In fact, in my case, as I suspected, the problem is the number of users already registered on the site (about 50k). I discovered that if the get_users() function is called without specifying any restrictions (for example specifying only the fields that are needed, such as the user ID in this case) WordPress (rightly) gives an out-of-memory error.
For now I’ve bypassed the problem by changing the instruction
$users = get_users();
in
$users = get_users(array(‘fields’=>array(‘ID’)));
in file ../includes/class-bp-toolkit-activator.php:71solving the problem.
I advise you to correct the instruction to prevent other users from falling into this problem.
Davide.
Same problem here: I just installed the plugin to see how it works and, on plugin activation, WordPress says it can’t activate it because of these fatal errors:
Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 20480 bytes) in […]/wp-includes/meta.php on line 1185
Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 20480 bytes) in […]/wp-includes/plugin.php on line 511
So we can’t test it. I don’t know if it can help but consider we have a medium/bigger site with at least 30k users already registered on it.
Anyone can help?
Thanks in advance,
DavideForum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Latest Update breaks Youtube in ampSame problem here. As suggested we have updated to 1.0.77.47 but the problem still persist:
https://validator.ampproject.org/#url=https%3A%2F%2Fwww.gay.it%2Femira-dspain-modella-trans-nera-victorias-secret%2FampThanks for any help.
Hi Ahmed,
I can send you a video shot of the behaviour if you give me an address where to post a little video.Otherwise, what it happens is this:
When you add a post a js error appears in the console:Uncaught TypeError: Cannot read properties of null (reading ‘on’)
at HTMLDocument.<anonymous> (custom-amp-content-button.js?wp-mce-49110-20201110:6:108)
at e (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:30038)
at t (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:30340)as you can see the custom-amp-content-button.js is what is causing the very first js error. Then, if you click on ARVE Button on the TinyMCE Editor you get this error on the console:
Uncaught Error: cannot call methods on dialog prior to initialization; attempted to call method ‘open’
at Function.error (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:2616)
at HTMLDivElement.<anonymous> (core.min.js:116:2055)
at Function.each (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:3003)
at s.fn.init.each (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:1481)
at x.fn.<computed> [as dialog] (core.min.js:116:1794)
at HTMLButtonElement.<anonymous> (admin.js:1:119063)
at HTMLDocument.dispatch (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:43064)
at v.handle (load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,regenerator-runtime,wp-polyfill,wp-hooks&ver=6.0:2:41048)and the popup to enter video details is not shown.
Probably, the problem is that in the page the button with ID “arve-btn” is repeated three times and it seems that it is Amp for WP that creates them.
Hope this is enough for you to understand the problem. IF not I can also give you a temporary login access on our back-end, if it can be useful.
Thanks,
Davide,Same here.
Did someone solve this issue?Thanks
Thanks for the quick resolution :))
Forum: Plugins
In reply to: [Login for WordPress] [object Object]Same problem here, on all pages. Can you please help me to understand where am I wrong?
- This reply was modified 5 years, 10 months ago by budy74.
Ok thanks Nico, your answer is exhaustive!
I’ll try the beta and see what’s happen in GSC.
I repeat that I don’t want to be polemic on this issue, it was just a curiosity of mine :))thanks again for your work.
Davide.Forum: Plugins
In reply to: [OneSignal - Web Push Notifications] Sending out push before Scheduled PostWe have a similar issue: when we schedule a post the notification dose not start (as it should be). When the post is published via wp cron the notification is sent but with the wrong permalink (index.php?p=xxx). This behaviour is not the same for every scheduled post but with some of them and we don’t understand why.
We use Linux cron to call wp-cron.php every 5 minutes.Can someone help us to solve this problem?
Davide.
Hi Nico,
thanks for your reply. You’re right: our theme defined global content_width to 640. We’re just correcting it… Strange that we did not have this problem before the update, anyway issue resolved!Thanks again,
Davide.