[Resolved] Oxygen 2 Builder

[Author]

Posts

[raulE-2]

Hi!

I have already asked some help to Oxygen 2 Builder support, but if add any tutorial or useful link about integration with Oxygen Builder, it would be nice.

I'm having some difficult to understand how to insert Types custom fields in my designs.

Thank you

[Nigel]

Hi Raul

I've just got a copy of Oxygen 2 to do some testing, so give me a little time to play with it and I'll come back to you.

What I can say is that we don't currently have any integration with Oxygen, but are looking into it, we know the developers well from WP All Import.

[raulE-2]

Thank you Nigel

I have installed Oxigen recently and I also knwo WP All import.

This new builder seem to have lot of potential for webdesignrs and it would be very cool if we clould easaly integrat it with types and views 😉

[Nigel]

Hi Raul

So, I played around with Oxygen and Toolset together, using a default Oxygen install with the atomic site template.

As you will know, Oxygen doesn't use your theme at all (it doesn't even load the functions.php file), and doesn't use the theme templates such as single.php.

That means you are not going to be able to create Views Content Templates to design your single posts in the same way as you can with other page builders.

However, I found that the template Oxygen uses for single posts which includes the post body seems to run the_content filter before outputting that content.

What that means is that you can still create Views Content Templates for single custom posts, and when you use Oxygen to create a template for that post type, the content area of the page is still replaced by the Views Content Template, much like it would be in a regular theme.

So the Content Template can output your custom fields, as required.

However, I also checked to see whether it would be possible to insert custom fields in other areas of the site, and it appears not.

The text (and rich text) modules do not parse shortcodes, so you couldn't copy and paste in a Views shortcode or Types shortcode.

But you can place WordPress widgets arbitrarily in your pages and templates designed with Oxygen, so you can add a text widget and use shortcodes within it (but you will need to enter them manually, there is no Fields and Views button to insert them).

Likewise you can use Toolset's WP Views widget to insert a View.

You can also use Oxygen's custom field module inside the WordPress > Dynamic Data section (recall that Types fields are stored with a 'wpcf-' prefix.

So, in sum, without any formal integration it looks like you can already do quite a lot with Oxygen 2 and Toolset together.

I'll raise this with my colleagues to see if we might add more options for inserting Types fields. I also haven't tested this with other Toolset plugins than Types and Views, I expect there may be issues with things like edit Forms, for example.

[Nigel]

Quick update.

I tested edit Forms (which are problematic with other page builders) and they work fine out of the box, which is good news.

[raulE-2]

Nigel

Thank you for your reply.

But when I try to insert a types custom field there is any 'wpcf-' option in the drop down. The only thing related is 'types_field_group_purpose'.

For example in the video module I can get dynamic data. I put this for a field with slug 'video-evento'. But its not working:
[oxygen data='meta' key='wpcf-video-evento']

Can you help me?

[Nigel]

Hi Raul

That's a problem with Oxygen.

I did a quick test where I created a Types video embed field on a custom post type and added a youtube link.

On the Oxygen template I inserted a video module, and used the dynamic data dropdown to find the custom field (wpcf-youtube-link in my case), saved the template and then viewed the post on the front-end, where it still showed the default Rick-roll video.

I repeated this with the Hello World post and the blog post template (having manually added a wpcf-youtube-link custom field to the post), and this time it worked correctly.

It seems like the Oxygen video module fails with custom post types, and to confirm that I used a non-Toolset plugin to create a custom post type, manually added a wpcf-youtube-link custom field, and it also did not work.

You'll need to report this kind of thing to Oxygen.

I would point out that in half an hour or so of testing Oxygen generated 1Mb worth of error messages in the debug logs, so I would expect to see lots of issues, I'm not really sure it was ready to move out of beta.

[raulE-2]

Thank you. I think you are right... the builder wasn't ready to move out of beta 🙁

[sridharK]

"The text (and rich text) modules do not parse shortcodes, so you couldn't copy and paste in a Views shortcode or Types shortcode."

We can select any string inside those elements, then click on Insert Data button at the top > PHP Function Return Value > Function Name.

A code snippet can be added prior to define a function that outputs the shortcode.

[Beda]

HI @sridhark

I have seen that you contacted the Oxygen Builder Admins in Facebook and shared this thread, as well as it seems you have news about the issue here.

I don't think it helps anyone sharing a Thread with problems over a month old, nor to follow up on one.
Please, if you see issues with Oxygen - report them to their Developers, as Louis correctly states, they will fix them!
If you instead see issues wit Toolset, please open a new thread, we will help.

It is however not Toolset's Support primary goal to debug and warn other 3rd Party Developers about errors in a Beta Release, this while it still was in beta, or to steer conflicts when we mention that there are issues in a plugin.

I think the right move, in a perfect worlds, would be us to give them (Oxygen) a heads up, but that did not happen, also because it is not something we cover in Toolset Support - I apologize that this did not happen, I will try to look out for such issues in future, but please acknowledge that we Support Toolset - not other plugins.
https://toolset.com/toolset-support-policy/

This does not mean we reject, or do not help others.
On the contrary, I today contacted a colleague of me that works at Toolset so to refresh our contacts to Oxygen guys and girls once more (we already worked in past on Oxygen beta and now 2.0 compatibility - for example for Forms).

I invite you to open a new ticket with any issue of Toolset or as well related to your news above.

Rest assured that we always will try to resolve issues, as well as collaborate with other Plugin authors!
If you let the Developers at Oxygen know that you'd like to use Toolset with, I am sure we can even be more productive together.

[Beda]

hidden link

🙂