rafael777

The problem isn’t canceling backups in progress. The problem is that there are still backup processes running in the background, consuming resources, days after the backup has already been completed. These backups don’t appear in the UI, the only way to cancel them is to kill the server processes (which I can’t do myself, only my hosting provider can)

OK the manual backup I ran just completed… but once again, the hosting provider said that lots of processes continue to be initiated, and continue to run even after the backup is completed… These processes end up hogging all of the server resources and the hosting provider has to kill the processes manually.

My hosting provider told me to deactivate the plugin immediately.

Please advise.

Update: I just removed the “plugins” (and “themes”) folder from the backup as it seemed from their logs that the culprit might be related to the backup of the plugins folder. I then ran a manual backup to see what happens. Turns out the backups don’t even work anymore. It just hangs on “Creating file backup zips (Uploads)”.

Here’s the log from the backup I just ran: https://drive.google.com/file/d/13C5Ic5WqZLt3QoKctwfK325lt1tgH5sP/view?usp=sharing

And here’s the log from the last successful backup from last week (the one where my hosting provider complained about): https://drive.google.com/file/d/1xhr8lWv5wrA5J1exF5Y8JRIUR6sp3q1F/view?usp=sharing

• This reply was modified 4 years, 3 months ago by rafael777.

But that’s the point, the text element is not contained within any class… So now I have no way to target the headers in pages that have Easy Table of Contents enabled. I have separate CSS for blank h2’s where there’s no TOC, and h2’s where there is a TOC.

How can I accomplish this in 2.x?

OK I figured out the problem. The problem was that gzip compression was enabled in W3, while Brotli compression was enabled in Cloudflare (it’s enabled by default). As a result, the server responded with “Content-Encoding: br” (Brotli), even though W3 compressed it with gzip the first time, when Cloudflare wasn’t primed for that page yet. That’s why it worked fine the second time you loaded the page, because by that point it bypassed W3 and loaded the cached version from Cloudflare.

I disabled the gzip compression in W3, and everything is working fine now.

You might want to add a notification somewhere that warns users when GZIP compression is enabled to make sure there’s no compression conflict. I suspect I won’t be the only one who stumbles into this…

Hi,

Sorry for the delayed response. I enabled the feed cache again… you can check out the broken feed here: https://amenvamen.com/channel/social/feed

Here you go: https://amenvamen.com/channel/social/feed

Keep in mind that I disabled the feed caching option on W3 for now, so the feed is currently working.

Let me know if you want me to enable it again so you can see the broken cached version.

Of course it’s not there at the demo page – because you’re not trying to hide the WhatsApp button.

Just follow your own instructions from here to hide the Whatsapp icon: https://support.heateor.com/tag/hide-whatsapp-icon/

And when the icon disappears, it will leave a white space behind on the horizontal floating bar.

I can’t show you a live example, because I didn’t hide the icon due to this bug.

Are you joking?

Of course they belong to you…

I changed the colors of the mail icon via CSS, that’s probably why thought its a different plugin.

You really think I’m that stupid? I uploaded screenshots, showed you your plugin’s CSS, and you really think I mistook your plugin with someone else’s?

C’mon…

I assume you haven’t looked into the issue then?

Right now my website is live with the Whatsapp Icon showing on the horizontal bar on tablets (which clearly it doesn’t belong there), because when you hide it – it leaves a blank space like I showed in the 2nd screenshot.

• This reply was modified 6 years, 7 months ago by rafael777.

OK, thanks.

Another thing I just noticed: it seems that the text included in the “Text that appears wrong” is marked display:none by default via CSS.

This is a problem for search engines because they ignore content inside hidden elements…

Can you please add an option that doesn’t use display:none via CSS, and instead uses JS to change to display:none after page load so that search engines take that content into consideration?

All of these things are possible with our plugin as it provides a checkbox and a text field where you can include this language. I don’t understand why you would need multiple text fields – you can use as many paragraphs as you want

The checkbox alone is where the marketer references the (unbundled) channels they’ll contact the user with (in this case – email). But then there’s also a GDPR requirement to mention that they can unsubscribe at any time (i.e the right to be forgotten) and clearly specify what we’re planning to do with their information (send them weekly offers, marketing material etc’).

Naturally, it’s a little hard to fit all of that in one tiny checkbox field.

You can take a look at what Mailchimp did to get a better idea of what I mean. They added several key elements for GDPR:

1. The checkbox field
2. A description field (above the checkbox) where you clarify what you’ll use their information for
3. A Legal text field (below the checkbox) to clarify the terms of service (and link to it as needed)

The checkbox field alone looks like a partial solution and doesn’t seem to comply with GDPR fully.

Did you enter a value for the Merge Field Opt-in Value? (The second input field shown on this screenshot: https://ps.w.org/eu-opt-in-compliance-for-mailchimp/assets/screenshot-1.png?rev=1872070).

I haven’t. That’s probably why it didn’t work. The placeholder (that says “Opted in”) made me think that it has that as a default value…

I just updated the plugin, and having the same problem. All of a sudden, the Social Warfare icons are showing up after the checkbox and messing up the entire opt-in box.

I think using the_content will have all sorts of similar problems when other plugins also hook into it. Probably a good idea to turn it off by default.

Also, the checkbox alone doesn’t make it compliant for GDPR.

From my understanding, you also need the following (in addition to the consent) to be compliant:
* Add a statement that recipients can unsubscribe or update their data/consent at any time
* Clearly specify why we want the data and what we will do with it.

In other words, it seems that another text/description field (or even two, if you want to mirror what Mailchimp did) for complementary legal text would be required (just like Mailchimp added a textbox for “Legal text”.

Can you add that please?

UPDATE: I just tested the “Save Checkbox Opt-In as a Merge Field”, and it doesn’t seem to work (unless I haven’t understood the feature properly).

I tried creating a hidden merge field on Mailchimp, and then selecting that field to store the opt-in compliance. After subscribing, that field still has an empty value.

• This reply was modified 6 years, 10 months ago by rafael777. Reason: Save checkbox opt-in as a merge field feature not working
• This reply was modified 6 years, 10 months ago by rafael777.

And now it started working… straaaange

Ok quick update. Apparently the old analytics code originated from cloudflare. So i disabled it thinking maybe the plugin recognizes a GA code so doesn’t add another one.

But apparently the plugin simply doesn’t work… no analytics code is added whatsoever, and apparently it was cloudflare saving my ass all this time making me think it was the plugin sending data to GA…

Bottom line – plugin doesn’t work

Thought so ??

Thanks for your help