WarfarePlugins
Forum Replies Created
-
Thank you for bringing this to our attention. We will get his on the GIT board and looked at ASAP.
Hi Woorooo,
Terribly sorry for the frustration. You can always send an email directly to [email protected] and we have staff there to assist with 24 hr or less response time.
I am sorry that you were unable to use the website contact form. It was down for a few hours last week due to an update. But it has since been resolved. Please try again.
We value your support and business.Have you downloaded and reinstalled the most recent version of the plugin? Please do that. This has been fixed. You might need to manually do it depending on your version number.
Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] No longer on the WP repository?We are excited to announce that 4.4 has been updated for both core and pro.
When you update, it is best to update pro first, then update core.
Thank you for your patience and cooperation.Please update to 4.4
If you are using Pro, please update that first, then update core.
Thank you for your patience and understanding.The updates have been released.
It is best to update Pro first, then update core if you are using the paid version.
Hopefully Wordfence will fix their alert soon also.
Thanks for your patience.Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] No longer on the WP repository?We just got an email stating it will be updated here very shortly, within the hour.
We are also going to add a zip file to our website.Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] No longer on the WP repository?Yes, the issues reported in WP Scan and Wordfence are the same issue. In fact, I am not convinced that WP Scan does not just harvest info from Wordfence, but I am totally speculating.
Regarding the “issues” they have been fixed and we are still waiting for them to update in WP repo.
Yes, 4.3.1 is the “fix”Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] No longer on the WP repository?Hi everyone, thank you for your patience.
to be clear, everything has been al sorted out and this was really a matter of misunderstanding between WordPress and Wordfence.
The short answer is that we were removed from the WordPress repo due to a copyright infringement as we had both FB and Twitter logos on our banner. Once these were removed, we were reinstated into the WordPress repo as you can see. Unfortunately, we need to wait for the WordPress team (who you can imagine is extremally busy) to audit and approve our updates to the banner and confirm that we are in fact not in copywrite violation.
Regarding the security risk, WP Remote is echoing what Wordfence is reporting. The Wordfence issue was a separate matter and technically not a real threat which is why they list it as a 5.4 out of 10 on their website.
First they made a typo by listing it as 4.4 and they have fixed that typo.
Secondly there was an issue that allowed one logged in user to temporarily disconnect another users FB token. To which we asked Wordfence, “Who would go through all that hassle to trick someone into disconnecting Facebook.” and they agreed it is very minor but it is technically an “issue” they need to report.
We have fixed this with one line of code and version 4.3.1 is getting approved as we speak.
Thank you all for your patience.Hi Karen,
Yes, we are working closely with both the WordPress team and the Wordfence team to sort this confusion out.
The long answer is that WordPress removed us from the WordPress repository because we had FB and Twitter logos on our main banner and both FB and Twitter said this is a copywrite violation.
so we quickly changed the banners and submitted the changes to the WordPress team.
This revision to the change log triggered a version number increase that then trigger an automated alert to Wordfence.
There is also a ‘vulnerability’ issue that Wordfence reported that has also been fixed.
So the TL;DR to your question is that everything is fine, we are here and fully supporting the plugin and it is safe and secure.
Thank you for choosing Social WarfareHi We just received word back from Wordfence that they have updated their record.
They corrected their typo stating that we are up to 4.4.0 and corrected it to read 4.3.1 which the current version.
We now need to wait for WordPress Repo to update, and then Wordfence will update their vulnerability alert.
And for those who are interested, the vulnerability they are reporting is not even technically a vulnerability. Basic they see one instance where, if someone is logged in as ‘user’ (any level from admin to subscriber) then that person can cause another user to have their Facebook token temporarily disconnected. So basically they agree with our question, “Who would go through all that hassle to trick someone into disconnecting Facebook.”
Regardless of the severity of the “vulnerability” it has been fixed and we are now waiting for WordPress repo to update.
Thank you for your patienceForum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] No longer on the WP repository?We are working to resolve this issue with WordPress.
We are not going anywherePlease forward all support tickets to [email protected]
Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] Linkedin not retrieving informationWe don’t monitor this forum as much for support as we do on the support system on our website. Since you’re a pro user, send us a support ticket from the account page on our website and we’ll respond within 1 business day (at the most) and get this resolved for you as quickly as possible.
You were super close. It’s “no_pin”.
Forum: Plugins
In reply to: [Social Sharing Plugin - Social Warfare] swp_localization_init never firesThis is now fixed in version 2.2.10. Thank you for reporting it.