gafferCanberra
Forum Replies Created
-
Forum: Plugins
In reply to: [Kadence WooCommerce Email Designer] Customiser Not Loading Prevuiew OrderYes
I used the troubleshooting mode and only had the two plugins open but still no joy.
WooCommerce is fully active.
Forum: Plugins
In reply to: [Custom Login] Thanks for the upgrade and fatal crashAustin
Unfortunately not. The following was report by WordPress:When seeking help with this issue, you may be asked for some of the following information: WordPress version 6.0.1 Active theme: Kahuna Plus Child (version 0.5) Current plugin: Custom Login (version 4.0.6) PHP version 7.4.29 Error Details ============= An error of type E_ERROR was caused in line 210 of the file /home/nationaltrail/www/www/wp-content/plugins/custom-login/src/WpLogin/Login.php. Error message: Uncaught TypeError: Return value of TheFrosty\CustomLogin\WpLogin\Login::removeLostPasswordText() must be of the type string, bool returned in /home/nationaltrail/www/www/wp-content/plugins/custom-login/src/WpLogin/Login.php:210 Stack trace: #0 /home/nationaltrail/www/www/wp-content/plugins/custom-login/vendor/thefrosty/wp-utilities/src/Plugin/HooksTrait.php(197): TheFrosty\CustomLogin\WpLogin\Login->removeLostPasswordText(false, false) #1 /home/nationaltrail/www/www/wp-includes/class-wp-hook.php(309): TheFrosty\CustomLogin\WpLogin\Login->TheFrosty\WpUtilities\Plugin\{closure}(false, false) #2 /home/nationaltrail/www/www/wp-includes/plugin.php(191): WP_Hook->apply_filters(false, Array) #3 /home/nationaltrail/www/www/wp-includes/l10n.php(197): apply_filters('gettext', false, false, 'default') #4 /home/nationaltrail/www/www/wp-includes/l10n.php(361): translate(false, 'default') #5 /home/nationaltrail/www/www/wp-content/themes/kahuna-plus/plus/plus-extras/widgets.php(1119): esc_attr_e(false) #6 /home/nationaltraForum: Plugins
In reply to: [Custom Login] Thanks for the upgrade and fatal crashNot sure what’s happening here but I have V4.0.5 and am having issues as per above with the WooCommerce sites. WordPress is rw3porting a fatal error with the following:
WordPress version 6.0.1 Active theme: Roseta Plus Child (version 0.5) Current plugin: WooCommerce (version 6.7.0) PHP version 7.4.30 Error Details ============= An error of type E_COMPILE_ERROR was caused in line 106 of the file /home/narrabun/public_html/wp-content/plugins/woocommerce/src/Container.php. Error message: Declaration of Automattic\WooCommerce\Container::has($id) must be compatible with Psr\Container\ContainerInterface::has(string $id): boolPS – the image is code not visual in the received email.
Update *** If the field type is changed from email to text all behave as expected. So something to do with field tpe.
Caseproof
Obviously, I have something wrong. In your example, I would not want the roles of sneakers’, ‘backpacks’ or any not logged in visitor to see ANY data. But they can. And if I change the roles to folk that should see data it still does not work for me.Caseproof
Thanks for that but unfortunately it did not work for me.I assume the snippet was to go into the functions.php file.
I have the same issue. It blocks content if you access a product via the menu but if you know the URL the product description is protected but not the product purchase – Add to Cart, product data and product short code content are all visible and will enable a product purchase, even though the product is restricted to members.
Surely, the whole product page should be restricted!
Folks
Thanks, but holding back on plugin version updates is not something I wish to do.I have developed work around that, while not ideal, achieves the client’s outcome.
I have modified via WooCommerce template process the form-billing.php file. The down side is I need to keep an eye on it for upgrades.
This must have also been a recent requirement of WordPress as I do note that your Quadlayers plugin ‘Features’ include “Add html to fields label”
Also, can you point me to the “Replace Text using Text/ Html Swapper” (WP Plugin page) feature and how it operates as I will try and explore that.
Thanks, but a bit of a bummer as the plugin responded well to what was needed on the checkout page using both logic, link and colour. This enabled a last chance for upselling at a better point than the cart page where the customer is more focused on moving through the process of buying. Incidentally, this approach was attracting purchases as you could tell by product purchase combinations.
Any thoughts of how the plugin could achieve the outcome using another of its features?
Forum: Plugins
In reply to: [Checkout Field Manager (Checkout Manager) for WooCommerce] mandatory fieldsI reported this back in April and have yet to see a fix. As an interim you could add the following to your functions.php file:
/* WooCommerce Checkout Manager plugin failure re mandatory fields */
add_filter( ‘woocommerce_default_address_fields’, ‘customise_postcode_fields’ );
function customise_postcode_fields( $address_fields ) {
$address_fields[‘address_1’][‘required’] = true;
$address_fields[‘city’][‘required’] = true;
$address_fields[‘state’][‘required’] = true;
$address_fields[‘postcode’][‘required’] = true;return $address_fields;
}
/* end */Michael
This issue has been around for some time and is unresolved. I had a work around in place to overcome required fields been shown on-screen as optional and vice versa. The system at least did force entry for required fields but it is frustrating for clients when it says on screen the field is optional.But now also I need to change the Label and Placeholder text which the current issue prevents even though it is set in Checkout Manager.
Is there a timing on this fix?
Forum: Plugins
In reply to: [WC Fields Factory] Checkout Admin Not WorkingDon’t worry. I moved to the plugin WooCommerce Checkout Manager
Undid the visserlabs… zip as it was at stable 4.1 whereas the current downloadable zip is stable 4.5