zgomez

Okay it’s not wordpress at all. This seems to be Firefox doing this. I don’t know how or why! But I can’t replicate the issue in Safari or Chrome, and in Firefox the weird div is showing up on random pages that have nothing to do with Elementor. I’m closing this because now it looks like it was not the plugin at all.

You’re incorrect. This happens even with a fresh text block and no copying. I also already turned off every plugin and it was still happening with only Elementor enabled. The square in your example is also not the same as my issue; that’s a character, while mine is a div with a dotted border.

I will try changing the theme, but our theme has not been altered in any way, so I’m not sure how the theme could be involved.

• This reply was modified 1 year, 9 months ago by zgomez.

@israelaz It has not been resolved. Here’s a screen recording of the issue: https://www.ezfacility.com/wp-content/uploads/2023/02/Screen-Recording-2023-02-20-at-10.47.35-AM.mov

In it, I indicate the square I am talking about, and then highlight and remove the code from the text box. I leave the block and re-enter, and the extra code is back. It makes the four little dots that form a tiny square that shows up below and to the left of the text box.

@israelaz You can see it here, beneath the first two paragraphs. It looks like a tiny square of four dots: https://www.ezfacility.com/careers/

@fschall Yup, that tag has to remain disabled when I want to edit via Elementor. GTM is still enabled, just that one script is disabled.

It turned out the issue was with some custom-written javascript from a few years ago being inserted via GTM, rather than GTM itself.

I had to create a copy of our GTM, insert it into our dev site, and then turn off all tags until I found out which one was creating the interference with Elementor. Unfortunately, we had to keep that disabled if we want Elementor to work. Hope that helps.

@plantprogrammer Thank you, that was helpful! I did identify the plugin causing this, “Contact Form 7 to API” which looks like it may have been abandoned and removed from the plugin store. I will have to figure out if we can fix it or if we need to find a different solution.

Bumping this because I am still having this issue and need assistance.

Said, I already did that. I need help beyond those steps.