Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing in a Clean WordPress Installation #81

Closed
jaswrks opened this issue Feb 3, 2015 · 4 comments
Closed

Testing in a Clean WordPress Installation #81

jaswrks opened this issue Feb 3, 2015 · 4 comments
Assignees

Comments

@jaswrks
Copy link
Contributor

@jaswrks jaswrks commented Feb 3, 2015


KB Article Creation Checklist
  • Write initial draft for this KB Article; label this issue draft and either questions or tutorials
  • Add required YAML configuration
  • Add Tags for this KB Article to the YAML config (see YAML Keys (Explained))
  • Edit and finalize draft for publishing (remove draft label, add draft-finalized label)
  • Assign Issue to yourself and create Markdown file (remove draft-finalized label, add pending)
  • Project Lead: Review and Publish KB Article (remove pending label, add published label)
Additional TODOs

Additional TODO list items go here.


Markdown File: http://wsharks.com/1GIsuFh
Published KB Article: http://s2member.com/kb-article/testing-in-a-clean-wordpress-installation/


@raamdev
Copy link
Contributor

@raamdev raamdev commented Feb 4, 2015

I was just reviewing this draft (nice!) and thought I'd suggest a few header changes to make the whole thing more attractive:

Unexplained BugsIs it really a bug?
A Clean WordPress TestReproduce the problem in a clean WordPress environment
Getting Help with Conflicts?How do I get help with plugin/theme conflicts?
Support Policy Excerpt...Our Support Policy
Reporting Plugin ConflictsHow to report plugin/theme conflicts

@jaswrks
Copy link
Contributor Author

@jaswrks jaswrks commented Feb 4, 2015

Updated. Thanks!

@RealDavidoff
Copy link

@RealDavidoff RealDavidoff commented Mar 12, 2016

How to Report Plugin/Theme Conflicts
If you identify a conflict between s2Member and another plugin, we would love to hear about this! While we cannot offer support for other 3rd-party themes/plugins, we do accept feedback. Theme/plugin conflicts are reviewed by our developers on a regular basis, and efforts to enhance compatibility are always underway. Thanks in advance for your patience!

How can we improve this article?

How to Report Plugin/Theme Conflicts
we would love to hear about this!
Nothing above says "HOW"??

So I can only go back to the "ticket" that linked to that page, and reply inside that "ticket".

@raamdev
Copy link
Contributor

@raamdev raamdev commented Mar 14, 2016

@RealDavidoff Thank you. I've added a link to the relevant area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants