gab81

hi @miloss84

Today Danilo from Qode support did custom testing for me on my Bridge theme and I think you guys need to be open that this is entirely on Elementor.

We’ve gone ahead and provided feedback 2x and now custom feedback.

From Bridge support

“No matter what people from Elementor said, the issue is not theme-related. I enabled the Twenty-four theme and disabled our theme and our plugins, but it persisted after activating another theme.

Please note that this is not something that we can solve as the problem is not within our theme.

You should contact Elementor regarding this and tell them that you have reproduced the issue with the Twenty Twenty-Four and that is not related to the Bridge theme you are using.

Danilo moved the styles for me into Qode Options>General>Custom CSS and then i removed that custom code from each page (took me 1 hour of work) and the workaround worked so now the custom code is there and not on each page. My site is now running the latest Elementor and runs perfect, but we’ve had to correct it this way.

While i do understand you have thousands of customers, the code i had in the header of each page (whether that was best practise or not), was very basic.

Anyhow, probably there are other customers with these issues with the same implementation as mine and they won’t go to that effort i went for correcting it and they will just end with a broken site.

hope it helps. ciao.

• This reply was modified 4 months, 3 weeks ago by gab81.

I just reported what you said once again to Bridge support, though i highly doubt it’s Bridge.

@miloss84

This is going in circles man. I have tested it with the 2024 twenty-twentyfour Standard wordpress theme and 100% was the same in front end, did you see that in my previous message here?

I’ve already talked with Bridge support who told me since there’s the error with the standard theme, this is within Elementor to fix.

You say it’s them. They say it’s you. I am in the middle.

@miloss84

Ok, new update from me:

I updated Bridge to latest release 30.8.1 – after that site was still great

Then i checked, cleaned cloudflare, all good.

Then tried to update elementor to 3.24.6 again – site broken as per before, same identical.

Then rolled back to 3.24.3 and site’s fine again. So nothing changed even with Bridge’s latest update as well.

Pages are quite basic.

It’s literally showing on front end some small code customizations i have on “Heading Sections”, for headers with one underline, a small custom css. not even super advanced stuff!

Let’s see if this helps figuring out what’s wrong. Check one page from my site https://www.gabriolinari.com/about-gabrio-linari/

We have this in the Heading Section

<span class="custom-underline">Biography</span>

 <style>
        .custom-underline {
            display: inline-block;
            line-height: 1.2; /* Adjust this to control the space between text and underline */
 border-bottom: 4px solid #1AA9C7; /* Customize the color and thickness */
            padding-bottom: 0px; /* Adjust this to control the space between text and underline */
        }
    </style>

The homepage has a bit more heavy things, i suppose. That bit screws up the whole page, as shown in here:

https://drive.google.com/file/d/1PHbYlGSev9rFVu4YjOek7xwtc0Jowfkb/view – About Me Page, same as above

https://drive.google.com/file/d/1bb0B4rfmUheVKJXuVOWPi3OgHZh1UCOI/view – This is the homepage.

If you can drop me an email we can take this privately, perhaps that’ll help others.

Thank you ??

@miloss84

Here’s what i just tried today:

Upgraded Elementor to latest 3.24.6 on Bridge and no change – theme is still screwed up with the weird CSS text on front end

Switch another theme – 2024 with 3.24.6 – theme is still screwed up with the weird CSS text on front end

Tried to clear CSS files, etc – no change

Screenshots

https://drive.google.com/file/d/1PHbYlGSev9rFVu4YjOek7xwtc0Jowfkb/view?usp=drive_link

https://drive.google.com/file/d/1bb0B4rfmUheVKJXuVOWPi3OgHZh1UCOI/view?usp=drive_link

Disabled elementor for another test – no weird CSS text displayed on front end

Re-enabled elementor – weird CSS on front end again

Rolled back to 3.24.3 – all back to normal

There’s also a Bridge Core update available which i haven’t done just yet, at this point i am still clueless.

With the other theme it’s also showing the weird CSS so doesn’t seem Bridge related?

thanks,
Gabrio

• This reply was modified 4 months, 4 weeks ago by gab81.

hi @nemanjat thanks for the drop in and appreciate that you guys are dealing with a lot. Here’s some new feedback:

i’ve just tested;

