drtonyb

I see no parent page selector in Gutenberg 3.2 nor has there been in any of the earlier versions.

Pages were originally created using the classic editor. For child pages, the parent page selector shows in the classic editor. Open a child page in Gutenberg, there is no parent page selector, only a template and order selector.

Actually,

$merge_vars = apply_filters( ‘mailchimp_woocommerce_merge_vars’, $merge_vars, $user );

would be a better order for the filter arguments.

Having a closer look at this, I have concluded that it is not currently possible. The only fields added to the mailchimp list are first_name and last_name.

However, the simple addition of a filter for the $merge_vars on line 114 of the class MailChimp_WooCommerce_User_Submit in file includes\processes\class-mailchimp-woocommerce-user-submit.php would allow developers to easily add extra custom fields to the mailchimp list captured in the registration process.

For example:
$merge_vars = apply_filters( ‘mailchimp_woocommerce_merge_vars’, $user, $merge_vars );

Please consider adding such a filter. I believe it would greatly enhance this useful plugin.

• This reply was modified 6 years, 8 months ago by drtonyb.

Please disregard my post. I have found the problem – a required field on the mailchimp list that my client had setup that should not have been ‘required’. New customer registration now works.

Found my problem – content being pasted had a new line at the end of it.

Still, if I paste content like this at the end of an existing block, should a new block be created or not?

Hello Birgit,

Thanks for your reply. Your suggestion to check the error in the browser Console (in my case Firefox) has lead me to the cause of the problem. It was code I had recently added to my own plugin, which I have now found wasn’t doing what I had planned it to do – it was inadvertently replacing ‘ with ” in scripts causing strings to terminate mid string resulting in multiple JS syntax errors. I have removed the code from my plugin and all is well.

Thanks again,
Tony

Hi Zandy,

Tested again after updating to 1.0.27 and the transaction with Square completed successfully. There is an update to woocommerce that I will be installing today.

Prior to the successful test yesterday, three tests using version 1.0.26 resulted in ‘failed’, but the customer was charged and in the first test, was charge twice (this could have been a tester problem, but a double charge should never have been able to happen). I think it could have been related to the timeout issue that has been changed in version 1.0.27.

Here is the System Status Report: (note that the theme is my own theme)

### WordPress Environment ###

Home URL: https://tasteblackgold.com.au
Site URL: https://tasteblackgold.com.au
WC Version: 3.3.1
Log Directory Writable: ?
WP Version: 4.9.4
WP Multisite: –
WP Memory Limit: 128 MB
WP Debug Mode: –
WP Cron: ?
Language: en_AU

### Server Environment ###

Server Info: Apache/2.2.34 (Unix) mod_ssl/2.2.34 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 Phusion_Passenger/5.1.11 mod_perl/2.0.8 Perl/v5.10.1
PHP Version: 5.6.33
PHP Post Max Size: 8 MB
PHP Time Limit: 30
PHP Max Input Vars: 1000
cURL Version: 7.54.0
OpenSSL/1.0.2k

