hexagongirl

Thanks Jeff, that’s perfect. Sorry I didn’t manage to find that myself!

@jocce – not sure I understand – are you back to using individual blocks rather than the Media/Text block? If so, have you tried putting them inside an Atomic Blocks ‘Container’ block and then duplicating the Container?

I tried both this and using the Media/Text block; the latter is better – I can duplicate and retain the resized image, then resize if I need to. Using the Atomic Blocks Container block does work, although the formatting seems to mess up a bit in the admin panel – it’s not the easiest to use.

Apologies if I’ve misunderstood – perhaps someone else can help out?

See also here: https://github.com/WordPress/gutenberg/issues/11623

Hi Ruth! The Classic Editor plugin will override Gutenberg – so you’ll need to deactivate this to see the Gutenberg editor.

Ah yes of course! We need the section block – I think there is one planned, but probably not until after WP 5.0. Then you could put the text and image inside a section and duplicate the whole section.

I think https://atomicblocks.com/ does have a section block if you wanted to go that route.

Re. Media & Text – when I test it I get a blue dot drag-handle to the centre-right of the image and can resize (have to click on the image first)?

Have you seen the ‘Duplicate’ option? (When you hover over a block, you get an inline toolbar; at the end there is three dots (‘More Options’) – click on this -> Duplicate.

As an aside, you might also be interested in the ‘Media & Text’ block (if you’re not using that already) – although this aligns image/text vertically-centered. I think it may be a new addition (or at least I only noticed it recently!)

Just a quick update… I have migrated a few sites (with Custom Field Template) over to PHP7 today, after testing on localhost. They seem to be fine.

Looking at the code, the errors seem to relate to the ‘cftsearch’ shortcode function. I’m not using this at all, but my hunch is that if you were, that’s when you’d run into problems.

Ditto to the above. Is anyone able to confirm this is definitely a blocker to moving to PHP7 and not a false positive?

An update from the plugin author as to whether this will be fixed would be very much appreciated.

Thanks!

This caught me out too – I was expecting to see the Gutenberg editor on the standard New Post screen. Can we add an FAQ on the main plugin page?

“How do I get started using Gutenberg?”
“Install and activate the plugin. In the main left hand menu, click on ‘Gutenberg’ -> ‘New Post’ or take a look at ‘Demo’ to see what’s possible!”

Many thanks Justin. I just needed to add it to the cmb_init hook.

Or I wonder what the consensus would be for disabling featherlight for text-only links, where they are pointing to an external resource?

Just flagging up that I’ve also come across the same issue (again, Wikimedia links) – when crediting images via links at the bottom of a post or in an image caption.

I would second Collin’s suggestion for using an attribute or similar to disable the lightbox manually on specific links. I suspect some people have a use case for text links -> lightbox, so don’t imagine disabling them wholesale would be feasible.

Thanks!

• This reply was modified 8 years, 1 month ago by hexagongirl. Reason: Email follow-up

Hi Robert

Thanks so much for your reply and for the demo, just back to work now after Christmas, sorry for the slow reply.

Just had a look at the demo – that kind of looks similar to how I have things working with fluidvids. But in your demo, if I resize my screen (using Chrome developer tools) so that the video cover image fills the screen (say 646px x 362px), then click to play, once the video is playing I get black horizontal bars top and bottom, and the video itself is only half visible.

Can you see what I mean?

Thanks for your help,
Sarah

Hi WP Site Care, thanks for getting back to me.

Just checked out the issue on Github, the latest update is as follows:

The original author isn’t around much, I do most of the maintenance…

Which doesn’t bode too well! Do you know whether there’s any other work around? I’m using fluidvids, but this doesn’t seem to help…

Thanks

Thanks Ivan… yep, that’s the conclusion I came to as well. I believe what’s permitted in the standard WP post editor varies dependant on the current user role too.

I use wp_kses_post where appropriate for custom fields. I know in theory it’s not supposed to be used for escaping as the site can take a performance hit, but I’ve not noticed any major issues with it.