3.24.5 with the Elementor > Tools > Regenerate CSS & Data – no change.

My site still looks broken with things like this showing on the main page, like code showing on front end (they should not show):

.responsive-h1 { font-size: 60px; /* Default for desktop / color: white; } / Small devices (phones, 600px and down) / @media (max-width: 600px) { .responsive-h1 { font-size: 30px; / Adjust font size for phones *

here’s some screencaps to show you

https://drive.google.com/file/d/1RoURcOWoykSteSn8EWc3zTIQwyZzafma/view?usp=drive_link, https://drive.google.com/file/d/1lg__5Uq5gBm3d_mJCbfRwyOi-x38ubDz/view?usp=drive_link, https://drive.google.com/file/d/17jpbYNwKfXMQyiL-01Uz8LWgYxy59FZS/view?usp=drive_link

I recorded a loom but won’t share it here for privacy – can i send it to you in DM somehow? I am a Bridge User which then leverages Elementor.

i’ve reverted back to 3.24.3 and site is fine again ??

Thank you!

• This reply was modified 5 months, 1 week ago by gab81.

Actually, 3.23.3 was also not working properly, i’ve put it back to 3.24.3 and my site now renders as before in all areas and will stick to that. Hopefully they release a new version which takes into account everything not working, etc.

I suggest disabling automatic Elementor updates in the meantime, i have done that.

Cheers!

• This reply was modified 5 months, 2 weeks ago by gab81.
• This reply was modified 5 months, 2 weeks ago by gab81.

Ah phew, there’s an easy rollback feature. just rolled back to 3.23.3 as someone suggested and site is back to normal.

Same here guys, it just ruined all my work website, i just saw the “click here to finish update” in backend, and then BOOM that happened, it exposes the CSS code on my site.

simple CSS is not rendered anymore. On Version 3.24.4

• This reply was modified 5 months, 2 weeks ago by gab81.

Indeed cheers. One last thing: i’ve noticed that there’s a time, maybe once in a day only, when the form submits and it doesn’t give you the green “Message sent” – in that case there’s no email received, cache or not cache. Please let the dev know. Server is fine and load is low. cheers

Haven’t heard back from you anymore, wanted to let you know that with CF setting to 8 hours for the contact page it works, problem seems solved.

hello, me again, I went to the bottom of this and analysed the code entirely, please share this with your developers:

Just after exactly 24 passed, the form started not working again, hence it’s not the captcha – i thought there must be something that changes after 24 hours but gets blocked because CF doesn’t serve it due to cache.

I dug deeper and,

With a bit of help of ChatGPT, I discovered that the issue is with the “nonce”, which is issued by WordPress and expires after 24 hours. Since i have a cache rule “cache everything for 1 month”, WordPress issues a new nonce after 24 hours, Cloudflare still serves the “expired” one, WordPress isn’t happy and voilà form is stuck and no email.

“nonce”:”e944626262″ this is unique and refreshed every 24 hours.

A simpler approach might be to dynamically load the nonce on the client side via AJAX. This would keep pages cacheable while ensuring that a valid nonce is always used for form submissions. This might involve some changes on the plugin side by your developer.

Workarounds possible are:

• Entirely disable CF cache for the contact page (not great for international traffic)
• Change global caching policy to 20 hours (not great also)
• Change caching policy only on the contact page to 20 hours (this way contact page is still fast and nonce should work)

I just went with option 3, which i think is the best one, everything can remain cached up to 1 month, whereas the contact page will refresh every 20 hours, allowing the new nonce to work.

Back in 24 hours again.

Best Regards,
Gabrio

• This reply was modified 1 year ago by gab81.
• This reply was modified 1 year ago by gab81.

hello,

Update:

It’s been 21 hours since clearing cache on CF yesterday. Form perfectly works. So, looks like the REcapctha is the issue here. Good i don’t get much spam (for now) so could stay off.

I was using captcha v2 on Gutena’s settings, i could test v3 as well.

Considering CF Cache bypass for /admin-ajax.php does its job, is there a similar .php or .js file used when REcapctha is on that i could bypass so it does not interfere with the form?

thank you,
Gabrio

i’ve removed the recapctha – testing a further 10-12 hours from now. after removal and checking the contact page, it works (with full cache switched on).

No problem, thank you! ??