[Sotiris]

Same problem here. I had to switch to 1.63 manually to get it working.

[Sotiris]

Great! That did the trick!

I could not find another way to override this properly but I did not want to edit core Theme files and have to do it again after each update.

Thanks a lot.

[Sotiris]

This reply has been marked as private.

[Sotiris]

Positive. I have v1.40 installed and WP 4.2.3 (multisite)

I think there are differences between the two stylesheets and that is causing the issues. My main concern is the paddings applied to the containers that misbehave. Please try to set some row paddings and use an override class (pt0) and then check the inner spb_content_element. It seems as if the paddings apply to two different cotnainers.

[Sotiris]

It actually took me these corrections to make the buttons work

a.sf-button.sf-icon-reveal.large {
    padding: 0;
}

a.sf-button.sf-icon-reveal i {
    width: 60px;
}

a.sf-button.large.sf-icon-reveal i {
    line-height: 16px;
}

a.sf-button.sf-icon-reveal.large:hover span.text {
    transform: translateX(0px);
}

[Sotiris]

Sorry to hijack this topic (too) but I have spent 10 hours + trying to fix things up too.

It seems like the latest update has introduced some bugs to the page builder content elements.

For example you set paddings with the slider for a “Row” and it seems like that there are two containers that settings (such as override classes pr0, mb0, etc) are applied too.

For example I set the vertical padding for a row to 70px:

The “.spb-row-container” inherits the override class “pb0” but then the “.spb_content_element” still has 70px top and bottom paddings. The same happens with most elements.

Another “bug”:

The row class always has a 15px padding and had to resort to this to get rid of that
.row {
padding-left: 0!important;
}

Yet another one:

The toggles – accordions + signs have an “atelier” font assigned to them.

Had to resort to:

.spb-row-expand-text span::before {
content: “+”;
font-family: “SSGizmo”;
transform: translate3d(0px, 5px, 0px) rotate(0deg);
}

The icon-boxes needed fixes too and the Icon Reveal buttons (large) are messed up as well (additional padding breaks them).

I have noticed the a lot of the intruding styling comes from page-builder.css file.

Please have a look at this since correcting a 100+ pages site ain’t easy.

[Sotiris]

The same for me. Messed up!

Is there a fix on the way or should I dig into CSS?

Attachments:

You must be logged in to view attached files.

[Sotiris]

Great response as always.

Thanks a lot to all of you.

[Sotiris]

It seems that I had not payed attention to Templetera. It supports what you say so I will put it on my list to buy and check.

[Sotiris]

This reply has been marked as private.

[Sotiris]

Templatera does not produce a single shortcode the same as SPB sections do I think.

For example:

A) I built an SPB section that I need to use its single line shortcode.
B) I add this SPB section as an element to a temporary page and then switch to classic editor view.
C) I see a short shortcode with the SPB section ID
D) I can copy this shortcode to the private content container once and then each time I edit this SPB section the private page displays the new content as well.

The advantage is that essentially I can use the Swift Page Builder within the private content container while otherwise it would not be possible. You see it is not a standard custom post type and uses its own text editor that accepts html and shortcodes.

I can not achieve this with Templatera and have dynamic content editing capability at the same time since a) it needs VC to work (can’t in this post type) and b) it does not produce a single shortcode with the id of the section so you have to copy the whole new content again in the private container.

It is just a way to save a page template just like you do with the “Save Template” feature in Swift Page Builder since VC does not offer this on its on. Damn they do not even offer the option to save an element. All in all, SPB wins hands down here and it is also much more efficient and fast in doing so.

Simply put SPB works seamlessly while VC is a hassle and a lot slower in general in my site. I only use it for some of the fancy addons, not for post and page building – just certain elements.

Some features that would be nice to see in Swift Page Builder are:

A) The ability to add page specific CSS straight into the page

B) Independent left-right margin/padding settings for each element such as VC (top-bottom is not needed as there are many ways to set it). I am using the override classes many times but these are only for zeroing margins/paddings. Another workaround is using these classes selectively in a column (i.e. left) and then in an inside element (i.e. right) to define different paddings left and right. Nonetheless, even the per page custom css option would help a lot here rather than going to the main theme Custom CSS editor for small things like the above.

I can’t think of anything else right now but will certainly add more feedback if something comes up.

[Sotiris]

After a lot of tweaking and testing I have made a page that consists of both VC and SPB elements working perfectly now.

As I said above the trick is to use Swift Page Builder as normal but for every VC element you want to insert in the page/post it has to be in text shortcode mode. You can create whatever you want on a temporary page with VC, then switch to classic – text mode and copy all the text shortcodes to a text block in your SPB page. It works like a charm but in order to edit it you need to either maintain the original VC page (I don’t) or copy back the text shortcodes and edit it with VC elsewhere.

One other idea is to use SPB sections with VC and save them for easy re-editing in the future but that would be far easier if categories get supported (SPB sections) so the area does not get cluttered.

This way you get the best of both worlds – SPB as the main editor which I prefer and the ability to use the fancy VC addons.

[Sotiris]

Yes just to be able to organize the view as the number of sections increases. It should not be hard to implement. I already can assign categories to SPB sections through a plugin I use to organize pages but there is no drop down menu in the backend list view.

I am also thinking of using SPB sections for Visual Composer elements within Swift Page Builder pages. See my other post here

[Sotiris]

Right now since both builders can be enabled the user has to create VC elements in another page using VC, then switch to classic and text mode and copy the end result so it can be pasted into an SPB Text block. You can always go back and re-edit visually the shortcode. (It also works vice-versa SPB to VC).

The only way I can imagine, that could allow the creation and visual editing of VC elements within SPB would be to contact the authors of thos VC add-ons and check with them if they could add support for SPB.

Other than that I can’t think of anything else. It is not too much trouble to create the elements in another temporary page though only used for VC element editing. You don’t need to save the temp page since the text shortcodes can always be copied back to another temp page and be edited again. A bit of hassle yes but it adds so many elements to the mix (VC addons) that it is worth it.Think of it as an independent Shortcode generator for SPB Text blocks.

[Sotiris]

It is actually working! I pasted a VC element (from ultimate addons) in text mode within a SPB text block and it displays fine.