SUHOSIN Installed: ?
Max Upload Size: 2 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 3.3.1
WC Database Prefix: wp_
MaxMind GeoIP Database: ?
Total Database Size: 10.53MB
Database Data Size: 9.26MB
Database Index Size: 1.27MB
wp_woocommerce_sessions: Data: 0.16MB + Index: 0.01MB
wp_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_order_items: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_order_itemmeta: Data: 0.00MB + Index: 0.01MB
wp_woocommerce_tax_rates: Data: 0.00MB + Index: 0.01MB
wp_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.01MB
wp_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB
wp_404_to_301: Data: 0.41MB + Index: 0.00MB
wp_blc_filters: Data: 0.00MB + Index: 0.00MB
wp_blc_instances: Data: 0.01MB + Index: 0.00MB
wp_blc_links: Data: 0.03MB + Index: 0.01MB
wp_blc_synch: Data: 0.00MB + Index: 0.00MB
wp_commentmeta: Data: 0.00MB + Index: 0.00MB
wp_comments: Data: 0.00MB + Index: 0.01MB
wp_links: Data: 0.00MB + Index: 0.00MB
wp_options: Data: 0.92MB + Index: 0.07MB
wp_postmeta: Data: 0.46MB + Index: 0.14MB
wp_posts: Data: 0.50MB + Index: 0.06MB
wp_termmeta: Data: 0.00MB + Index: 0.01MB
wp_terms: Data: 0.00MB + Index: 0.01MB
wp_term_relationships: Data: 0.01MB + Index: 0.01MB
wp_term_taxonomy: Data: 0.00MB + Index: 0.01MB
wp_usermeta: Data: 0.02MB + Index: 0.01MB
wp_users: Data: 0.00MB + Index: 0.01MB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB
wp_wfBadLeechers: Data: 0.02MB + Index: 0.00MB
wp_wfBlockedCommentLog: Data: 0.02MB + Index: 0.00MB
wp_wfBlockedIPLog: Data: 0.05MB + Index: 0.00MB
wp_wfBlocks: Data: 0.02MB + Index: 0.02MB
wp_wfBlocks7: Data: 0.02MB + Index: 0.05MB
wp_wfBlocksAdv: Data: 0.02MB + Index: 0.00MB
wp_wfConfig: Data: 0.30MB + Index: 0.00MB
wp_wfCrawlers: Data: 0.02MB + Index: 0.00MB
wp_wfFileChanges: Data: 0.02MB + Index: 0.00MB
wp_wfFileMods: Data: 1.52MB + Index: 0.00MB
wp_wfHits: Data: 1.02MB + Index: 0.23MB
wp_wfHoover: Data: 1.52MB + Index: 0.11MB
wp_wfIssues: Data: 0.02MB + Index: 0.06MB
wp_wfKnownFileList: Data: 1.52MB + Index: 0.00MB
wp_wfLeechers: Data: 0.02MB + Index: 0.00MB
wp_wfLockedOut: Data: 0.02MB + Index: 0.00MB
wp_wfLocs: Data: 0.02MB + Index: 0.00MB
wp_wfLogins: Data: 0.17MB + Index: 0.06MB
wp_wfNet404s: Data: 0.02MB + Index: 0.02MB
wp_wfNotifications: Data: 0.02MB + Index: 0.00MB
wp_wfPendingIssues: Data: 0.02MB + Index: 0.06MB
wp_wfReverseCache: Data: 0.02MB + Index: 0.00MB
wp_wfScanners: Data: 0.02MB + Index: 0.00MB
wp_wfSNIPCache: Data: 0.02MB + Index: 0.05MB
wp_wfStatus: Data: 0.16MB + Index: 0.11MB
wp_wfThrottleLog: Data: 0.02MB + Index: 0.02MB
wp_wfVulnScanners: Data: 0.02MB + Index: 0.00MB
wp_yikes_easy_mc_forms: Data: 0.00MB + Index: 0.00MB
wp_yoast_seo_links: Data: 0.02MB + Index: 0.02MB
wp_yoast_seo_meta: Data: 0.02MB + Index: 0.00MB

### Post Type Counts ###

acf-field: 12
acf-field-group: 1
attachment: 95
custom_css: 1
nav_menu_item: 18
page: 22
post: 17
product: 27
product_variation: 11
publication: 1
revision: 206
shindiri-woo-slider: 1
shop_order: 4
turbo-sidebar-cpt: 3
woocarousel: 1

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (32) ###

404 to 301: by Joel James – 2.3.3
Add From Server: by Dion Hulse – 3.3.3
Advanced Custom Fields PRO: by Elliot Condon – 5.6.8
Australia Post WooCommerce Extension: by WPRuby – 1.5.8 – Not tested with the active version of WooCommerce
Broken Link Checker: by Janis Elsts
Vladimir Prelovac – 1.11.5

Custom Login URL: by Simpliko – 1.0.2
EasyRecipe: by EasyRecipe – 3.5.3229
Enable Media Replace: by M?ns Jonasson – 3.1.1
Enhanced Media Library: by wpUXsolutions – 2.5
Force Regenerate Thumbnails: by Pedro Elsner – 2.0.6
Google Language Translator: by Rob Myrick – 5.0.37
HubSpot Tracking Code for WordPress: by HubSpot – 1.2.1
List category posts: by Fernando Briano – 0.75.2
Metrilo for WooCommerce: by Metrilo – 1.7.5 – Not tested with the active version of WooCommerce
Multiple Roles: by Florian TIAR – 1.2.0
WooCommerce Product Carousel Slider: by ADL Plugins – 3.0.2 – Not tested with the active version of WooCommerce
Redirect Default Login Pages: by Coyote6 GraphX – 1.0.0
Taste Black Gold: by Tony Blackett – 1.0.0
Themextras: by Tony Blackett – 1.1.3
Under Construction: by Noah Kagan – 1.18
Widgets On Pages: by Todd Halfpenny – 1.4.0
Shindiri Woo Shop Slider Lite: by Shindiri Studio – 1.2.1 – Not tested with the active version of WooCommerce
WooCommerce Email Test: by RaiserWeb – 1.8 – Not tested with the active version of WooCommerce
WooCommerce Square: by WooCommerce – 1.0.27
WooCommerce Wholesale Prices: by Rymera Web Co – 1.6.2
WooCommerce: by Automattic – 3.3.1 – 3.3.2 is available
Wordfence Security: by Wordfence – 7.0.5
Yoast SEO: by Team Yoast – 6.3.1
WP Publication Archive: by Eric Mann – 3.0.1
WP Video – HTML5 Video Player for WordPress: by onigetoc – 4.5.5
WPB WooCommerce Product slider: by wpbean – 2.0.6.3
Easy Forms for MailChimp: by YIKES
Inc. – 6.3.30

