Search Results for 'contact form 7'

[Gilbert C]

Gilbert C

#261545

Did not have time to debug but reverting to WP 5.5, Kadence theme V1.9.5. Kadence premium extension V.0.9.0, Kadence blocks V.1.9.5 and Kadence Blocks PRO v.1.4.16 solved the issue.

Yoast Seo , Redirections, Contact Form 7, Ecwid e-commerce plugins installed
No fancy plugins installed.

[Gilbert C]

Gilbert C

#261545

Did not have time to debug but reverting to WP 5.5, Kadence theme V1.9.5. Kadence premium extension V.0.9.0, Kadence blocks V.1.9.5 and Kadence Blocks PRO v.1.4.16 solved the issue.

Yoast Seo , Redirections, Contact Form 7, Ecwid e-commerce plugins installed
No fancy plugins installed.

[alex]

alex

#260879

Hi I have placed a contact form in a modal pop up. I would like to have the image at the top of the pop up go right up to the edges of the box (no white space around left right and top) without touching the position of the form itself. Perhaps you can suggest some CSS to achieve this result?

[alex]

alex

#260879

Hi I have placed a contact form in a modal pop up. I would like to have the image at the top of the pop up go right up to the edges of the box (no white space around left right and top) without touching the position of the form itself. Perhaps you can suggest some CSS to achieve this result?

[Nick Spence]

Nick Spence

#260396

Hello Ben,

Thanks for the reply.

1) When do you expect to release the Kadence theme with this hook ?
In the meantime I created a Kadence-child theme, copied over template-parts/content/single-entry.php and added ‘in_same_term’ => true, at line 47. This works and gives me a temporary workaround.

2) I see what you mean, and added the search bar. Thanks.

3) The contact widget is the right idea but doesn’t have the icons I am looking for so I will probably go back to some raw HTML code.

4) While setting up the kadence-child theme I tried to use the Import/Export function, but the import failed with this error:

Fatal error: Uncaught Error: Call to undefined method Kadence_Starter_Templates\Customizer_Import_Export::sideload_image() in /homepages/.../wp-content/plugins/kadence-starter-templates/inc/class-import-export-option.php:358 Stack trace: #0 /homepages/.../wp-content/plugins/kadence-starter-templates/inc/class-import-export-option.php(307): Kadence_Starter_Templates\Customizer_Import_Export::import_images(Array) #1 /homepages/.../wp-content/plugins/kadence-starter-templates/inc/class-import-export-option.php(176): Kadence_Starter_Templates\Customizer_Import_Export::import_data(Object(WP_Customize_Manager)) #2 /homepages/.../wp-includes/class-wp-hook.php(287): Kadence_Starter_Templates\Customizer_Import_Export::import_export_requests(Object(WP_Customize_Manager)) #3 /homepages/.../wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NUL in /homepages/.../wp-content/plugins/kadence-starter-templates/inc/class-import-export-option.php on line 358

I used the https://wordpress.org/plugins/customizer-export-import/ plugin and it worked. Both export functions (Kadence & the plugin) produce exactly the same file, so the problem seems to be with the Kadence Import. I would upload the 26KB dat file, but the forum uploaded won’t let me (even if I change the file name suffix). I can give you more information if you need it.

Regards,
Nick

[phil2]

phil2

#259469

Thanks Hannah, that’s a much more elegant solution!

I see that the footer row can’t be defined as “full width” due to the container width set to #conainerfooter.container set to 1170px. I’ve set that to 100% to match the current site, but it still isn’t reaching across. Please can you help me get the new site to match the original?

1. Left and right margin on “We can help…”. This row needs to stretch edge to edge.

2. Likewise the next row containing map and contact form, edge to edge, please.

3. The next 2 rows need to be back to normal content width (1170px). I’ve tried various settings on the rows but with no success.

4. Vertically, remove all the additional gaps. On the original site, these rows are all butted up together with no vertical gaps.

5. Remove the additional space after the final row.

6. Also, I can’t see a way to include the menu “footer menu” as a widget in the re-usable block. Does this require another plugin or is there a way to pull-in this menu which I have already setup?

Many thanks fro all your help,
Phil.

[StEAS]

StEAS

#259331

This reply has been marked as private.

[John]

John

#258502

When using the Ascend “Contact us” page contact form, the email delivered to the MTA uses the email address entered by the customer as the FROM address. If the customer’s email uses the yahoo.com domain name AND the recipient is using a gmail mailbox, then gmail will reject the incoming mail due to DMARC violations. Here is typical rejection message in the postfix mail log. Again, it is the receiving system (gmail) that is creating the rejection.

B83413F8EF: to=<[email protected]>, relay=aspmx.l.google.com[209.85.235.27]:25, delay=1.2, delays=0.1/0.02/0.4/0.68, dsn=5.7.26, status=bounced (host aspmx.l.google.com[209.85.235.27] said: 550-5.7.26 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.26 DMARC policy. Please contact the administrator of yahoo.com domain 550-5.7.26 if this was a legitimate mail. Please visit 550-5.7.26 *Login to see link to learn about the 550 5.7.26 DMARC initiative. l2si3780362otf.316 - gsmtp (in reply to end of DATA command))

I have now tested 2 different cases and see the same results in both cases:

