sandeld
Forum Replies Created
-
This post is more of a reminder to myself and for record keeping. The version this is not working on is 1.2.9, last updated on 12/12/2018.
Which, 2 months without an update with a known, major bug seems very negligent.
- This reply was modified 7 years, 3 months ago by sandeld.
I’m using v2.0.2 and I’m getting “opportunity messages” from Google PageSpeed Insights that the images are not lazy loading.
I’m also not entirely sure if this just means that I need to upload more properly sized pictures to begin with or if maybe your plugin is missing something here as well.
Why is this marked as resolved? It is still very much broken and unusable.
I made a test page for you to use. Also, any chance that “group” capability is coming, or at least the possibility of adding custom code to a submit event?
Yes. But you can’t see it on the site because I don’t publish it since it’s not working. I just added it again so that you could see it still doesn’t work.
Yes, it’s still there.
I click on “Purge cache”, the notification pops-up that tells me the cache has been cleared, and then I cannot close it and it doesn’t disappear on its own.
I just spent almost an hour with your online chat support, and he said that since he can’t reproduce the problem and there are no error logs, there is nothing he can do.
So basically I can’t use your plugin until something magically happens and they disappear at some random point in the future if the universe allows it. Cool.
Forum: Plugins
In reply to: [Comic Easel] Different navigation? Swiping through pages?I’m still a little confused on making the swipeable pages. you said:
yes you can create a swipe for mobile, can link it directly to this function:
function ceo_get_adjacent_comic($previous = true, $in_same_chapter = false, $taxonomy = 'comic')
to go prev and next $previous = false -> is next comicBut I’m not sure where to insert that code snippet.
On the mobile front, Zappbar looks and works amazingly well! Thanks!
Forum: Plugins
In reply to: [Comic Easel] Different navigation? Swiping through pages?This is all very fantastic!
I’m going to work on the site today or tomorrow and will check back in if I have any problems.
Forum: Plugins
In reply to: [MC4WP: Mailchimp for WordPress] GDPR consent with WooCommerce IntegrationYes they do.
I’m having this exact same problem. It’s on the homepage at the very bottom:
Forum: Reviews
In reply to: [Mailchimp for WooCommerce] It’s pretty worthlessSandeld, what other plugins do you use to get WooCommerce data over? I desperately want to work with abandoned cart recovery via Mailchimp.
I still use this horrible plugin out of necessity, but I pair it with “MailChimp for WordPress” and custom coding to avoid conflicts and to make sure I get all the functionality I need. It really depends on my clients’ applications though.
I think I would still avoid this plugin in the short term. I have uncovered two different bugs in the integrations between MailChimp and Shopify, and MailChimp and WooCommerce. Clearly something is broken at MailChimp right now so I’d hold off on this one for a few weeks if you can, and maybe they’ll have something updated and functional again.
I’ve done that before, and it didn’t work either. I’m pretty sure it has something to do with the response in my other thread:
Either way, I can’t use the plugin because of that deficiency, and I’ve had to deactivate it on all the other sites it was on too.
When using API then don’t allow to re-subscribe the same address that was already subscribed to list.
That’s a pity since so many other plugins offer this kind of “update” feature (not necessarily popup plugins, but just plugins that integrate with MailChimp in general).
I’m not an expert on the API, but I know there’s a difference between “adding” a subscriber and “updating” a subscriber. Perhaps your plugin could make use of that, because I cannot use your plugin the way it currently is.
They are unrelated. I hope.
I’ve setup my form to put people into the hidden group like this:
And when I test it on the front end with a completely random email address (re: the other thread that exposed a bug), I get an error like this: