Divi page formatting problem after CF7 styler upgrade

@energised Hi,

Can you confirm do you use more custom divi module? Can you share yours all plugin lists?

Also, did you try to roll back and use 3.25 divi version? After divi 3.26 there some issue with custom modules and we report that issue to divi. Hopefully, they solved.

But also you can use our old version from here: https://www.ads-software.com/plugins/cf7-styler-for-divi/advanced/

Select 1.0.2 and Download old version.

Thanks

Hi there,

Thanks for getting back to me.

I’m not sure if we are using any other Divi custom modules. Is there a way to check?
We are just using one of the pre-built Divi themes.
https://www.elegantthemes.com/blog/divi-resources/get-a-free-professional-digital-marketing-layout-pack-for-divi

The plugins currently on the site are:
Contact Form 7
Contact Form 7 Styler for Divi
WP Mail SMTP
Yoast SEO

I tried rolling back the Divi theme back to 3.26.5, however the problem was still there. It wouldn’t let me rollback any further.

However I downloaded your CF7 Styler plugin v1.0.2 and everything is now working again.

Currently v1.0.2 is working with Divi theme v3.27.4.

Is it ok to stay on v1.0.2 for the time being?

Many thanks

@energised No problem, v1.0.2 also a stable version but I will check that issue and if really an issue, I will solve it and update a new version soon.

If you give me screencast/video share where the issue then I will fix it quick.

But yes you can use now 1.0.2v. It does not create any issue if you do not use radio/checkbox filed.

Thanks

Hi
Thanks for letting me know and helping me with this issue.
I’ll get a video sorted to show you the issue.
Cheers

Hi
I have the same problem and reverted to v1.0.2
I don’t think I use other custom divi modules.
Sorry, I don’t have more informations to help you identify the cause.
Cheers

+1 on this. Rollback to 1.0.2 have sorted this issue. Not Custom Divi Modules. It’s just plain Divi site. Is it the plugin level change or from Divi side ?

@logixtree @aldelpech @energised

Can you share with me a screencast.. cause I am not able to identify the issue. Everything work for me is good.

Thanks

Hi,

We had the same issue with one of our websites.

I contacted Elegant Themes, and one of their developers fixed an issue in the code.

There seems to be 2 closing brackets missing- “]”.

This line has the issue (there are 2 of these lines)-
%1$s .dvppl-cf7-styler .wpcf7 input[type=tel,

Instead it should be-
%1$s .dvppl-cf7-styler .wpcf7 input[type=tel] ,

Here is the full code-

$advanced_fields[‘borders’][‘field’] = array(
‘label_prefix’ => esc_html__( ‘Field’, ‘dvppl-cf7-styler’ ),
‘toggle_slug’ => ‘form_field’,
‘css’ => array(
‘main’ => array(
‘border_radii’ => sprintf(‘
%1$s .dvppl-cf7-styler .wpcf7 input:not([type=submit]),
%1$s .dvppl-cf7-styler .wpcf7 input[type=email],
%1$s .dvppl-cf7-styler .wpcf7 input[type=text],
%1$s .dvppl-cf7-styler .wpcf7 input[type=url],
%1$s .dvppl-cf7-styler .wpcf7 input[type=tel],
%1$s .dvppl-cf7-styler .wpcf7 input[type=date],
%1$s .dvppl-cf7-styler .wpcf7 select,
%1$s .dvppl-cf7-styler .wpcf7 textarea’,
$this->main_css_element
),

‘border_styles’ => sprintf(‘
%1$s .dvppl-cf7-styler .wpcf7 input:not([type=submit]),
%1$s .dvppl-cf7-styler .wpcf7 input[type=email],
%1$s .dvppl-cf7-styler .wpcf7 input[type=text],
%1$s .dvppl-cf7-styler .wpcf7 input[type=url],
%1$s .dvppl-cf7-styler .wpcf7 input[type=tel],
%1$s .dvppl-cf7-styler .wpcf7 input[type=date],
%1$s .dvppl-cf7-styler .wpcf7 select,
%1$s .dvppl-cf7-styler .wpcf7 textarea
‘,
$this->main_css_element
),
),

‘important’ => ‘all’,
),
);

Thanks.

Hi,

Regarding my above comment, before making this adjustment to the code, our website broke when we updated Divi.

Once we made the tweak to the code and updated Divi again, everything worked fine.

Here is the path to the file where you need to adjust the code-
wp-content / plugins / cf7-styler-for-divi / includes / modules / CF7Styler / CF7Styler.php

Thanks.

Thanks @damienomahony that worked for me either!

Can confirm the above replace solution by @damienomahony fixed mine, too.

This should be fixed as a priority.

FYI, the 1.0.4 update broke this as well. Fortunately, the same fix still works.

BTW, your github link on the plugin home page goes to a 404 page.