Case 1: Mail delivered directly by postfix on hosting server
Case 2: Mail relayed by Postfix to commercial SMTP service (SMTP2Go in my case)

I think that this sort of problem would be solved if the email send by the contact form used the recipient’s email address as both FROM and TO.

[John]

John

#258502

When using the Ascend “Contact us” page contact form, the email delivered to the MTA uses the email address entered by the customer as the FROM address. If the customer’s email uses the yahoo.com domain name AND the recipient is using a gmail mailbox, then gmail will reject the incoming mail due to DMARC violations. Here is typical rejection message in the postfix mail log. Again, it is the receiving system (gmail) that is creating the rejection.

B83413F8EF: to=<[email protected]>, relay=aspmx.l.google.com[209.85.235.27]:25, delay=1.2, delays=0.1/0.02/0.4/0.68, dsn=5.7.26, status=bounced (host aspmx.l.google.com[209.85.235.27] said: 550-5.7.26 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.26 DMARC policy. Please contact the administrator of yahoo.com domain 550-5.7.26 if this was a legitimate mail. Please visit 550-5.7.26 *Login to see link to learn about the 550 5.7.26 DMARC initiative. l2si3780362otf.316 - gsmtp (in reply to end of DATA command))

I have now tested 2 different cases and see the same results in both cases:

Case 1: Mail delivered directly by postfix on hosting server
Case 2: Mail relayed by Postfix to commercial SMTP service (SMTP2Go in my case)

I think that this sort of problem would be solved if the email send by the contact form used the recipient’s email address as both FROM and TO.

[John]

John

#258483

I have a site using Ascend Premium. I tested the “Contact Us” form using a customer email address on the yahoo.com domain name. My email log indicates that the mail sent to the administrator (gmail.com) was bounced because of DMARC policy set for the yahoo.com domain name:

Oct 10 09:49:25 vu5 postfix/smtp[654433]: DA24C3EA3C9: to=<[email protected]>, relay=gmail-smtp-in.l.google.com[64.233.179.26]:25, delay=0.18, delays=0.05/0/0.08/0.06, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[64.233.179.26] said: 550-5.7.26 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.26 DMARC policy. Please contact the administrator of yahoo.com domain 550-5.7.26 if this was a legitimate mail. Please visit 550-5.7.26 https://support.google.com/mail/answer/2451690 to learn about the 550 5.7.26 DMARC initiative. x7si6539721oia.130 - gsmtp (in reply to end of DATA command))

I think the “from” address is still being configured as the customer’s email address. Because of this, a certain percentage of mails sent by the “Contact us” form are being bounced.

[Griffin Stewart]

Griffin Stewart

#257240

Hi Ben and team. I am wanting a different menu depending on the page the user is viewing. I will include code below on how we did it via Beaver Build in case it helps, but am wondering if there is ay way with Kadence Theme to do it via a custom header/menu only on certain pages that does not require custom code. If not, no worries, but thought I would check. Thanks.

One idea would be to maybe use elements and then load the menu as an element on certain pages and disable the normal menu via the page settings. Is that a good idea? Any performance concerns vs custom PHP?

`<?php
​
/**
* Helper class for theme functions.
*
* @class FLChildTheme
*/
final class FLChildTheme {
​
/**
* @method styles
*/
static public function stylesheet() {
$css_ver = filemtime( get_stylesheet_directory() . ‘/style.css’ );
echo ‘<link rel=”stylesheet” href=”‘ . FL_CHILD_THEME_URL . ‘/style.css?ver=’ . $css_ver . ‘” />’;
}
​
/**
* Renders the markup for the fixed header.
*
* @since 1.0
* @return void
*/
static public function fixed_header() {
​
// Prevet showing fixed header on the Logo Page tempale
if ( is_page_template( ‘page-templates/page-logo.php’ ) ) {
return;
}
​
$header_layout = FLTheme::get_setting( ‘fl-fixed-header’ );
$header_enabled = apply_filters( ‘fl_fixed_header_enabled’, true );
​
if ( ‘visible’ == $header_layout && $header_enabled ) {
get_template_part( ‘includes/fixed-header’ );
}
}
​
/**
* Renders the markup for the main header.
*
* @since 1.0
* @return void
*/
static public function header_layout() {
$header_layout = FLTheme::get_setting( ‘fl-header-layout’ );
$header_enabled = apply_filters( ‘fl_header_enabled’, true );
​
if ( ‘none’ != $header_layout && $header_enabled ) {
if ( is_page( array( ‘cart’, ‘checkout’ ) ) ) {
get_template_part( ‘includes/nav-without’ );
} else {
get_template_part( ‘includes/nav-‘ . $header_layout );
}
}
}
​
/**
* Regiser the menu in the main header.
*
* @since 1.0
* @return void
*/
static public function register_menus() {
​
unregister_nav_menu( ‘header’ );
​
register_nav_menus( array(
‘back-to-top’ => esc_html__( ‘Back-To-Top Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘customer’ => esc_html__( ‘Customer Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘sale’ => esc_html__( ‘Sale Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘non-sale’ => esc_html__( ‘Non-Sale Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘affiliate’ => esc_html__( ‘Affiliate Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘sale-party’ => esc_html__( ‘Sale Menu – Party Page’, ‘bb-theme-5dd’ ),
) );
}
​
/**
* Renders the menu in the main header.
*
* @since 1.0
* @return void
*/
static public function header_menus() {
​
$header_layout = FLTheme::get_setting( ‘fl-header-layout’ );
​
if ( is_page_template( ‘page-templates/page-logo.php’ ) ) {
/*
* If page template is “Logo Page”, show no menu
* @since 1.0
*/
return;
}
elseif ( is_page( array(
52426, // affiliate-area/about
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘back-to-top’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page( array(
115611, // vcb-iii-party
115882, // vcb-iii-kickstart
142873, // vcb-iv-party
147539, // vcb-iv-sumo
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘sale-party’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page( array(
142766, // vcb-iv-kickstart
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘blank-menu’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘customer’ navigation menu
* @since 1.0
*/
array(
52266, // my-account
52475, // my-account/faqs/
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘customer’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘affiliate’ navigation menu
* @since 1.0
*/
array(
38, // affiliate-area
52480, // entry
52456, // affiliate-area/contact/
52473, // affiliate-area/faqs/
52434, // affiliate-area/products/
60177, // affiliate-area/resources/
88825, // my-profile
142212, // affiliate-area/resources/smart-goals/
124419, // affiliate-area/products/
217193, // affiliate-area/resources/difference-makers/
217585, // partner-onboarding-2/
216459, //partner-onboarding/
)
)
|| ‘contributor’ === get_post_type()
) {
wp_nav_menu( array(
‘theme_location’ => ‘affiliate’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘sale’ navigation menu
* @since 1.0
*/
array(
52353, // iii
52533, // bb-i
52829, // bb-i-1
52910, // bb-i-2
52958, // bb-i-3
52981, // bb-i-4
53001, // bb-i-5
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘sale’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
else {
wp_nav_menu( array(
/*
* If page slug is not above, use ‘non-sale’ menu
* @since 1.0
*/
‘theme_location’ => ‘non-sale’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
}
​
}`

