klynam

Divi support points fingers at Popup Maker. So here I am again…

For some reason, when Popup Maker is enabled, a line of CSS “reset” code gets injected into ALL of my Divi page layouts, which forces all of the “paragraph” line-spacing throughout my site to “1em !important;”

Disabling PUM instantly fixes the problem. Disabling all other plug-ins or any combination of plug-ins shows no effect whatsoever. The problem only happens when PUM is activated. Clearing browser or Divi cache does nothing to fix the issue. It’s there with PUM on, and gone with PUM off.

I contacted Divi first and (naturally) they said, “it’s not their problem – its a conflict with the plug-in so go to the plug-in dev.” Which I’m doing now.

I have PUM running on multiple client sites, and they’re all affected. PLEASE help!!!

Yes, the dev was VERY responsive and accommodating to this request. Technically, being able to affect the position of the simple banner within the header is a PRO (paid) feature, but it DOES now work within the Divi header, even when “show header after scroll” is enabled, which is where most all of these banner plug-ins fail on the Divi theme. With appreciation and now a modified rating !!!

Based on the authors enthusiasm and determination to support his product and users, I’m optimistic that the core (free) version of Simple Banner will soon be compatible with Divi.

The plug-in author has been very communicative about this issue, and says the PRO version has a function to fix it. Unfortunately, I don’t like the idea of having to pay for compatibility with one of the leading theme frameworks in the world. So for now, it seems fair and accurate to say the core (free) version of the Simple Banner plug-in simply doesn’t work well with Divi.

alright, that is enabled, but i’d prefer not to expose the site address here on public support so I’ll ping you on slack

For anyone else running DIVI… So far, latest release of PUM is returning the same “Popup Maker detected an issue with your file system’s ability…” error message on EVERY Divi site I have it installed on (and updated) regardless of host – looking forward to a resolution

Why not callout each specific attribute like this…

.attribute-1, attribute-2, attribute-3 {visibility: hidden !important;}

In my experience, using visibility:hidden seems to preserve layouts better than display:none
???

• This reply was modified 3 years, 1 month ago by klynam.

Yep – reviewed the troubleshooting docs but thank you.

Just updated another site from within the WP dashboard, seems to have worked perfectly w/ no issues.

(^^^ why I asked instead of complaining – LOL ??

Failed after repeated attempts on Inmotion Hosting using a very basic and fresh (today) WP installation. Same error as above. Tried deactivating WordFence and adding the wp-config mod suggested above. Neither worked, same error kept happening. Switched to another user importer and it worked on the first attempt even using the original CSV user export generated by this tool. Not complaining, just letting you know. Looks like a great tool, just didn’t work for me in this particular case.

@bobsled… my understanding was that “repair” basically restores a target file to current specs per the plug-in’s official WP repository. (In which case, it would seem that TMCE needs to address the issue, not WF.) Please let me know if that’s NOT correct, as it would definitely change my approach to some things – lol.

In general, I’m uncomfortable “ignoring” anything flagged by WF – and there’s been no OFFICIAL announcement by either plug-in author about these being false positives. The only info I’ve personally found is the post above from @azaozz (which really doesn’t provide much insight into the issue, or inspire much confidence in the recommendation.)

For the record, I’m now getting RE-alerts from WF on sites w/ TMCE where I DID run the repair option. So whether it’s good or bad to do so, it apparently doesn’t HELP to do so.

JM2C – and I appreciate the convo…

Yep, I’m receiving the same Wordfence notifications from several of my sites.

Rather than just dismissing or ignoring, I’ve been running the “REPAIR ALL repairable files” option which seems to be working fine to remove the warnings.

(Whether or not that actually updates the files and/or corrects whatever is triggering WF is still tbd I suppose…)

You need some CSS specific to the Divi theme.

Here’s the base CSS solution: #main-header {display: none;}

Google = https://www.markhendriksen.com/how-to-hide-the-header-and-footer-in-divi/

Get rid of all the other stuff you did EXCEPT the child theme for Divi.

Add the CSS above to your child theme.

PS. If it does NOT work when added to the child theme CSS file, you will need to add it to the Divi settings > Custom CSS (you can also add it directly to your landing page instead of the theme CSS, and only disable the menu on the landing page – which can be very handy)

OMG… you’re brilliant – LOL

Of course the site settings were CLONED from the old site. One text change to include the correct sub-directory and I’m off to the races.

Thank you so much @jnashhawkins !!!

• This reply was modified 6 years, 5 months ago by klynam.

For instance, is there a way to create a NO-REWRITE sort of rule, so that a specified URL construct is always honored and not rewritten to the default sub-directory?

That appears to have worked splendidly, and SO much easier than all the other procedures I had found online !!!

Thanks again Steve ??