SPiNNdevs
Forum Replies Created
-
Forum: Plugins
In reply to: [Responsive Picture Block] Usage with synced pattern overrideslove it, thank your very much!
Forum: Plugins
In reply to: [Responsive Picture Block] Usage with synced pattern overrides1. I think allowing to change the image source it totally fine in many use cases. We often have the case that we are providing hero section as synced pattern with overrides and have pre defined breakpoints defined in the synced pattern and only want the user to edit/change the image source itself. So I think your plugin would be really helpful for this workflow and works like this already in the backend.
2. Ah ok, I missed that this is the intended way it should work, or interpreted it wrong. I think was especially misleading is that there are other options which don’t change the default behaviour like Show All or Desktop. I think Desktop should only display the Desktop image, what it is not doing at the moment. Also “Auto (use editor preview)” sounds for me, like it should only display the desktop image in the editor of no other breakpoint was selected for the preview. Maybe a solution would be:
– make “Show All” the default Option
– update “Desktop” Mode to show only the Desktop image all the time
– update “Auto (use editor preview)” to behave like the frontend “real” codeForum: Plugins
In reply to: [Responsive Picture Block] Usage with synced pattern overridesHello, thank you for the very fast feedback! 🙂
1. yeah, hopefully WordPress make a move here, this is currently very limiting… BUT you plugin already works with synced pattern overrides in the Gutenberg backend editor. It “only” does not work correctly in the frontend. So I was wondering, if there would be a way to fix with the current status of WordPress.
2. In the frontend everything is fine. But in the backend editor, Mode: Auto (use editor preview) always shows all images. To replicate, just start your playground “Live preview” link and edit your demo page. We are using the newest version of Chrome.
Very nice, thank you!
Forum: Plugins
In reply to: [Contact Form 7] v5.7 ‘wpcf7_form_novalidate’ hook removed (alternatives?)@takayukister Alright, thank you.
@zoonars Thanks for you suggestion 🙂 , but we have a slightly other problem then discussed in that ticketHi Torsten,
Thanks for your reply!
Turned out, it’s our own code, so we fixed it by not adding the attribute in advance to the input when your plugin is active. Fair enough.Thank you,
Best regards@haet any news on this?
@haet do you consider adding this update to your plugin?
Yeah, seems to be necessary to work in all email client consistently…
The conditional comment seems to do the trick for outlook that the preheader keeps being hidden on forwarding.
We used this solution in some newsletter template as well my colleagues told me, so it should be save and work.
Hy,
I can see that you are wrapping the preheader in this HTML:
<span style=”display:none;visibility:hidden;font-size:1px !important;”>….</span>Newsletter systems also use preheader and can achieve that preheaders are not visible, maybe we can use this as some inspiration to improve this?
I saw something like this:
<!–[if !gte mso 9]>
<div style=”display:none;font-size:1px !important;color:transparent;line-height:1px;max-height:0px;max-width:0px;opacity:0;overflow:hidden;visibility:hidden;mso-hide:all;”>….</div>
<!–<![endif]–>In a first test of mine this seems to work with outlook!
Hi,
Any help on this problem ?
Hi @querysolutions,
Thank you, it is working now!
Sorry, I was redirected here wrongly. Please consider deleting the request as this was not meant for this plugin.
Forum: Plugins
In reply to: [Custom Post Type UI] Feature requeststhat worked great, is there also a way to automatically import this exported settings? say in a production environment?
Forum: Plugins
In reply to: [Custom Post Type UI] Feature requestsgreat thank you, I’ll have a look