dccs52
Forum Replies Created
-
Can confirm working, excellent news and support
Sure, we have further nailed down what it seems the issue is just with safari and litespeed, only js defer is turned on and excluded the trustindex js but still https://shorturl.at/XCjr2
We have tried disabling defer so no optimisations are running, but seems even with just a cache running the popup does not work in litespeed
It’s been the same since 2020. Wordfence simply updated their system. If you’ve been running it for years then nothing else has changed. We have worsened running as they have a firewall rule already for this.
- This reply was modified 1 year, 3 months ago by dccs52.
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Issue with ACF Shortcode Not WorkingCan confirm, the below works with ACF 6.3.11
function force_acf_shortcode($atts) {
$value = apply_filters('acf/format_value', get_field($atts['field'], $atts['post_id']));
return $value;
}
add_shortcode('acf', 'force_acf_shortcode');Thank you all for finally putting this to rest.
Great work! Look forward to the updates!
Got it thanks. Like the plugin, nice and simple. I would suggest:
- the backend loading animation is very slow, if this using an ajax load, i would suggest just using a normal reload
- The email when cancelled, has the variable that seems to be a bug
- Cancellation Reason
- {{booking.cancel_reason}}
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Issue with ACF Shortcode Not Workinghas anyone got this working with any of the latest update using either SCF or ACF?
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Issue with ACF Shortcode Not Working@jason9j I was planning to do the same thing and report to ACF. If you do could you update this ticket. I will do the same thing. And yes the irony was not lost on me either
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Issue with ACF Shortcode Not WorkingStill can’t update as this bug is still there in 6.3.6.1
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Issue with ACF Shortcode Not WorkingCan also confirm 6.3.6 has a bug for shortcode rendering, 6.3.5 works fine.
Anymore thoughts on this as we are really looking for a solution?
Are you saying the important solution is available already or not?
Or even a switch that says use background instead of background-image for that form?
The latest update has just undone the last menu update, so now we are stuck with an ugly looking Omnisend menu trying to give itself top billing in the WordPress menu.
This is just bad on your part. Omnisend once setup in wordpress is not a plugin you come back to. This is just a cynical way to plant it right at the top of any wordpress admin menu. Do consider your audience and who you’re providing this plugin for. This creates a messy UI and just gives wordpress plugins a bad name for these kind of unwarranted changes.
At least give us the option to move it to the woocommerce menu where it should natively belong.
Forum: Plugins
In reply to: [SMTP2GO for WordPress - Email Made Easy] March 24 update breaking some sitesAlways appreciate the quick response but this has happened too many times.
Please can you put processes in place to triple check before roll out, as this always appears careless. Long time SMTP2GO customer, 12 years, never had to doubt SMTP2GO, but this plugin has already caused many issues for us described above over time.
thanks for the update Mark.
we’ve used SMTP2go since 2012, so a very long time customer.
we use it via the server method and recently in the last year delved into the plugin side via API due to the progress and the fact that some sites are on servers we do not fully control. So hopefully you can understand why I’m trying to understand what’s going on so we can make sound choices for clients. Things such as this happening, the client will never understand nor should they really have to. They just want their email delivered.
Trying to be constructive, even though my initial annoyance did come through, due to the work we had to undertake yesterday to solve this. (My original post was 3:30am GMT)
it turns out some softalicious setups don’t respect the PHP update block, so we had 20 sites update from 1.5.6 to 1.6.1 on a PHP 8 setup. So we had to decide manually revert each one or push forward with 8.1. We pushed with 8.1 as it’s the right thing to do (fixing various things site by site) but ideally we’d like warning in future in the dashboard or through SMTP2go if this gets bumped again via PHP.
apologies, not trying to ramble, and no small violin here, just wanted to give you the real world experiences that happen and its consequences.