[Griffin Stewart]

Griffin Stewart

#257240

Hi Ben and team. I am wanting a different menu depending on the page the user is viewing. I will include code below on how we did it via Beaver Build in case it helps, but am wondering if there is ay way with Kadence Theme to do it via a custom header/menu only on certain pages that does not require custom code. If not, no worries, but thought I would check. Thanks.

One idea would be to maybe use elements and then load the menu as an element on certain pages and disable the normal menu via the page settings. Is that a good idea? Any performance concerns vs custom PHP?

`<?php
​
/**
* Helper class for theme functions.
*
* @class FLChildTheme
*/
final class FLChildTheme {
​
/**
* @method styles
*/
static public function stylesheet() {
$css_ver = filemtime( get_stylesheet_directory() . ‘/style.css’ );
echo ‘<link rel=”stylesheet” href=”‘ . FL_CHILD_THEME_URL . ‘/style.css?ver=’ . $css_ver . ‘” />’;
}
​
/**
* Renders the markup for the fixed header.
*
* @since 1.0
* @return void
*/
static public function fixed_header() {
​
// Prevet showing fixed header on the Logo Page tempale
if ( is_page_template( ‘page-templates/page-logo.php’ ) ) {
return;
}
​
$header_layout = FLTheme::get_setting( ‘fl-fixed-header’ );
$header_enabled = apply_filters( ‘fl_fixed_header_enabled’, true );
​
if ( ‘visible’ == $header_layout && $header_enabled ) {
get_template_part( ‘includes/fixed-header’ );
}
}
​
/**
* Renders the markup for the main header.
*
* @since 1.0
* @return void
*/
static public function header_layout() {
$header_layout = FLTheme::get_setting( ‘fl-header-layout’ );
$header_enabled = apply_filters( ‘fl_header_enabled’, true );
​
if ( ‘none’ != $header_layout && $header_enabled ) {
if ( is_page( array( ‘cart’, ‘checkout’ ) ) ) {
get_template_part( ‘includes/nav-without’ );
} else {
get_template_part( ‘includes/nav-‘ . $header_layout );
}
}
}
​
/**
* Regiser the menu in the main header.
*
* @since 1.0
* @return void
*/
static public function register_menus() {
​
unregister_nav_menu( ‘header’ );
​
register_nav_menus( array(
‘back-to-top’ => esc_html__( ‘Back-To-Top Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘customer’ => esc_html__( ‘Customer Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘sale’ => esc_html__( ‘Sale Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘non-sale’ => esc_html__( ‘Non-Sale Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘affiliate’ => esc_html__( ‘Affiliate Menu’, ‘bb-theme-5dd’ ),
) );
register_nav_menus( array(
‘sale-party’ => esc_html__( ‘Sale Menu – Party Page’, ‘bb-theme-5dd’ ),
) );
}
​
/**
* Renders the menu in the main header.
*
* @since 1.0
* @return void
*/
static public function header_menus() {
​
$header_layout = FLTheme::get_setting( ‘fl-header-layout’ );
​
if ( is_page_template( ‘page-templates/page-logo.php’ ) ) {
/*
* If page template is “Logo Page”, show no menu
* @since 1.0
*/
return;
}
elseif ( is_page( array(
52426, // affiliate-area/about
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘back-to-top’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page( array(
115611, // vcb-iii-party
115882, // vcb-iii-kickstart
142873, // vcb-iv-party
147539, // vcb-iv-sumo
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘sale-party’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page( array(
142766, // vcb-iv-kickstart
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘blank-menu’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’,
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘customer’ navigation menu
* @since 1.0
*/
array(
52266, // my-account
52475, // my-account/faqs/
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘customer’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘affiliate’ navigation menu
* @since 1.0
*/
array(
38, // affiliate-area
52480, // entry
52456, // affiliate-area/contact/
52473, // affiliate-area/faqs/
52434, // affiliate-area/products/
60177, // affiliate-area/resources/
88825, // my-profile
142212, // affiliate-area/resources/smart-goals/
124419, // affiliate-area/products/
217193, // affiliate-area/resources/difference-makers/
217585, // partner-onboarding-2/
216459, //partner-onboarding/
)
)
|| ‘contributor’ === get_post_type()
) {
wp_nav_menu( array(
‘theme_location’ => ‘affiliate’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
elseif ( is_page(
/*
* If page slug is in array, use ‘sale’ navigation menu
* @since 1.0
*/
array(
52353, // iii
52533, // bb-i
52829, // bb-i-1
52910, // bb-i-2
52958, // bb-i-3
52981, // bb-i-4
53001, // bb-i-5
)
)
) {
wp_nav_menu( array(
‘theme_location’ => ‘sale’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
else {
wp_nav_menu( array(
/*
* If page slug is not above, use ‘non-sale’ menu
* @since 1.0
*/
‘theme_location’ => ‘non-sale’,
‘items_wrap’ => ‘<ul id=”%1$s” class=”nav navbar-nav ‘ .
( ‘right’ === $header_layout ? ‘navbar-right’ : ” ) . ‘ %2$s”>%3$s</ul>’,
‘container’ => false,
‘fallback_cb’ => ‘FLTheme::nav_menu_fallback’
) );
}
}
​
}`

