Here at Warfare Plugins, we’ll do our best to help you solve any issues and answer any questions you might have while using our plugins. However, we periodically encounter requests for support in situations that are beyond what we can or are willing to help with.
A. Protecting Ourselves & Our Staff
Warfare Plugins can not and will not ask our support teams to view any site containing the below-listed content, and as such, we will not provide support for those sites. This includes providing support for websites that contain any of the following features:
- Is sexually explicit or pornographic, exploits or presents minors in a sexual way, or promotes adult sexual services
- Creates a genuine risk of physical injury or property damage, credibly threatens people or public safety, or organizes or encourages harm
- Promotes self-harm, eating disorders, or hard drug abuse
- Attacks, bullies, or harasses nonpublic people
- Includes hate speech
- Is gratuitously violent or gory
- Infringes anyone’s intellectual property, privacy, or other rights
- Is fraudulent or deceptive
- Is someone else’s personal information or requests a minor’s personal information
- Contains any information or content that’s illegal
- Represents a private person offering to trade or sell drugs, alcohol, tobacco, firearms, or other hazardous materials
Additionally, we reserve the right to refuse support to people that become hostile or verbally abusive during their encounters with our support staff. We offer our full support, kindness, and respect to those who offer their patience and understanding in return.
B. Excessively Abnormal Situations
There are some situations where websites don’t follow standard WordPress best practices due to the nature of the way they are coded. These situations make it nearly impossible to provide accurate support within a reasonable timeframe. A few examples include:
- 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. Beyond this advice, we are unable to provide support for this scenario. There are too many different implementations of Ajax page loads to be able to code our plugin in a way that works in conjunction with all of them.
- Custom-Designed Themes: We work incredibly hard to ensure 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 cannot control the limitless configurations that individuals may implement into custom themes. This becomes more difficult when we find that users have failed to follow WordPress codex guidelines. Our plugin almost always works as it should when these guidelines are followed. When they are not followed, we simply cannot troubleshoot your theme and provide development education.
- 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 usually not possible for plugins that have not been updated in a very long time or ones that 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 found.
- Locally Hosted Development Sites: Because we have no way to view the frontend or backend of a locally hosted site, there is usually little that can be done to troubleshoot issues. If there is a known issue, we will offer what advice we can, but we can’t guarantee a fix for websites when we lack the visibility to see into them.
