[chsweb]

“text and background in white color and then put the paragraphs in black, since these are identified in the html”

For me, the paragraphs are not wrapped in <p> tags, so I cannot target them. When I edit to add <p>Text</p>, the <p> gets removed.

…I think the tag removal is a DIVI problem, as I see it happen from time to time when editing HTML in the DIVI content modules.

[chsweb]

I had a similar issue, and it took 24 hours for the content to appear. It appeared when logged in as an Admin first, then later, to the public.

I use WPRocket, and cleared all cache. I also deleted all data files from Safari for the website. I think that my issue was that CloudFlare is also used, and that may have been creating some additional delays, but I cannot confirm that.

@CW are you using CloudFlare or any kind of CDN service?

[chsweb]

Thank you @rafamoreno1960 – I am also using Divi. I tried something similar, but applied display:none; to everything, and then display:block to the headings and paragraph text, but that did not work because the paragraph tags are removed in the term box for some reason on save.

This is what I tried:
/* hide everything, then show just what is needed */
div#termsBox * { display: none;}
div#termsBox h2, div#termsBox p { display: block;}

My working solution was to revert the page back from Divi’s editor to the default WordPress editor and then edited the Terms content as follows:

I edited in HTML view and added some inline CSS to get the headings and body text to render better, since the WordPress editor was removing the paragraph tags on save:

<div style=”white-space:normal;”>
<h2 style=”margin-top:24px; font-size:24px;”>Section Title Here</h2>
<p>The quick brown fox jumps over the lazy dog. If the dog is lazy the fox is safe.</p>
<h4 style=”margin-top:24px; font-size:20px;”>Sub Title Here</h4>
<p>The quick brown fox jumps over the lazy dog. If the dog is lazy the fox is safe.</p>
</div>

[chsweb]

Having the same problem. I manually added affiliates and they do not receive the message with:

Your affiliate account for {blogname} has been approved!.
Username: {affusername}
Password: {affpassword}
Login URL: {affloginurl}

In another case, the received an email, but it send them to the WP Admin login, not the affiliate login.

[chsweb]

I have a similar question. It would be great if there were standard {mergFields} that could be used in any messaging.

For example, I created a new “Desired Affiliate Code” input field on the registration form, and in the email that gets sent on affiliate approval I’d like to give them their code along with their user name, pass and login URL, in the email using {affiliateCode}.

[chsweb]

How did you resolve this? I have the same issue.

[Author]

Posts