[Ben Ritner]

Ben Ritner

#256455

1. Compress components with gzip. You should be doing this through an optimization (caching) plugin. I suggest you make sure to install this.

2. Lazy load background images, this will save a lot. (you can find this in your settings)

3. Use Kadence Blocks and our form block for your contact page. Our block is much more optimized then contact form 7 and it will keep you from having to use the contact form 7 Recaptcha which loads on every page of your site and you don’t need that. You can enable Recaptcha in Kadence blocks and it will only load on the page that needs it.

see: https://www.kadencewp.com/blog/need-for-speed/

Ben

[Janek]

Janek

#256297

This reply has been marked as private.

[Connie]

Connie

#254797

Can you show this to the developer? All of the virtue premium links in wp_options table are still stored in the website that is the sandbox. As soon as we delete the sandbox directory all those links break and the images are gone.

We need an SQL query that updates all the links in the wp_options table.

You can see the problem behavior if you look at the site on Firefox and look at the URL for the links. For example, the links in the image menu are still pointing back to the sandbox. See https://mathengineering.com/ (Right now the sandbox is still up, so you won’t see everything actually broken).

We can’t use the widget you mentioned because the site is already live.

Here is more information from my brother (it’s his site):

(17175, ‘widget_virtue_calltoaction_widget’, ‘a:3:{i:1;a:0:{}i:2;a:21:{s:5:\”align\”;s:6:\”center\”;s:10:\”btn_target\”;s:5:\”false\”;s:8:\”btn_link\”;s:42:\”http://sandbox.mathengineering.com/contact\”;s:8:\”btn_text\”;s:24:\”Schedule a Consultation \”;s:9:\”btn_color\”;s:7:\”#4f58f2\”;s:14:\”btn_background\”;s:7:\”#efc44f\”;s:16:\”btn_border_color\”;s:0:\”\”;s:10:\”btn_border\”;s:1:\”2\”;s:17:\”btn_border_radius\”;s:1:\”2\”;s:22:\”btn_hover_border_color\”;s:0:\”\”;s:15:\”btn_hover_color\”;s:7:\”#efc44f\”;s:20:\”btn_hover_background\”;s:7:\”#1e73be\”;s:6:\”tcolor\”;s:0:\”\”;s:6:\”scolor\”;s:0:\”\”;s:5:\”tsize\”;i:0;s:5:\”ssize\”;i:0;s:11:\”tlineheight\”;i:0;s:11:\”slineheight\”;i:0;s:5:\”title\”;s:26:\”Find out how we can help: \”;s:8:\”subtitle\”;s:0:\”\”;s:14:\”title_html_tag\”;s:2:\”h1\”;}s:12:\”_multiwidget\”;i:1;}’, ‘yes’),

The problematic part is “s:42:\”http://sandbox.mathengineering.com/contact&#8221;. It has both the string and the string length so that when I use MySQL replace function to change the URL to “https://mathengineering.com&#8221; everything breaks.

Thanks,
Connie

[augusto]

augusto

#253849

Aloha Team Kadence,
I am reporting this issue for both Ascend and Pinnacle themes.
I am not able to access the Menu settings (see attached screen shot)

Error Details
=============
An error of type E_ERROR was caused in line 59 of the file /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/plugins/ultimate-member/includes/admin/core/class-admin-navmenu.php.
Error message: Uncaught ArgumentCountError: Too few arguments to function um\admin\core\Admin_Navmenu::wp_nav_menu_item_custom_fields(), 4 passed in /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php on line 287 and exactly 5 expected in /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/plugins/ultimate-member/includes/admin/core/class-admin-navmenu.php:59
Stack trace:
#0 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php(287): um\admin\core\Admin_Navmenu->wp_nav_menu_item_custom_fields(‘1766’, Object(WP_Post), 0, Object(stdClass))
#1 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#2 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/themes/ascend_premium/lib/classes/class-ascend-custom-menu.php(322): do_action(‘wp_nav_menu_ite…’, ‘176
=============

I am using Ultimate Member (UM) plugin. I did disable UM and the issue goes away and I am able to access the Menu settings.
So I looked for support forum in UM and found this:
*Login to see link
=============
UM 2.1.6: Menu Issue – Too few arguments to function
A new changes made to the WP Core related to the Menu structure. We have made the same changes to make the UM Menu Visibility feature compatibility with these changes.

If you are encountering an issue with the Menu, here are the possible conflict issues:

1. If you have Mega Menu feature that’s enabled to your site, you must contact them to make the changes for the core Menu compatibility. They have incomplete parameters in wp_nav_menu_item_custom_fields hook.
2. Your Theme has Mega Menu feature but it doesn’t have the action hook ‘wp_nav_menu_item_custom_fields’ to support the standard Menu call so that other plugins can hook into it.
=============

Please let me know if you need more information from me to help fix this problem.

Thank you,
Augusto

[augusto]

augusto

#253849

Aloha Team Kadence,
I am reporting this issue for both Ascend and Pinnacle themes.
I am not able to access the Menu settings (see attached screen shot)

Error Details
=============
An error of type E_ERROR was caused in line 59 of the file /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/plugins/ultimate-member/includes/admin/core/class-admin-navmenu.php.
Error message: Uncaught ArgumentCountError: Too few arguments to function um\admin\core\Admin_Navmenu::wp_nav_menu_item_custom_fields(), 4 passed in /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php on line 287 and exactly 5 expected in /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/plugins/ultimate-member/includes/admin/core/class-admin-navmenu.php:59
Stack trace:
#0 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php(287): um\admin\core\Admin_Navmenu->wp_nav_menu_item_custom_fields(‘1766’, Object(WP_Post), 0, Object(stdClass))
#1 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#2 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /home1/zerowau6/public_html/domains/zerowasteschoolhui/wp-content/themes/ascend_premium/lib/classes/class-ascend-custom-menu.php(322): do_action(‘wp_nav_menu_ite…’, ‘176
=============

I am using Ultimate Member (UM) plugin. I did disable UM and the issue goes away and I am able to access the Menu settings.
So I looked for support forum in UM and found this:
*Login to see link
=============
UM 2.1.6: Menu Issue – Too few arguments to function
A new changes made to the WP Core related to the Menu structure. We have made the same changes to make the UM Menu Visibility feature compatibility with these changes.

If you are encountering an issue with the Menu, here are the possible conflict issues:

1. If you have Mega Menu feature that’s enabled to your site, you must contact them to make the changes for the core Menu compatibility. They have incomplete parameters in wp_nav_menu_item_custom_fields hook.
2. Your Theme has Mega Menu feature but it doesn’t have the action hook ‘wp_nav_menu_item_custom_fields’ to support the standard Menu call so that other plugins can hook into it.
=============

Please let me know if you need more information from me to help fix this problem.

Thank you,
Augusto

[marj.esch]

marj.esch

#253574

I’m using Foobox as my lightbox. I can code a hyperlink to have a form or table or other html elements load in a Foobox modal box. I’m wondering if there’s any way to do the necessary coding using the Kadence advanced button block. Currently I’m coding it manually in a custom html block, but would love to be able to use your advanced button block instead.

Here’s an example that’s on this page: *Login to see link The four button styled hyperlinks right below the breadcrumbs.

Below is my custom html code. In particular, the two hyperlinks styled as buttons that call Foobox are the Request Info and How to Contact Us buttons. For the link to open in the Foobox modal box, added to the href tag must be a call to a hidden div ID along with a target of “foobox” and data-width and data-height parameters. And for accessibility I add in an aria-label.

<div class=”cta-buttons”>
Request Info
989-275-5000
Apply Now
How to Contact Us
<div id=”contact-info” style=”display: none;”>[table id=92 column_widths=”25%|25%|25%|25%” /]</div>
<div id=”request-info” style=”display: none;”>[gravityform id=”9″ title=”true” description=”true”]</div>
</div>

Is there any way to do this using your advanced button block? Like maybe a field for additional href parameters?

[marj.esch]

marj.esch

#253574

I’m using Foobox as my lightbox. I can code a hyperlink to have a form or table or other html elements load in a Foobox modal box. I’m wondering if there’s any way to do the necessary coding using the Kadence advanced button block. Currently I’m coding it manually in a custom html block, but would love to be able to use your advanced button block instead.

Here’s an example that’s on this page: *Login to see link The four button styled hyperlinks right below the breadcrumbs.

Below is my custom html code. In particular, the two hyperlinks styled as buttons that call Foobox are the Request Info and How to Contact Us buttons. For the link to open in the Foobox modal box, added to the href tag must be a call to a hidden div ID along with a target of “foobox” and data-width and data-height parameters. And for accessibility I add in an aria-label.

<div class=”cta-buttons”>
Request Info
989-275-5000
Apply Now
How to Contact Us
<div id=”contact-info” style=”display: none;”>[table id=92 column_widths=”25%|25%|25%|25%” /]</div>
<div id=”request-info” style=”display: none;”>[gravityform id=”9″ title=”true” description=”true”]</div>
</div>

Is there any way to do this using your advanced button block? Like maybe a field for additional href parameters?

[Susan]

Susan

#252817

Hi,
A site I manage had a critical error this morning after updating the Kadence Blocks – Gutenberg Page Builder Toolkit plugin.
Only the home page was affected (page id noted in the details below). I could still access the Dashboard and other pages. I was able to revert to a backup of the site from a few hours previous, so for now the page is back and the site is ok, but I can’t update the plugin again until I know that crash won’t happen again – and won’t happen on other sites I manage as well.
WP Admin sent an email notification, with specific details of the error:
Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Gutenberg Blocks by Kadence Blocks – Page Builder Features.

First, visit your website (*Login to see link and check for any visible issues. Next, visit the page where the error was caught (*Login to see link and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

*Login to see link

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.4.2
Current theme: Ascend – Premium (version 1.9.12)
Current plugin: Gutenberg Blocks by Kadence Blocks – Page Builder Features (version 1.8.6)
PHP version 7.3.19

Error Details
=============
An error of type E_RECOVERABLE_ERROR was caused in line 4334 of the file /home/gritlabs/public_html/wp-content/plugins/kadence-blocks/dist/class-kadence-blocks-frontend.php. Error message: Object of class Kadence_Blocks_Frontend could not be converted to string

——————————————————————————————-

:)Susan D

[Susan]

Susan

#252817

Hi,
A site I manage had a critical error this morning after updating the Kadence Blocks – Gutenberg Page Builder Toolkit plugin.
Only the home page was affected (page id noted in the details below). I could still access the Dashboard and other pages. I was able to revert to a backup of the site from a few hours previous, so for now the page is back and the site is ok, but I can’t update the plugin again until I know that crash won’t happen again – and won’t happen on other sites I manage as well.
WP Admin sent an email notification, with specific details of the error:
Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Gutenberg Blocks by Kadence Blocks – Page Builder Features.

First, visit your website (*Login to see link and check for any visible issues. Next, visit the page where the error was caught (*Login to see link and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

*Login to see link

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.4.2
Current theme: Ascend – Premium (version 1.9.12)
Current plugin: Gutenberg Blocks by Kadence Blocks – Page Builder Features (version 1.8.6)
PHP version 7.3.19

Error Details
=============
An error of type E_RECOVERABLE_ERROR was caused in line 4334 of the file /home/gritlabs/public_html/wp-content/plugins/kadence-blocks/dist/class-kadence-blocks-frontend.php. Error message: Object of class Kadence_Blocks_Frontend could not be converted to string

——————————————————————————————-

:)Susan D

[Gabi]

Gabi

#252812

Hello, I have the following problem, after updating my sites with new WordPress version 5.4.2., and both Virtue Premium 4.9.24 and Ascend Premium 1.9.12. and Contact Form 7 5.2. I have the following problem.
On pages where I have displayed Contact Form 7 form, when I change and save content, I want to go to other pages or to Theme Editor I receive the following warning:
“This page is asking you to confirm that you want to leave – data you have entered may not be saved – Leave page / Stay on page”
Changes to the page are made, but I get this message always.

I tried to switch to default Twenty Twenty theme and the problem is gone.
Even tried to switch to the parent theme (I use child themes) but the problem is still there.
Can you please check what is going on. Will send you the login details to one page so you can test it by yourself, thanks Gabi

• This topic was modified 5 years, 10 months ago by Gabi.

[Gabi]

Gabi

#252812

Hello, I have the following problem, after updating my sites with new WordPress version 5.4.2., and both Virtue Premium 4.9.24 and Ascend Premium 1.9.12. and Contact Form 7 5.2. I have the following problem.
On pages where I have displayed Contact Form 7 form, when I change and save content, I want to go to other pages or to Theme Editor I receive the following warning:
“This page is asking you to confirm that you want to leave – data you have entered may not be saved – Leave page / Stay on page”
Changes to the page are made, but I get this message always.

I tried to switch to default Twenty Twenty theme and the problem is gone.
Even tried to switch to the parent theme (I use child themes) but the problem is still there.
Can you please check what is going on. Will send you the login details to one page so you can test it by yourself, thanks Gabi

• This topic was modified 5 years, 10 months ago by Gabi.

[Susie]

Susie

#252122

Hi I thought I had submitted this problem yesterday but I can’t find it so assume that I didn’t submit it properly or something. Anyway, as a result, I don’t have access to the exact error message but another user had a similar problem a while ago and will include what their message was – the log is *Login to see link

wiltonwindmill.co.uk is on PHP version 7.0 and for security and performance, it needs to be updated to 7.3 (according to WordPress). I updated the PHP version to 7.3 and got an error message regarding Slider Revolution. I found the same problem on the support forums here and the solution seemed to be to use 7.1. So I changed to 7.1 and that didn’t work either – I still got an error message but it was different and in fact couldn’t access the admin screens. I received this email from WordPress:
Hi!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Slider Revolution.

First, visit your website (*Login to see link and check for any visible issues. Next, visit the page where the error was caught (*Login to see link and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

*Login to see link

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.4.2
Current theme: Virtue – Premium (version 4.9.24)
Current plugin: Slider Revolution (version 5.1.6)
PHP version 7.3.3

Error Details
=============
An error of type E_ERROR was caused in line 71 of the file /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/includes/framework/base-admin.class.php. Error message: Uncaught Error: [] operator not supported for strings in /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/includes/framework/base-admin.class.php:71
Stack trace:
#0 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(465): RevSliderBaseAdmin::addMetaBox(‘Revolution Slid…’, ”, Array, NULL)
#1 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(72): RevSliderAdmin->addSliderMetaBox()
#2 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(44): RevSliderAdmin->init()
#3 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/revslider.php(165): RevSliderAdmin->__construct(‘/var/sites/w/wi…’)
#4 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-settings.php(371): include_once(‘/var/sites/w/wi…’)
#5 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-config.php(98): require_once(‘/var/sites/w/wi…’)
#6 /v

I have since changed PHP back to version 7.0 but obviously I need to find a resolution to the Revolution Slider problem in order to move forward.

Your help is most appreciated.

best wishes
Susie

[Susie]

Susie

#252122

Hi I thought I had submitted this problem yesterday but I can’t find it so assume that I didn’t submit it properly or something. Anyway, as a result, I don’t have access to the exact error message but another user had a similar problem a while ago and will include what their message was – the log is *Login to see link

wiltonwindmill.co.uk is on PHP version 7.0 and for security and performance, it needs to be updated to 7.3 (according to WordPress). I updated the PHP version to 7.3 and got an error message regarding Slider Revolution. I found the same problem on the support forums here and the solution seemed to be to use 7.1. So I changed to 7.1 and that didn’t work either – I still got an error message but it was different and in fact couldn’t access the admin screens. I received this email from WordPress:
Hi!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Slider Revolution.

First, visit your website (*Login to see link and check for any visible issues. Next, visit the page where the error was caught (*Login to see link and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

*Login to see link

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.4.2
Current theme: Virtue – Premium (version 4.9.24)
Current plugin: Slider Revolution (version 5.1.6)
PHP version 7.3.3

Error Details
=============
An error of type E_ERROR was caused in line 71 of the file /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/includes/framework/base-admin.class.php. Error message: Uncaught Error: [] operator not supported for strings in /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/includes/framework/base-admin.class.php:71
Stack trace:
#0 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(465): RevSliderBaseAdmin::addMetaBox(‘Revolution Slid…’, ”, Array, NULL)
#1 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(72): RevSliderAdmin->addSliderMetaBox()
#2 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/admin/revslider-admin.class.php(44): RevSliderAdmin->init()
#3 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-content/plugins/revslider/revslider.php(165): RevSliderAdmin->__construct(‘/var/sites/w/wi…’)
#4 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-settings.php(371): include_once(‘/var/sites/w/wi…’)
#5 /var/sites/w/wiltonwindmill.co.uk/public_html/wp-config.php(98): require_once(‘/var/sites/w/wi…’)
#6 /v

I have since changed PHP back to version 7.0 but obviously I need to find a resolution to the Revolution Slider problem in order to move forward.

Your help is most appreciated.

best wishes
Susie

[Bah Abdourahmane]

Bah Abdourahmane

#252111

Coucou comment allez-vous j’aimerais vous demander comment transformer ma boutique woocommerce en des annonces ?
Au lieu d’avoir un bouton ajouter au panier
On obtient un bouton contacter le propriétaire.
Exemple :

[Bah Abdourahmane]

Bah Abdourahmane

#252111

Coucou comment allez-vous j’aimerais vous demander comment transformer ma boutique woocommerce en des annonces ?
Au lieu d’avoir un bouton ajouter au panier
On obtient un bouton contacter le propriétaire.
Exemple :

[Linda]

Linda

#251982

This reply has been marked as private.

[Ryan Purves]

Ryan Purves

#251355

This reply has been marked as private.

[marc joseph]

marc joseph

#250464

Hi ben and Hanna
My home page *Login to see link take no more in count the ccs code in Option theme advanced css … :

/* FOR HOME PAGE 3 buttonslanguage choice No menu and no footer . The following code suppress the display of menu and footer only on mainhome landing template page */
home #kad-banner, .home #containerfooter {
display: none;
}

best Marc

/*STyle of the portfolios items … on a Portfolio page */
.portfolio_item .portfoliolink {
position: static;
border: 0px solid rgba(255,255,255,.5);
opacity: 1;
background: rgba(0,0,0,0);
border: 2px solid transparent;
}
.portfolio_item .piteminfo h5 {
margin: 0;
padding: 6px 0 6px 0;
color: #EEE;
}
.portfolio_item .piteminfo p {
color: #EEE;
}
.portfolio_item:hover .portfoliolink {
border: 2px solid rgba(255,255,255,1);
}

/* epaisseur police filter name du portfolio */
#filters li h5 {
color: #99a1a4;
font-weight:400;
}
/* color mouse over filter name on portfolio page */
#filters li h5:hover {
color: #fff;
}
/* pour mobile couleur du mot filter dans potolio page */
.filter-trigger {
color: #7593a0;
}
#filter-trigger:hover {
color: #fff;
}

/* rend transparent le backgrounddesarea de saisie de texte ds contact page */
#kad-feedback-new-post input.full, .contactform input.full, .wpcf7 input {
background-color: rgba(220,220,220, 0.7);
}
.wpcf7-form-control.wpcf7-textarea {
background-color: rgba(220,220,220, 0.7);
}

/* change la couleurdu texte du bouton submit dans contact */
.wpcf7 input.wpcf7-submit {
padding: 12px 18px;
font-size: 12px;
border: none;
display: inline-block;
color: #1b84e1;
background: #fff;
transition: background .6s ease-out;
-webkit-transition: background .6s ease-out;
-moz-transition: background .6s ease-out;
-o-transition: background .6s ease-out;
}

/* pour que la page 3 langues s’affiche sur Mobile */

@media (max-width: 780px) {
.so-widget-sow-hero-default-2da0f0801951 .sow-slider-base ul.sow-slider-images .sow-slider-image-wrapper {
height: auto !important;
}
}
/* to hide the right top bar widget on mobil only under a resolution */

@media (max-width: 768px) {
.topbar-widget {
display: none;
}
}
/* to suppress empty space before content of home page */

@media (max-width: 768px) {
.sow-slider-base ul.sow-slider-images li.sow-slider-image .sow-slider-image-container .sow-slider-image-wrapper {
padding: 0;
}
}

/* margin top et bas du H5 titre du portfolio sous le logo */
h5 {
margin-top: 0;
margin-bottom: 0;
}

/* supprimer espacement avant la top bar en haut
#topbar {
margin-top: -20px;
} */

/* Espacement vertical dans le texte paragraphe de PAGE BIO à 30px dans le css de la page */

/* CODE POUR MOBIL REDUIRE LE FILTER PROJECT SUR MOBILE */
#filters li {
float: left !important;
margin-left: 15px !important;
margin-bottom: 10px !important;
}
#filters {
height: auto !important;
}
.filter-trigger {
display: none;
}

[marc joseph]

marc joseph

#250464

Hi ben and Hanna
My home page *Login to see link take no more in count the ccs code in Option theme advanced css … :

/* FOR HOME PAGE 3 buttonslanguage choice No menu and no footer . The following code suppress the display of menu and footer only on mainhome landing template page */
home #kad-banner, .home #containerfooter {
display: none;
}

best Marc

/*STyle of the portfolios items … on a Portfolio page */
.portfolio_item .portfoliolink {
position: static;
border: 0px solid rgba(255,255,255,.5);
opacity: 1;
background: rgba(0,0,0,0);
border: 2px solid transparent;
}
.portfolio_item .piteminfo h5 {
margin: 0;
padding: 6px 0 6px 0;
color: #EEE;
}
.portfolio_item .piteminfo p {
color: #EEE;
}
.portfolio_item:hover .portfoliolink {
border: 2px solid rgba(255,255,255,1);
}

/* epaisseur police filter name du portfolio */
#filters li h5 {
color: #99a1a4;
font-weight:400;
}
/* color mouse over filter name on portfolio page */
#filters li h5:hover {
color: #fff;
}
/* pour mobile couleur du mot filter dans potolio page */
.filter-trigger {
color: #7593a0;
}
#filter-trigger:hover {
color: #fff;
}

