Hi Ismael,

Thanks for your patience with this.

I have disabled WPERP on both staging and production. The editor loads OK on staging but still still not on production.

I have raised this issue with them, but they take time to respond. With WPERP disabled the error no longer show, but the editor still doesn’t load.

I also see other errors on production:

Failed to load resource: the server responded with a status of 403 () admin-ajax.php:1
Failed to load resource: the server responded with a status of 404 () editor.css:1

Could that be contributing to the issue

Thanks

Phil

• This reply was modified 1 month, 3 weeks ago by philthebass.

Thanks Nikko,

That’s fixed it :-)

Regards

Phil

Hi Nikko,

Sure. Have posted privately as requested.

This has the hacky !important fix in the Quick CSS

/* Hack to fix field widths in GF and Enfold */
.gform_wrapper.gravity-theme .gfield input.small, .gform_wrapper.gravity-theme .gfield select.small {
width: calc(25% – 16px * 3 / 4)!important;
}

I can disable that if you need me to.

Thanks

Phil

Thanks Rikard. I’ll try that.

What’s odd is the theme wasn’t auto updated. My Envato key looks ok, so I’m not sure why I haven’t been prompted to update before.

Regards

Phil

Hi Rikard,

It seems to be intermittent and I get the same issue on Safari, Chrome and Firefox on both desktop and mobile.

The first time a product is added during a fresh session, it is not added to cart. Try a second or third time and then it’s added.

The moment I disable Enfold and use 2022 the issue goes away.

I’ve attached a video showing the fail the first time.

What’s worrying is that it’s intermittent and I don’t see ant console errors.

I’ve also updated to the latest version of Enfold. Still have the same issue.

Regards

Phil

Hi Rikard,
Thanks. Where do you see those overrides?
Regards
Phil

Thanks Ismael,

I copied it from the forum and that works nicely.

Thanks for your help.

Regards

Phil

Hi Rikard,

We managed to fix it like this

`@media only screen and (max-width: 1300px) {
.responsive #top .av-menu-mobile-active {
text-align:center
}
.responsive #top .av-menu-mobile-active .mobile_menu_toggle{
display:inline-block
}
.responsive #top .av-menu-mobile-active .av-subnav-menu{
display:none
}
.responsive #top .av-menu-mobile-active .av-subnav-menu.av-open-submenu{
display:block
}
.responsive #top .av-menu-mobile-active .av-subnav-menu > li {
display: block;
border-top-style: solid;
border-top-width: 1px;
padding: 0;
}
.responsive #top .av-menu-mobile-active .av-subnav-menu > li:first-child {
margin-top: -1px;
}
.responsive #top .av-menu-mobile-active .av-subnav-menu > li > a {
border-left: none;
padding: 15px 15%;
text-align: left;
}
.responsive #top .av-menu-mobile-active .av-subnav-menu > li a::before {
content: “\25BA”;
position: absolute;
top: 15px;
margin-left: -10px;
font-family: ‘entypo-fontello’;
font-size: 7px;
}
.responsive #top .av-open-submenu.av-subnav-menu > li > a:hover,
.responsive #top .av-subnav-menu .current-menu-item a:hover .avia-menu-text {
color: #53565a;
}
}
Regards

Hi

We have billing enabled. As i said in my note above, everything is set up as it should be with a valid API and a billing account set up.

It looks as though the wrong API is being used even though we’ve treble checked it and cleared caches several time.

Hi Victoria,

We’re using 4.7.6.1.

I can give you access to our staging site if that helps.

With thanks

Regards

Phil