joycegrace

Yes, thank you. I saw these. I have been using Version 12.1. However, can you let me know if you will be adding the other styling suggestions noted above in my original request? Namely ul/ol/li tags and shortcodes? heading tags? HTML code editing?
I had missed the inline image option (duh), but have not tested it’s wrapping and alignment abilities.

• This reply was modified 6 years, 8 months ago by joycegrace.

Hello Marius! Thank you for this very quick reply.

Where do we enter the block title? I don’t seem to see that option for an H2 output. I also don’t see it in instructions… (if I’m blind and missed it, I apologize).

Side note: I looked more into the CSS for the accordion method, but that would require setting up form checkboxes and such in the HTML output, and that would have been an mess as far as an ‘easy’ way to set that up for ‘dummy proof’ back-end editing (like if a client wanted to edit). So, I went back to a js plugin as a solution…

It turns out, by accident, today I just happened to try entering a shortcode in the question field, which gave me the proper output of an H2, using the collapse-o-matic plugin.

So for example, [expand title=”My amazing qustion?” tag=”h2″]

And then adding [/expand] at the end of the question. It also did the expand/collapse accordion thing.

Of course, the problem with doing that is that now the structured data name includes the shortcode characters, which won’t read nice on search results pages. Can’t imagine that will help ranking either… (it does validate though…)

In case anyone is wondering, I am able to enter that shortcode into the answer itself and it appears fine as an h2 with expand/collapse, but still gives the problem of the shortcode showing up in the schema markup answer.

Now, the above issue probably has to do with the fact I’m using a shortcode for the js, and not some other method… but still, it would be nice if the FAQ block could accept more common WP inputs, or more HTML options, at least.

I’m also having a lot of trouble with formatting, such as adding list styles, bold text, or images within paragraphs. (I’ll write a separate post on this since it’s getting off topic).

Any change I try to make by switching to HTML, renders that whole block no longer editable, and no longer able to convert back to an FAQ block. Even if I click on “resolve” after the fact and then “Convert to blocks” – it just goes back to an HTML block or a shortcode block. It doesn’t seem to ‘understand’ that this was the FAQ block formerly.

If click the “undo” button in the Block Editor twice, after clicking to “resolve” and then “convert to blocks”, it goes back to the FAQ block, without my HTML changes of course.

But leaving it as HTML is very difficult to make updates if a client wanted to do it, who does not know HTML.

So I’m in a dilemma again.

I also have revisions turned to 0, because I want to keep the database light. So right now I’m not sure how the revisions option can help me (I’m not able to try your method, but my guess is that in the interim, it would still be hard for the client to update, and would lose our later content changes if we went to an older revision that used the FAQ block).

Anyway… I’m currently at a loss. This is a big toss up for us. Do we manually set up structured data and forgo the Yoast FAQ block method, or wait for the Yoast code to update the strong tag to an h2, or just use Yoast’s block and lose our heading tags… this is a really hard decision to make.

Thank you for all your work in making this feature free for everyone, however.

still brings up errors

You were right and I was wrong, sorry Steve. Your solution does solve my problem. Thank you.

Well, I’m afraid to use that if it’s not been tested and confirmed. Anyone know if PHP 7 errors and warnings will be fixed soon?