How-to questions and documentation

[JiveDig]

I've been lurking/following this class for a while and gave it a try today. Thanks for sharing! It's pretty straightforward and cool but I'm wondering if there is any official documentation that I missed? I've just been digging through the code and the examples.

My biggest concern is over a block preview in the editor. Is it not currently setup to have a preview? I'm wonder if thing widget_ops output argument can take a callback/function so we can return the actual block content in the editor as well?

[pol76]

Hi Jivedig, sorry for missing your request, I've asked the developers to follow up.
Thanks for your patience,

[Stiofan]

Hi @JiveDig,

Do you mean the hover preview or the actual output when editing a block?

This class was originally built only for our internal use and as such we just used code comments inside the class instead of documentation.

If we are talking hover preview then that was not an option when we originally built this class and when I last looked into it there was a bug where if previewed it would then not render initially when added. However if this is what you mean then I can check this again.

If you mean the edit block preview then this can be output in a few ways, usually this will just work out the box but if you need to check if you are in a editor preview then you can use $this->is_preview() and output something different .

Thanks,

Stiofan

[JiveDig]

Hmmm, I don't think I'm looking for either. In the editor I see my block settings but I do not see any of my output/HTML. I don't need anything different in editor vs front end, I was just wondering why I didn't see any of the actual block output.

[Stiofan]

You should, are you returning the content in the output() function or echoing it?
You can install this whole repo as a plugin and activate it, you can test the hello world example.