I never said you should store builder layout data into post_content.
your previous post being
[...] It is entirely possible to create a layout builder without shortcodes or metadata.
i assumed that’s what you meant. If to store builder layout inside a single meta is not an issue then i have nothing to argue.
greenshady saidI thought the same since, in my post, i explained why i don’t think to store builder layout data into post_content is a viable solution and you’d still rely on meta for that.
I’m pretty sure people simply don’t read the words that I write sometimes.
To use post_content as builder storage and saving rendered markup into it as fallback for customers switching theme are not the same thing in my book: builder itself won’t need/use post_content to edit/render page content.
greenshady saidI don’t see post content as viable solution to store page builder structure, to me it has too many drawbacks. For instance, you would need to parse the markup and rebuild the builder layout each time the page is edited.
Sure. Essentially, the idea is to tie all the data back into
$post->post_contentwithout resorting to shortcodes.
Consider a block which pulls data from other posts, you would store the generated markup at the time the page is saved but changes made to those posts afterwards would be ignored unless the parsing/markup translation is done again each time the page is rendered.
Using a single meta to store the builder layout as a serialized object is simpler and requires no parsing (unlike markup/shortcode case).
Markup can be rendered into post_content as well when saving the builder layout, this way user switching theme won’t lose any content.
Page templates / custom metaboxes are enough to handle fixed/simple layouts but anything more complex/flexible would require either shortcodes or a page builder.
About meta vs shortcode as builder storage, the sc parser can’t handle nested macros (same name).
Nope, because a theme would most likely use custom templates for the plugin so css alone won’t give you the same look. To include custom template files won’t work as well because the custom markup needs the original theme css for layout/additional styling.
Got my answer via Payoneer live chat.
Since a recent billing address update, I’m having trouble using my Payoneer card online in about 95% of websites. I suspect its due to Mastercard’s pre-purchase card info validation process returning “invalid” due to address miss-match. The card works in 5% of sites, but I guess these don’t use that extra validation. Can you look into this issue please?
ps. I’ve recently sent you a direct email about the topic. Also tried using the Payoneer online contact form is not validating it’s fields correctly and can’t be sumbitted.
pps. Anyone else experiencing this problem?