Dustin W. Stout

Looks like this is a WordPress core bug. I’m assuming it will be fixed soon.

@richtabor ah-ha! So there WAS a class that I wasn’t aware of that I could have targeted myself. I didn’t know the mt-0 and mb-0 were the classes associated with Remove Top/Bottom spacing, so I ended up creating my own class of no-margin.

@paranoia1906 those css rules have always been there.

CoBlocks had an update, and suddenly this is happening. The Remove Top Spacing and Remove Bottom Spacing options that CoBlocks provides on its block elements have always worked in overriding this css, and now it’s not. So I don’t see why changing my CSS (which is there because of other specific scenarios) is somehow the problem now.

Hi, Rich. Here you go: https://sovisual.co

I was just about to write some CSS to bypass whatever is happening, but my server seems to be having performance issues.

So here’s the ONLY way I’ve been able to avoid this… and it’s weird, but it works.

When typing a tag, type only the first letter and then wait for the cursor to blink 3 times, then type the second letter. The autosuggest should then populate and you can click on the pre-existing tag. I’ve noticed if I do it that way, selecting from the list, the tags don’t disappear.

It’s pretty agonizing to have to slow down at first, but then I realized I’m actually saving time by not having to retype the same tag 5 times.

Same issue with disappearing tags and CPU skyrocketing (as @plagiarismtoday noted). Has anyone found a solution or even gotten support on this issue?

Marking this as resolved since we’re 99.9999999999% sure it’s not coming from CPTUI.

You know what, I think you’re right @tw2113. I just watched the console as it happened and I’m seeing POST .../wp-json/wp/v2/tags?_locale=user 400 error. And then a whole list of things, most of which seem to have to do with api-fetch.min.js?ver=2.2.8:1 and a bunch of other files. All of them seem to be in WP core.

I didn’t think to check the console first. Thanks! Will see if I can get WP core support to look at this.

@specialk I read that you said that in another support thread, but I don’t see that to be true in my own WordPress installs. If you mean Advanced Custom Fields, then yes, I’ve never had a problem seeing those. It’s the “protected” and “hidden” custom fields that I need to view, and can’t be seen without this plugin (and in the classic editor, Phillip Newcomer’s _Show Hidden Post Meta_ plugin).

Awesome! Saw the update this morning and was going to try it out today.

I don’t know how much more clearly we can state this to everyone, but I will try to restate as best as I can:

Everything you’ve read about social share buttons and GDPR are things our team is aware of. And everything in these articles does not apply to the implementation by Social Warfare due to our methodology.

We’ve sought legal counsel. Consulted with professionals. We’ve read hours worth of GDPR documentation and guides.

Social Warfare is and always has been GDPR compliant.

All good questions, @lauratraveler. We do not load the Google Analytics Script. We add the necessary piece of code that will allow Google Analytics (when ALREADY LOADED) to track button clicks. All stats are stored in Google Analytics. So, again, Social Warfare is (and always has been) 100% GDPR compliant as we do not load any sort of tracking nor do we process or store any personal data with the plugin from your visitors.

We cannot speak to how social network APIs use (or don’t use) cookies. Since Social Warfare launches a new window which then allows the social network to activate its own sharing function, this then falls into their domain, not Social Warfare’s nor the website owner.

And no, we do not load any Google Ajax Search API either.

Hi, @sapphire! We’ve had this happen with a small percentage of users and it’s a PayPal issue. Open an official support ticket and our team knows exactly what to do.

Hi, @klausharms. As we’ve said, no action is taken, nor data transferred until a button is clicked.

So, again, Social Warfare is GDPR compliant, and always has been. The only scripts loaded to page by Social Warfare is the Social Warfare script. This is how we keep page load time at a minimum.

• This reply was modified 6 years, 6 months ago by Dustin W. Stout.

Hi, all! I wanted to jump in here and say that our entire team has been working very hard to address and squash bugs. Version 3.0.4, which is available for both Social Warfare and Social Warfare – Pro, is the most stable version.

We cannot recommend reverting back as it could potentially cause meta data conflicts, complicating issues that would have otherwise been solved with the next release (which will be 3.0.5). Our developer has told us he’s confident we will be back to normal by tomorrow.