### Settings ###

API Enabled: ?
Force SSL: ?
Currency: AUD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

### WC Pages ###

Shop base: #51 – /products/
Cart: #53 – /products/cart/
Checkout: #55 – /products/checkout/
My account: #57 – /products/my-account/
Terms and conditions: #556 – /terms-and-conditions/

### Theme ###

Name: Taste Black Gold
Version: 1.0.0
Author URL: https://anthonyblackett.com.au/
Child Theme: ?
Parent Theme Name: PressFlex
Parent Theme Version: 1.0.9.7
Parent Theme Author URL: https://anthonyblackett.com.au/
WooCommerce Support: ?

### Templates ###

Archive Template: Your theme has a woocommerce.php file
you will not be able to override the woocommerce/archive-product.php custom template since woocommerce.php has priority over archive-product.php. This is intended to prevent display issues.

Overrides: taste-black-gold/woocommerce/cart/cart-totals.php
taste-black-gold/woocommerce/cart/cart.php
taste-black-gold/woocommerce/cart/proceed-to-checkout-button.php
taste-black-gold/woocommerce/content-product.php
taste-black-gold/woocommerce/emails/email-footer.php
taste-black-gold/woocommerce/emails/email-header.php
taste-black-gold/woocommerce/emails/email-styles.php

Hello royho,

If a customer could ‘accidentally’ click the payment button more than once, without knowing and have it process the payment more than once for the same order number, then return a failed transaction, I would think that would be a very serious problem indeed.

Thanks Caleb, just a note on your comment in the issue opened on github that the browser should be able to correct this problem: for me using Firefox, it threw the footer div block outside the site wrapping div, so the footer and its content became full width, and the css styling in the footer became confused so that text defaulted to black, the same colour as the background and ‘disappeared’. Fortunately, I tested on my development system before updating the live site.

I reported these problems more than 2 years ago now and nothing has been done to fix them.

https://www.ads-software.com/support/topic/severly-broken-in-debug-mode-not-truely-compatible-with-43/?replies=2#post-7466262

Yes, as a normal user you won’t see that there are problems, but the issues mean that the plugin is not compatible with the current WordPress version as stated by the developer. One day, when the deprecated functions are removed, the plugin will break for everyone.

Thank you for the quick update Waseem. The calculation problem was my fault – invalid postcode, although the error message did not point me to this.

Tony

Thanks for the prompt fix Kevin.

You say that you can’t reproduce the error. Are you running your development system in WP_DEBUG mode? If so, it should be logged in the usual php error log when the edit form page is loaded or refreshed.

I run my development environment in WP_DEBUG mode and often encounter errors in plugins. I’m also seeing another error in this plugin which I’ll report separately.

Tony

Thanks again Josh,
The code patch I mentioned ensures that the result of the array_intersect re-indexes the returned array starting at index 0 if the user has a wholesale customer role, otherwise, it returns an empty array. Since this will return exactly what is expected from the getUserWholesaleRole() function, it will not cause any problems in other parts of the plugin code.

Cheers,
Tony

Thanks Josh for your quick response. Your explanation for returning an array is fine. I thought it might be something like accommodating more than one wholesale user role in the future. However, assuming that the returned array will always begin at index 0 because WordPress only lets you assign one role per user means to me that a user will only ever have one wholesale customer role, so the returned array will only ever have one value, the opposite to why you explained an array is returned. If this is not the case, then I’m missing something here.

Regardless, your code should ensure that the returned array always has the expected value indexed by 0 if that is how you are going to access it. Installing another plugin should not break your plugin, especially when there is a simple solution to fix it.

Regards,
Tony

@klaconcepts The problems that still exist in this plugin that I am referring to are only evident when WordPress is in DEBUG mode. A live site should not be running in DEBUG mode and would not report the errors. How is the plugin breaking your site?