CodeBard
Forum Replies Created
-
I installed all but one of your plugins (i just installed a close one to that) and at the end i wasnt able to reproduce the issue.
P3 plugin profiler result doesnt even show the plugin in the pie chart.
http://test.codebard.com/hello-world/
Test site has no issues.
If peak mem usage was 64 mb, and your installation is running out of mem, then it means that your mem is STILL capped at 64 mb or vicinity.
Just putting in
define(‘WP_MEMORY_LIMIT’, ’256M’); etc wont change your mem limit.
Your PHP config defines your mem limit. In web servers using FastCGI, fcgid config also limits mem usage.
You should seek to check and increase your mem limit at php config by contacting your host, if it is at or around 64MB.
Can you install the famous P3 Plugin Profiler (https://ww.wp.xz.cn/plugins/p3-profiler/) and run an analysis to see what is the mem usage of plugins per plugin?
Can you give me a list of plugins you have at your wordpress install? Lets see if i can reproduce the situation.
http://test.codebard.com/hello-world/
Nope, cant reproduce. Images work fine in custom images folder.
Ill try to reproduce it in another way. Lets see.
Cant reproduce this problem at all, with the particular define you mentioned. Images work normally.
Just put the filter and function in the earlier post into your theme’s functions.php, or, even better, a dud plugin just having this code.
And in below bit:
$link= add_query_arg( ‘myparam’, ‘myvalue’, $link);
Change myparam to your url var, like, utm_source or utm_medium etc, whichever,
and myvalue to the value you want.
It doesnt need to be huge amount of plugins. just a few big plugins (woocommerce etc) are enough. Plugins in that class i mean.
At this point the only thing to do is to go up until you dont get memory issues anymore. Try 500~ mb or so. If again you get the error, then we can say that there is something going on.
You are so far the only one experiencing this, there may be a conflict in between plugins but its early to tell.
It seems you possibly increased the mem limit to 256, but you are still short. the error message shows 268 mb. You must be using some big plugins at your website.
Increasing the mem limit to 320 etc and then decreasing it from there until you get the mem error can help you to determine the mem limit you need.
Update: 2.0.0 fixes all these PHP notices.
You can update through your WP admin.
This can only be due to the memory limit at your WordPress being set low at default.
I was able to reproduce this issue at a default WordPress installation only by limiting WordPress memory to 32 mb via config.
define(‘WP_MEMORY_LIMIT’, ’32M’);
And even then only at admin. Front end works fine.
You may have numerous high memory use plugins in your WordPress, and the added mem use from this plugin may be pushing it over the limit.
At this stage the best solution would be to increase the mem limit, either from WordPress or PHP (sometimes both).
Hi again,
With the new major version (2.0.0) now filtering the urls is possible. You can add any parameter by hooking to the url generating function below:
add_filter( ‘cb_p6_filter_vars_after_make_to_patreon_url’, ‘yourfunction’);
And your function can be like:
function yourfunction($link)
{$link= add_query_arg( ‘myparam’, ‘myvalue’, $link);
return $link;
}
Naturally, it will go away when updated.
Next version of the plugin will bring a totally new plugin core, which allows every single action that happens inside the plugin to be hookable via filters and actions.
This could allow you to modify the url by modifying it through a filter. You can place it in a plugin file of yours, so it wont go away when the original plugin (this) gets updated.
The new version already has it. When it is published you wont get PHP notices.
However, in the meantime you can use current version without hesitation. Debugging necessity is at a minimum, since the plugin is OOP code, totally isolated, and it uses only wordpress functions, hooks, filters.
Since you have a production server and a test server, you are either a developer or sufficiently knowledgeable with PHP.
Notices should not be turned on on production servers, and the notices on your development server wont affect the operation of your plugin or your wordpress on your production server.
If there are any actual errors or issues that lead to anything in your wp admin becoming dysfunctional, please describe them in sufficient detail.