yootheme / example-element Goto Github PK

Hi

Code example not work on Wordpress
Element not show in Builder

Thank you

The docs and the readme here don't make clear what the new content.php is for. It seems to be a duplicate of part of template.php... but I have no idea what I'm supposed to do with it. It's never mentioned in the docs or in the readme except that it "renders the content which is saved in the page"... but what's the difference between that and rendering "the actual front-end markup"?

Will this be updated for YOOtheme 2.x with an example of a dynamic content source?

I created a custom builder element following the docs, and recently wanted to rename one of my props, so I added an 'updates' hook like this to the element.php file in the custom element's directory do so:

<?php

return [

    'updates' => [

        '1.1.2' => function ($node, array $params) {

			if (isset($node->props['tag_slug'])) {
				$node->props['filter_tag_slugs'] = $node->props['tag_slug'];
				unset($node->props['tag_slug']);
			}

        },

    ],

];

However when I load pages that already had the custom element on them (with a value in the old prop named tag_slug, they don't get seem to be getting the new prop name. It seems this hook isn't firing at all. What am I doing wrong?

The 1.1.2 version number is my child theme's version number, but I assume that part doesn't matter?

I'm running Yootheme 1.20.6 as the parent theme.

headline says it all.

I've created child theme as discribed in docs.

My child theme folder is yootheme_vbik

So I created builder folder in child theme and extracted this repo in it

So my structure looks like this:

But if I'll try to create new element - I don't see any icon on it

And in console I see wrong way to SVG icon

the true way is .../templates/yootheme_vbik/builder/pro-element/icon.svg

So, how to fix it?

Thank you wf!
Unfortunately, your component exceeds the limitations of our migration script.
We will update the documentation and script to reflect those limitations.

The problem is with the functions in the enable (and show) fields. Our script attempts to convert those to the new expression syntax, though it will fail with more complex examples. I'll change the script to not throw an exception, but instead, log helpful warnings to migrate those fields manually after the conversion.

Cheers!

JM