/* rend transparent le backgrounddesarea de saisie de texte ds contact page */
#kad-feedback-new-post input.full, .contactform input.full, .wpcf7 input {
background-color: rgba(220,220,220, 0.7);
}
.wpcf7-form-control.wpcf7-textarea {
background-color: rgba(220,220,220, 0.7);
}

/* change la couleurdu texte du bouton submit dans contact */
.wpcf7 input.wpcf7-submit {
padding: 12px 18px;
font-size: 12px;
border: none;
display: inline-block;
color: #1b84e1;
background: #fff;
transition: background .6s ease-out;
-webkit-transition: background .6s ease-out;
-moz-transition: background .6s ease-out;
-o-transition: background .6s ease-out;
}

/* pour que la page 3 langues s’affiche sur Mobile */

@media (max-width: 780px) {
.so-widget-sow-hero-default-2da0f0801951 .sow-slider-base ul.sow-slider-images .sow-slider-image-wrapper {
height: auto !important;
}
}
/* to hide the right top bar widget on mobil only under a resolution */

@media (max-width: 768px) {
.topbar-widget {
display: none;
}
}
/* to suppress empty space before content of home page */

@media (max-width: 768px) {
.sow-slider-base ul.sow-slider-images li.sow-slider-image .sow-slider-image-container .sow-slider-image-wrapper {
padding: 0;
}
}

/* margin top et bas du H5 titre du portfolio sous le logo */
h5 {
margin-top: 0;
margin-bottom: 0;
}

/* supprimer espacement avant la top bar en haut
#topbar {
margin-top: -20px;
} */

/* Espacement vertical dans le texte paragraphe de PAGE BIO à 30px dans le css de la page */

/* CODE POUR MOBIL REDUIRE LE FILTER PROJECT SUR MOBILE */
#filters li {
float: left !important;
margin-left: 15px !important;
margin-bottom: 10px !important;
}
#filters {
height: auto !important;
}
.filter-trigger {
display: none;
}