Will Stocks
Forum Replies Created
-
@jeherve just FYI – I’ve applied that PR to my site (because it’s small) and it works fine π Everything is showing correctly for me now!
Hi @supernovia
This was my first thought, however my theme hasn’t changed in a couple of months.
The only thing that has changed recently (bar a couple of plugin updates) is WP 5.2. Other than that, I cannot think of anything else recently that has changed that would’ve affected this π
Link to and example page: https://willstocks.co.uk/php-dom-manipulation-snippet/
@magicfilou OneLink is only available in certain countries if I remember correctly.
The link I posted previously lists the countries. But again, itβs still not a replacement/alternative for this plugin, which is a real shame! Makes it really difficult!
I think what @magicfilou and @taisa1984 are referring to is actually OneLink (another Amazon initiative relating to links – https://affiliate-program.amazon.com/help/node/topic/202165020).
Basically, what it will TRY to do (and I emphasise TRY because I see more misses than hits!) is match a product on the international variants of Amazon, but requires some configuratrion I believe?
That being said, SiteStripe or OneLink is by no means a replacement/answer for AALB. AALB was so much more convenient and easy to use.
@taisa1984 I’d be interested to know if you find an alternative?
Forum: Plugins
In reply to: [Cloud Blocks] Uninstalling the plugin leaves an orphaned database tablehi @foadyousefi
I can understand not deleting the table when the plugin is deactivated, but when the plugin is uninstalled completely, I would not expect a database table or configuration to remain (I don’t think I’ve ever seen this in a plugin before)?
As a worst case scenario, yes you could have a popup on uninstall. Or maybe you need a setting in the plugin that defaults to true (but people can then disable this – opt out is better than opt in?) for “Remove all plugin configuration on uninstall”
Nice one, thanks @fstat – I should probably have clicked around a bit more!!!!
Good catch @optimizingmatters! That seems to have done the trick!
I’m still seeing the error relating to:
(index):824 Uncaught ReferenceError: wp is not defined<script type='text/javascript'> ( function( domain, translations ) { var localeData = translations.locale_data[ domain ] || translations.locale_data.messages; localeData[""].domain = domain; wp.i18n.setLocaleData( localeData, domain ); } )( "default", { "locale_data": { "messages": { "": {} } } } ); </script>Also, interestingly (because I was fiddling to try and get this to work), if you enqueue your own version of lodash from a CDN (I know, not advised) this breaks again:
if (!is_admin() && !is_user_logged_in()) { wp_deregister_script('lodash'); wp_register_script('lodash', 'https://cdn.jsdelivr.net/npm/lodash@4.17.11/lodash.min.js', false, '4.17.11', false); }I have just removed the Slideshow block from my article – all errors have now disappeared π
Forum: Plugins
In reply to: [Aquila Admin Theme] Gutenberg post/page editor screen overflowThanks @guyprimavera – I will keep an eye on that other issue (it came first!) and will keep an eye out for the update π
Forum: Plugins
In reply to: [Aquila Admin Theme] Some Aquila CSS is being passed through to the frontendNice one, thanks @guyprimavera π
Forum: Plugins
In reply to: [Autoptimize] Lazy Loading Picture ElementSo, that’s good news then – if the
class="lazyload"is applied to theimg, the whole<picture>element will actually lazyload πApparently it’s the
<img>tag that controls the overall lazyloading.<picture class="lazyload">doesn’t do anything (something I found out myself recently)See lines 358 – 377 of lazysizes readme: https://github.com/aFarkas/lazysizes/blame/gh-pages/README.md#L358
So in theory @optimizingmatters – you’re already supporting the
<picture>element lazyloading πForum: Plugins
In reply to: [Autoptimize] Lazy Loading Picture Element@optimizingmatters – out of curiosity would the lazyloading still be applied to the
<img>element within the<picture>(usually used for fallback)?So if it were formatted:
<picture> <source srcset="full-size.jpg" media="(min-width: 1024px)"> <source srcset="large.jpg" media="(min-width: 300px)"> <source srcset="medium.jpg" media="(min-width: 150px)"> <img srcset="thumbnail.jpg" alt="Image description"> </picture>Would
<img srcset="thumbnail.jpg" alt="Image description">then become<img srcset="thumbnail.jpg" alt="Image description" class="lazyload">or is that<img>ignored?Donβt tease @macmanx ππ
That would be a very welcomed feature, Iβm sure!
OK brilliant, thanks @kokkieh – I’ll give that a go for the time being then π Just looks a bit nicer than
postidπDo you think “custom” displayed URL’s (aka
/%postname%/in the footer) will ever be an option? Ideally I wanted to use my own short URL here, but that’s an entirely different conversation altogether and not something I’m expecting at all! But at least/%postname%/would be a bit more “on brand”!