Tabulator has a great community of coders helping eachother get the most out of their tables.

Wheather you Need Help, want to Report A Bug, Request a New Feature or just want to Say Thanks there is someone here to help.

Getting Support

Having trouble getting Tabulator setup? A feature not working the way you think it should? Then there are plenty of ways you can get help.

Checkout the Quick Start Guide for a demo on getting up and running quickly.
Have a look at the working Examples to see if one of those fits the bill.
Search the Documentation for a guide to the section that is giving you trouble.
If you are still out of luck, head over to our Issues Page on GitHub and have a search, see if someone else has already solved your problem. If not, ask your own question, one of the community will get back to you within hours with a helpful response.
When you create an new issue for support please follow these steps:
Make the title short and descriptive so other users can find the issue easily. Please be polite, do not use all capital letters, this will not get your issue dealt with faster.
Make sure you include a detailed description with the issue you are having, mention the browser you have been using and include a screenshot or video if it is a visual issue.
Include a copy of your Tabulator constructor object so we have something to test with.

Found A Bug?

Is Tabulator behaving strangely, have you found a bug? Don't panic, we can fix that in a jiffy!

Head over to our Issues Page on GitHub and have a search to see if anyone else has had the same issue. If so include any info you have from your bug to help us solve the problem faster.
If you can't find the issue already? Create your own. Include as much detail as possible to help us find that pesky bug. A copy of the section of offending code would be great, info on what you are trying to achieve, what browser you are using, all that good stuff.
When you create an new issue for a bug please follow these steps:
Make the title short and descriptive so other users can find the issue easily. Please be polite, do not use all capital letters, this will not get your issue dealt with faster.
Make sure you include a detailed description with the bug you have found, mention the browsers you have been replicated it in and include a screenshot or video if it is a visual issue.
Include a copy of your Tabulator constructor object so we have something to test with.

New Features

Have you just had a spark of inspiration? or found that tabulator is missing that critical feature that would make your life much easier? why not let us know and we will see what we can do to help out.

Head over to our Issues Page on GitHub and have a search, see if someone has already requested the same feature, if so, add your thoughts to the conversation, help guide how Tabulator develops.
If you can't find the feature already, create a new issue and let us know what features we can add to Tabulator to bring a touch of sunshine to your day.
When you create an new issue for a new feature follow these steps:
Make the title short and descriptive so other users can find the issue easily. Please be polite, do not use all capital letters, this will not get your issue dealt with faster.
Include as many details about the feature as possible, including a usage case so we can understand why yhe feature is needed and how it will be used.
If the feature will alter the layout of the table please include an image/mockup of how you expect the feature to work.
If your feeling adventurous, why not fork Tabulator, make your own modifications and then submit the changes back to us in a Pull Request so others can benifit from your new feature. Full details on how to use pull requests with GitHub can be found Here.
When you submit a pull request please follow these steps:
Make the title short and descriptive so other users can find the issue easily.
Make sure that any code changes work with Tabulator as a whole and are designed to increase functionality for all users, not just to add a restricted workaround for a single use case.
Include as many details about the feature as possible, including a usage case so we can understand why yhe feature is needed and how it will be used.

Want to Say Thanks

Enjoying Tabulator? Wanna say thanks to the chap who built it? Aren’t you a lovely person

If you want to show your support for Tabulator, please head over to our GitHub Page and click that Star button in top right hand corner to show other users what you think.
Better yet, why not introduce your developer friends to Tabulator, see if you can make their table building tasks that little bit easier too!