Dharmesh Patel
Forum Replies Created
-
Forum: Plugins
In reply to: [GoCardless for WooCommerce] Subscriptions importSounds like a great plan. Please don’t hesitate to reach out if you run into anything unexpected, and we’d be glad to hear how the test goes.
Best regards,
Forum: Plugins
In reply to: [GoCardless for WooCommerce] Subscriptions importHello Bill,
Thank you for reaching out to us, and for the detailed breakdown of the meta fields you observed.
For WooCommerce subscription recurring payments, the plugin requires only the mandate ID, stored on the subscription as
_gocardless_mandate_id(the value must begin withMD). When a renewal is due, the gateway constructs the GoCardless payment from that mandate together with the subscription’s own amount and currency, none of the other meta fields are read during this process.Accordingly, the remaining fields do not need to be populated for your migration:
_gocardless_billing_request*pertain solely to the initial checkout flow and are not referenced on renewals._gocardless_payment*are written automatically after each charge, so there is nothing to seed._gocardless_mandateis stored asarray( 'id' => 'MD...' ). You may set it to match for consistency, but it is not the value used when taking renewal payments.
Please also ensure that the payment method is set to GoCardless (
gocardless) on each subscription, so that WooCommerce Subscriptions triggers the charge correctly.We would recommend setting the mandate ID via the Edit Subscription screen (Billing → payment method fields), which validates the
MDformat on save. As a precaution, we would also advise testing the complete flow on one or two records before processing all 600.Please let us know if any further detail would be helpful. Thanks!
Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] How can I style the form?Hi Lee,
Thanks for reaching out, and apologies for the delay in response.Q: How can I do this (without just adding custom CSS – can I add CSS classes to the elements somewhere?)
The plugin doesn’t currently support adding a custom class to the individual elements (inputs, button, etc.). However, if you’re using the block, you can add a class to the wrapper via the block’s Advanced → Additional CSS class(es) field, and then target the inner elements from there.
It’s also worth knowing the block has built-in styling controls in the editor sidebar – background/text/border color, typography (font size, line height, alignment), and spacing (margin/padding), so you may be able to match a good part of your theme without writing any CSS at all.Q: I can’t see anything in plugin settings to customise the form – Can this be done within Mailchimp using the built-in self hosted form settings?
No, changes in Mailchimp’s self-hosted form settings won’t affect the styling here. Those only apply to forms Mailchimp itself renders, not the markup this plugin outputs on your site.
Q: I want to customise the layout of the markup (or at the very least, add classes to my input and button – to change the styling to match my website).
You can add a class to the wrapper (as above) to scope your styles, then target the elements with CSS. The form already outputs stable classes you can hook onto, so you don’t need to add anything to the elements themselves. The main ones:
- Form wrapper:
.mc_signup_form - Text inputs:
.mc_input - Selects:
.mc_select - Radios:
.mc_radio, labels.mc_var_label/.mc_radio_label - Submit button:
.mc_signup_submit_button
Hope that helps! Thanks
Forum: Plugins
In reply to: [Autopost for X (formerly Autoshare for Twitter)] Fixing PHP 8.4 DeprecationsHi @ispreview,
Thanks for reporting this. I’ve created an issue on our GitHub repo to track this, and this will be fixed in upcoming releases.
Thanks!Hi @hlet,
Thanks for reaching out.My understanding of Autopost for X is that it only runs when a specific event occurs (such as when a post is published or updated)
Yes, it only publishes a post to X when the post is published or when you manually post to X. Otherwise, no process runs continuously, and the plugin doesn’t affect the site’s performance. Please let me know if you need any further information.
Thanks!Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] ERROR: submission flagged as potential spamThanks for sharing your feedback, @edker and @yoyun. I’ve opened an issue on our development repository to consider switching to a vanilla JS-based implementation. While we don’t have an ETA set for it yet, we’ll try to review and consider it in the future. Thanks again for all the input you’ve shared here, and please feel free to report any other issues you come across.
Thanks!Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] ERROR: submission flagged as potential spamjQuery has been used from the beginning for tasks like JS submission, date pickers, etc. I’m just curious, why are you disabling jQuery? Is there a specific reason? As of now, we don’t have any plans to remove jQuery, but we’d love to understand your reasons and reconsider if needed. Thanks!
Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] ERROR: submission flagged as potential spamThanks for sharing the error, @edker . Could you please enable jQuery? It is used by the plugin, so disabling it causes the issue. Please enable it, and the issue should be resolved. Thanks!
Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] ERROR: submission flagged as potential spamThanks for providing all this information, @edker.
Based on what you’ve shared, it seems you have JavaScript disabled in your browser. Could you please confirm if that’s the case? If not, are you seeing any JavaScript errors in the console?
Thanks!Forum: Plugins
In reply to: [Mailchimp List Subscribe Form] Subscription Form BugHi @cognisant_2000,
Thanks for reporting the issue.
In the recent release (1.7.0), we updated the Subscribe Form block, which now lets you reorder form fields, edit form labels, and more. You can use the block to arrange the fields as needed.
If you’re still using the old widget or shortcode, you can fix the field order by adding the code snippet below to your theme’sfunctions.phpfile. This will ensure your changes aren’t overwritten during plugin updates. However, we still recommend switching to the block. Please let us know if you run into any difficulties setting it up.add_filter( 'option_mc_merge_vars', function( $value ) {
if ( empty( $value) || ! is_array( $value ) ) {
return $value;
}
// Reorder the merge vars by display order.
usort($value, function ($a, $b) {
return $a['display_order'] <=> $b['display_order'];
});
return $value;
} );We’ve also created a GitHub issue to address this within the plugin itself.
Thanks!
Hi @gemini23,
You can see under the “X/Twitter connection settings” in Autopost for X/Twitter Settings and you can navigate to it by visiting Settings > Autopost for X/Twitter.
Thank youHi @gemini23,
Thank you for reaching out to us.
Based on the error, it seems the X app is configured incorrectly. Could you please confirm and configure the X app by following the steps on the plugin settings page (Settings > Autopost for X/Twitter), specifically the step “Set theCallback URLsfields to [specified value].”Please let me know if you are still experiencing any issues after following the steps.
Best Regards,Hi @justinwyllie,
Thank you for reaching out to us and reporting this issue.
Yes, the plugin currently has a hardcoded limit of 280 characters. I have opened an issue on our GitHub repository regarding this, and we will aim to implement and release a fix in upcoming plugin releases. Please follow the GitHub issue to stay updated on its progress.
Feel free to reach out to us if you need help with anything else.
Thank you!
Hi @justinwyllie,
Thank you for reaching out to us.Yes, that is the expected behavior. We currently have an open issue to add the ability to customize the order of the tweet text, hashtags, and link. In the meantime, you can use the
autoshare_for_twitter_bodyfilter to modify the tweet body according to your requirements. (You can find a code snippet for it here)Please feel free to let us know if you need any further information.
Thank you.Hi @behandlung,
Thanks for reaching out to us.
You can define the content to be shared at the post level by adding content to the “Custom message” field. However, we currently don’t have a UI for setting the default share content. We have an open issue for this, but there is no scheduled timeline for adding it to the plugin.
For now, you can use the
autoshare_for_twitter_bodyfilter to tweak the tweet body content to be shared. For example, if you want to share the post excerpt, you can use the following code snippet to do that:add_filter(
'autoshare_for_twitter_body',
function( $tweet_body, $post ) {
// Bail if we have a custom message.
$custom_message = get_post_meta( $post->ID, 'autoshare_tweet-body', true );
if ( ! empty( $custom_message ) ) {
return $tweet_body;
}
// If we have an excerpt, use that.
$excerpt = get_the_excerpt( $post );
if ( ! empty( $excerpt ) ) {
$tweet_body = $excerpt;
}
return $tweet_body;
},
10,
2
);Hope this helps you.
Thank you.