alissit
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Swiper] Version 1.2.1 not workMostly working now – but only if the JS is loaded on every page.
I can’t have that setting disabled or swiper isn’t loading when a block is present.
Forum: Plugins
In reply to: [WP Swiper] Version 1.2.1 not workSame here – 2 websites broken.
Error showing as:TypeError: Cannot read properties of undefined (reading ‘substring’)
at P (https://xxxx/wp-content/plugins/wp-swiper/gutenberg/js/admin_block.js?ver=1.0.0:1:35534)
at $r (https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:9383)
at Ur (https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:9764)
at https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:38850
at eo (https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:38966)
at https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:40051
at ro (https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:40115)
at https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:41197
at Array.reduce ()
at no (https://xxxx/wp-includes/js/dist/blocks.min.js?ver=0d232d232463200f5cfd:19:41173)Forum: Plugins
In reply to: [SVG Support] Undefined array key css_targetJust more info – I’ve had the plugin enabled for at least a month, and today was the first time I have the error in my error_log. So it doesn’t occur on activation:
PHP Warning: Undefined array key “css_target”
Forum: Plugins
In reply to: [WP Swiper] Disable script loading on specific pagesAny update on this? It would be great if the scripts only loaded on pages where the block is used.
Forum: Plugins
In reply to: [Automatic Product Categories for WooCommerce] More than one ruleSo your plugin is set to strip previously set categories if the rule does not match the product.
All my products have had their previously set categories stripped because my new rules no longer matched. This behaviour is odd. I’ve had to restore the site because I have 100’s of products and testing the plugin stripped them of all their categories.
Your applyTo function is as follows:else { foreach ($this->terms as $taxonomy => $termIds) { if ($termIds) { wp_remove_object_terms($product->get_id(), $termIds, $taxonomy); } } }
I can’t recall if this also stripped the manual categories I had placed the products in – but it stripped all the categories that I had set up with one rule – which I then deleted and tried a new rule.
Your plugin REALLY needs some documentation.This is how I did it on my shop, working perfectly.
add_action('init', 'remove_custom_loop_product_link', 100); function remove_custom_loop_product_link() { $instance = WPCleverWoosq::instance(); if (isset($instance) && has_filter('woocommerce_loop_product_link', [$instance, 'loop_product_link'])) { remove_filter('woocommerce_loop_product_link', [$instance, 'loop_product_link'], 99); } else { } }
Forum: Plugins
In reply to: [Conditional Fields for Contact Form 7] Invalid mailbox syntaxNo response at all?
Forum: Plugins
In reply to: [Simple Lightbox for WordPress] Custom Post TypesHi Martin,
I can give you access to the site if you want to log in and have a play with it?
Alternatively, the plugin Custom Post Types creates the exact same CPT that ACF Pro does. That’s just a new feature that they’ve released, but they are implemented the same way that the CPT plugin handles them (I think)
Forum: Plugins
In reply to: [Simple Lightbox for WordPress] Custom Post TypesHi Martin,
Yes, I’ve added the proper CSS class to the JSON, and it’s working perfectly on pages, but not on CPT’s.
Looking at Dev tools, I can see the JS being added on the pages, but on the CPT the JS doesn’t load at all.
I’m assuming because CPT’s aren’t normal post-types, they aren’t supported yet?
You can see it working properly on this page:
https://eleanorspensart.co.uk/gallery/But here’s a CPT where it’s not working:
https://eleanorspensart.co.uk/gallery-piece/crows-gathering/
I’m using the same CSS class on both URL’s.Here’s the JSON – I’ve tried adding ‘gallery-piece’, as that’s the CPT name, but it’s not working. It doesn’t work no matter what combination I’ve tried.
{ "$schema": "./settings/settings-schema.json", "hrefTypes": [ "Empty", "Media" ], "postTypes": [ "page", "post", "home", "front", "gallery-piece" ], "cssClassesToSearch": [ "wp-block-image", "gallery-piece-image", "wp-block-media-text", "wp-block-video", "postie-image", "wp-block-embed-youtube", "page-header-image-single" ], "excludeIDs": [ 0 ] }
Forum: Plugins
In reply to: [WPC Variation Swatches for WooCommerce] Swatches are showing AlphabeticallyResolved
Forum: Plugins
In reply to: [WPC Variation Swatches for WooCommerce] Swatches are showing AlphabeticallyAll new products had the attributes in the correct order, but I had to delete and re-add the older products to get them in the right order.
Thanks Peter!
I didn’t see the reply until now. I’ll check out the htaccess files and server setup.
We copied & moved the entire site from one domain & hosting to a new domain & hosting. It wasn’t happening on the previous set up, so most probably something to do with the new host & htaccess or server.Thank you very much!
This link has a solution:
https://github.com/dudaster/ele-custom-skin/issues/118The issue is in elementor, line 1181 of /elementor/includes/base/controls-stack.php
Change that line from:
if ( $dynamic_property ) ) {
to
if ( $dynamic_property && isset($settings[ $control_name ][ $dynamic_property ]) ) {You shouldn’t have plugins of wourse, but Elementor is aware of the issue, but haven’t fixed the issue now going on 10 months.
- This reply was modified 4 years, 2 months ago by alissit.
Forum: Plugins
In reply to: [WP Store Locator] Info Box on Map not opening above markerGreat, thanks Tijmen. Your plugin is amazing and has been loads of fun to customise! Thankful for the great docs you have posted as well ??
Forum: Plugins
In reply to: [WP Store Locator] Info Box on Map not opening above markerBy changing to default style, what functionality/style changes?
Thanks for the quick fix on this!