Stefano Lissa
Forum Replies Created
-
Hi, we saw and replied to your support request as well:
https://ww.wp.xz.cn/support/topic/plugin-has-stopped-working-38/
If you need more support or feedback let us know.
Forum: Plugins
In reply to: [Newsletter - Send awesome emails from WordPress] Plugin has stopped workingHi @jlvdaum if the engine lock is zero, you have a different problem. Please open a new support request so we can discuss your specific issue. On the new support request, report if there is a notification on top of the Newsletter admin pages about the “scheduler not working”.
Forum: Plugins
In reply to: [Newsletter - Send awesome emails from WordPress] Plugin has stopped workingIn a hour, please go to your Dashboard/Update and see if there is an update available for the Newsletter plugin. That last version changes the lock strategy, if the problem is the sending engine lock. For both the requests, thanks.
Forum: Plugins
In reply to: [Newsletter - Send awesome emails from WordPress] Plugin has stopped working@jlvdaum with stopped what do you mean? Like in the first ticket is something related to the newsletter sending not progressing? Could you follow the same instruction I gave above: “Please, goto the page Newsletter/Help/Sending and check if the “Engine lock” is set to a number. Please let me know even which is the speed set on Newsletter/Settings/Sending.”
Forum: Plugins
In reply to: [Newsletter - Send awesome emails from WordPress] Plugin has stopped workingHi, not sure it is your specific case, but you could be facing a problem with the latest plugin version and a provider with a forced timeout on task execution. Please, goto the page Newsletter/Help/Sending and check if the “Engine lock” is set to a number. Please let me know even which is the speed set on Newsletter/Settings/Sending.
Thanks!
Hi, the missing domain part is probably due to a configuration in your wp-config.php file or in the WP/Settings/General. It seems the domain part has been removed to generate relative paths.
Or the WP admin_url() function is filtered in someway.
If when you send tests from the admin side, you get the links correctly inserted in your newsletter, it means that the filter/configuration is active only on the frontend and during the “cron”.
You can change the action links type on Newsletter/Settings/Advanced and set it to “standard” so they don’t use the admin-ajax.php, but they will be addressed directly to the site index page with specific parameters.
About the apply for the text block, it could be a conflict with another plugin or your theme, injecting javascript into our admin pages. You can try to open the browser developer console (on Chrome you can press CTRL-SHIFT-i) and check for reported errors in the console tab.
Hi, since the subscribe2() function I see in the error report checks for the existence of that email, I suppose there was an instantaneous double submission of the same email address, and the second submission triggered the error (the first submission added the email to the database, the second one cannot add it once again… but if the submission are sent at the same time, the initial check can be ok for both).
The second error is a consequence of the first one.
Thank you for reporting that specific case, we’ll add a check on the save step to correctly manage it.
Forum: Plugins
In reply to: [Head, Footer and Post Injections] After the tag not workingYes, it’s something new, to avoid a deprecated buffering practice. If you can modify your theme (all free a pro theme should already be conformant), add the
<?php do_action('wp_body_open'); ?>after the <body …> tag-
Forum: Plugins
In reply to: [Head, Footer and Post Injections] After the tag not workingHi, you should check if your theme has the “do_action(‘wp_body_open’)”, is a WP standard but a theme should be missing it. That do_action is important to avoid resource consuming buffering and parsing.
Hi, you’re absolutely right, update to 9.2.1, it’s fixed now. Thank you.
Hi, please update to version 3.3.6 there was a problem on version 3.3.4. I need to recode this plugin since it uses old coding methods… sorry for this inconvenience.
Forum: Alpha/Beta/RC
In reply to: Bug in php-ai-client PromptBuilder (beta5)Hi, sorry, it is not a bug, the code using that method was calling it in the wrong way. Nothing to change! 🙂
Forum: Plugins
In reply to: [LiteSpeed Cache] Sharing a problem with Redis a WP cronYes, if the object cache option is on, but the redirs/memcached modules are, for example, missing, WP still use the object cache.
When saving the settings for the object cache, the drop in file could be deleted if there are no chance that cache can work. But a check before activating it is needed, since the services (memcached/redis) can fail later.
Forum: Plugins
In reply to: [LiteSpeed Cache] Sharing a problem with Redis a WP cronShort update. Intalled the plugin on a site NOT running on a LiteSpeed web server. Enabled the object cache and got the correct message, that it cannot work being missing the right server. It reports redis disabled, memcached disabled, connection failed.
But if I run wp-cron.php, wp_using_ext_object_cache() is returning true and the scheduler exists immediately after the first job (it tries to get a transient and compares it with the previously generated value, but the transient is empty).
Probably something needs to be done on the object cache configuration: if it’s not available, the object-cache drop-in file should be removed (just an idea).
Forum: Plugins
In reply to: [LiteSpeed Cache] Sharing a problem with Redis a WP cronHi, I cannot test in on the production sites, but I can try to setup a test site to reproduce the original problem. Thank you!