Support Terms of Service

  1. Home
  2. Knowledge Base
  3. FAQ
  4. Support Terms of Service

Not the solution you were looking for?

Click the link below to submit a support ticket. If you are a Social Warfare - Pro license holder, you can log into your Account page to submit a ticket.
Submit Ticket

Here at Warfare Plugins, we’ll do the absolute best we possibly can to help you solve any issues and answer any questions you might have while using our plugins. However, as you might imagine, we do periodically encounter requests for support in situations that are simply beyond what we are able or willing to help with.

A. Protecting Ourselves & Our Staff

This first section contains some issues that are rather boilerplate for most support teams. Simply put, we can not and will not ask our support teams to view any site containing the following things, and as such, we will not provide support for them either. This includes providing support for websites that contain any of the following features:

  1. Is sexually explicit or pornographic, exploits or presents minors in a sexual way, or promotes adult sexual services
  2. Creates a genuine risk of physical injury or property damage, credibly threatens people or public safety, or organizes or encourages harm
  3. Promotes self-harm, eating disorders or hard drug abuse
  4. Attacks, bullies or harasses nonpublic people
  5. Includes hate speech
  6. Is gratuitously violent or gory
  7. Infringes anyone’s intellectual property, privacy or other rights
  8. Is fraudulent or deceptive
  9. Is someone else’s personal information or requests a minor’s personal information
  10. Contains any information or content that’s illegal
  11. Represents a private person offering to trade or sell drugs, alcohol, tobacco, firearms or other hazardous materials

B. Excessively Abnormal Situations

Additionally, there are some situations that we find where websites don’t follow standard WordPress best-practices regarding the nature of the way that they are coded. These situations make it nearly impossible to feasibly provide support without spending incredibly excessive amounts of time to provide. A few examples include:

  1. Themes that Use Ajax Page Loads: Our plugin relies on the “Dom Loaded” event to fire off in the javascript. Ajax page loads prevent this event from firing off. If you are familiar with javascript, you can add our swSetWidths(true); and activateHoverStates(); functions to run after the page is fully revealed, but beyond that advice, we will be unable to provide support. There are simply too many different implementations of Ajax page loads that there is not way to be able to code our plugin in a way that properly detects them and fires the necessary events off properly.
  2. Custom Designed Themes: We work incredibly hard to ensure that our plugin does not conflict with other plugins or themes. When we learn of a conflict, we do whatever it takes to eliminate that conflict immediately. However, we have no control over the literally limitless configurations that individuals may implement into custom themes. This becomes especially difficult when we often find that the user failed to follow guidelines as put forth by the WordPress codex. When these guidelines are followed, our plugin almost always works as it should. When they are not followed, it simply isn’t our responsibility to troubleshoot your theme and provide you with development education.
  3. Plugin/Theme Conflicts resulting from Outdated plugins or Violations of WordPress Coding Standards: In most cases, when we encounter a conflict with another plugin, we are more than happy to create a solution to ensure that the conflict is eliminated. However, this is simply not possible for plugins that have not been updated in a very long time and are using outdated code. Additionally, while we do our absolute best to ensure compatibility with as many other plugins as possible (we usually even contact the creators of other plugins to collaborate on these types of issues), ultimately we cannot guarantee that a compatibility fix will be able to be found.
  4. Locally Hosted Development Sites: Due to the fact that we will literally have no way of viewing either the frontend or the backend of a locally hosted site, there is often very little that can be done to troubleshoot issues. If it is a known issue, we can offer advice towards a solution, but if it is anything beyond that, our hands are pretty much tied since we have no way of looking into it.

Was this article helpful?

Related Articles