Skip Navigation

[Resolved] Background colors & images not displaying

The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.

This thread is resolved. Here is a description of the problem and solution.

Problem: CSS styles applied to a WPBakery row module on a Post or Page are not copied over into a Content Template created with WPBakery when I use the shortcode markup generated by disabling WPBakery on the Post or Page.

Solution: The error seems to happen when copying a row styled with row options, from a single post or single page design, into the Content Template of a View. This is because Page Builder saves some of the row options information in the database alongside the original post as a postmeta field. When you copy + paste the shortcodes to another View, that original information is not migrated. Then the problem occurs.

In order to bring that information over into the View's Content Template, we would need to know programmatically which Views and Content Templates correspond to which Page row designs. That would be a massive undertaking. I could file this as a Feature Request, but frankly I do not think it will be accepted by our developers. I think they will suggest instead that row options are applied manually in the new Content Templates. Drop the CSS from any shortcodes migrated into Content Templates, and add the styles manually in the CT builder.

This support ticket is created 6 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 5 replies, has 3 voices.

Last updated by Christian Cox 6 years, 10 months ago.

Assisted by: Christian Cox.

Author
Posts
#621016

Lee
Views Content Template Code.png
Matching View Front End (2 Loop Items).png

Hi, I am trying to create a simple view with a block colour background. The 1st link is the Toolset View, the 2nd link is the layout I have designed for the view using a WordPress page and WPBakery Page Builder. As soon as I copy the layout into a toolset view, various random css issues occur.

Any background images or colours just dissapear (even though they are visible in the content template code)
Random margins & padding appear (that do not match the code in the content template)

Link to View: hidden link
Link to design: hidden link

I have even created a content template that is just a single row with a heading and background color. The background colour just doesn't display at all.

I have tried deactivating all plugins and this does not resolve the issue.

Thanks
James

#621142

Hi, I see what you mean. I'm able to replicate a similar issue in a local testing environment, so I need to escalate this to my 2nd tier support team for some additional investigation. Please stand by and I will update you when I have some information to share.

#622487

Lee

Hi Christian, have you made any progress?

Thanks
James

#622607

Hi

I was not able to replicate this.
Christian will eventually interact with you about this detail.

I wanted to update you on another issue.

The WP Bakery Plugin presents an issue with PHP 7.2 and above:

( ! ) Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /Applications/MAMP/htdocs/stable/wp-content/plugins/js_composer/include/classes/core/class-vc-mapper.php on line 111

hidden link

Would you mind to inform the Developers of the plugin about this?
I am sure they'll appreciate the heads up.

Meanwhile, once Christian will provide me with the required details to replicate the issue I will proceed working on this.

Right now I was not able to see this problem on a clean install.

#622649

Hi James, as Beda mentioned some of us are unable to replicate the issue so I'm working with the rest of the team to try to pin down the problem and understand why it is inconsistent across our environments. I will update you as soon as I have some information to share.

#623003

First, WP Bakery Page Builder uses the function "each" in PHP, which has been deprecated as of PHP 7.2. This produces an error on servers running PHP 7.2 or later. In my local tests, I was running PHP 7.1.12, so I did not see this error but other testers did.

With PHP version differences aside, the error seems to happen when copying a row styled with row options, from a single post or single page design, into the Content Template of a View. This is because Page Builder saves some of the row options information in the database alongside the original post as a postmeta field. When you copy + paste the shortcodes to another View, that original information is not migrated. Then the problem occurs.

In order to bring that information over into the View's Content Template, we would need to know programmatically which Views and Content Templates correspond to which Page row designs. That would be a massive undertaking. I could file this as a Feature Request, but frankly I do not think it will be accepted by our developers. I think they will suggest instead that row options are applied manually in the new Content Templates. Drop the CSS from any shortcodes migrated into Content Templates, and add the styles manually in the CT builder.

The forum ‘Types Community Support’ is closed to new topics and replies.