Frequently Asked Questions

How can we help you?

How to Use

Configure your settings, simply download and it into your plugins folder.


Configure your settings in the WordPress dashboard then drop the short tag: [customkiwichat] into your page or post. Instantly your users will be able to stay connected via IRC.

Bug reports and pull requests are welcome on GitHub

Submitting code changes: open a Pull Request

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.


GitHub Documentation Issues y pull requests

Issues y pull requests

An Issue is a note in a repository that tries to draw attention to a problem. It can be an error to be corrected, a request to add a new option or feature, a question to clarify an issue that is not properly clarified or many other different things. On GitHub you can tag, search, or assign Issues, making managing an active project easier.

GitHub's Issues tracking system is special because it's focused on collaboration, cross-document referencing, and proper text formatting.

The Pull Request is the core of the GitHub collaborative system. When you make a pull request, you are actually proposing changes for someone to integrate into the project. GitHub allows you to compare the content of the two branches (one with your proposal and one without it) so that with a simple color code you can see what the differences are. Changes, additions and deletions, are shown in green or red and are called diffs (differences).

If you are not familiar with how to work with GitHub, we recommend that you follow this tutorial: Learn GitHub at your own pace

Brief guide to opening an Issue

Make sure your request has not already been made. Avoid duplicating requests. Learn how to search for issues

If no one has made an issue with your request. Click on the Issues tab in the sidebar.

Click the New Issue button

Give it a sufficiently descriptive title and clarifying text of your request. The clearer you are, the better.

Explain the problem, what is the expected result and what is actually obtained.

Detail one by one the steps to repeat the problem. It includes details such as the operating system, the browser used, the library, or the versions of the software involved in it.

Paste the error messages or the content of the logs in the same pull request or in a Gist. In case of pasting it in the text itself, it opens and closes with three French accents like this: `` '' that allow the code to be displayed correctly.

Click Submit New Issue when you are done. Now this Issue has a permanent URL that you can reference to share.

If you want to go deeper into the subject, follow the following link of the official GitHub documentation: Mastering Issues

Brief guide to making Pull Request

Make a fork of the repository you wish to contribute by clicking on the button in the repository header. You must have logged into your GitHub account.

When complete, the page will open with your copy of the forked repository, but it only exists on GitHub for now. You will need to clone it on your local computer.

Now you can make the changes by editing the code or documentation in the repository cloned from the fork

When you are satisfied with the changes, follow the normal working procedure with commit and stage.

As soon as your changes are complete, and correct or improve the feature you had planned to contribute, be it code or documentation, you can push the repository.

At this time your changes are in the forked repository, not in the original, so we must proceed to communicate the changes. If you enter the repository, you will see a new flag indicating that a new branch has been pushed and that this branch can be added to the original repository.

Click Compare and Pull Request, a discussion page will open. In it you can include a title and an optional description. It is important that you provide all the necessary information to understand why you made the changes and what your improvement is based on. The project maintainer needs to be able to determine if the change is useful and / or necessary (remember that the project maintainer may have other improvements or changes in mind that may conflict with your contributions).

Send the pull request

Pull requests, apart from improving the code and existing documentation by the community, are very active discussion areas, so your changes may not be accepted at the same time. Do not be offended if the author does not accept your corrections or asks for further clarification before accepting them. In any case, your changes will be available to everyone thanks to your fork from the original project. Many original projects have been improved in this way, even being surpassed by those that started as a fork. Perhaps in the future someone will find that your contributions are extraordinary and greatly improve the original project.

If you want to delve into the subject, follow the following link from the official Github documentation: Forking Projects

Didn't you find anything here? contact me directly from the contact page