Getting Help

Stack Exchange

UserFrosting has its very own Stack Overflow tag.

Also, remember that UserFrosting builds on top of a number of very popular and well-supported packages. Although you can search for questions specifically tagged with userfrosting, you should also ask yourself if your question is really about UserFrosting in particular, or about one of the many technologies it builds upon. For example, many questions we get in chat are actually about:

If you have a specific, well-researched question, you may consider posting it to one of:

Tag your question as userfrosting, as well as any other relevant tags (twig, slim, eloquent, rest, jquery, etc). Before posting to any Stack community, please make sure your question conforms to their question guidelines! If your question is more open-ended or opinion-based, you should probably just ask directly in chat.

Once you post a question to Stack Overflow, you should post a link to your question in chat for the fastest response.

You may also find the following communities useful in certain cases:


Our forums, built on the excellent Discourse project and hosted courtesy of Nextgi, can be found at


UserFrosting has its very own chat room, built with and hosted thanks to the generous donations of viewers like you! Please feel free to stop by any time - we'd love to chat with you and help you out! You may sign in with your GitHub or Twitter account. But first, please note the following:


After joining chat, please be sure to choose the appropriate channel:

  • #support: Use this channel to get help.
  • #general: Use this channel if you're bored and you just want to chat, or if you want to discuss something about UF that doesn't belong in #support.
  • #github-activity: Automated notifications from Github. Please do not post in this channel.

Generally speaking, you're more likely to get a quick response if you post in #support rather than PMing Alex or another user directly.

Chat Rules

This is a public chat room.

Please be civil and respectful.

Don't ask to ask.

Just ask.

Your question may have been answered before.

Check Stack Overflow, the issue tracker, and the wiki first. You can also try searching the chat history in the sidebar.

Use Markdown to format blocks of code.

Markdown is the de facto standard for basic text formatting on the web. If you are unfamiliar with Markdown, please take a few minutes to learn. It will help you not just here, but all over the web! In particular, please make sure you know where the backtick key (`) is located on your keyboard:

Location of backtick key

Inline code

Use single backticks (`) to format inline code:

So you're telling me that `$user->owls()->count()` should work?
Short blocks of code

Use triple backticks (```) to format code blocks:

public function foo();

Note that for code blocks, each set of backticks must be on its own line. Use Shift+Enter to insert new lines into your message.

Longer blocks of code

For larger blocks of code, please paste into a Gist and then link to your Gist in chat.


The easiest way to share images with us, such as screenshots, is to simply drag them into the chat window. Please do not upload anything that contains sensitive or private content.

Set an avatar for yourself.

Click the arrow next to your username in the upper left corner, and go to "My Account" => "Avatar".


Our GitHub issue tracker is reserved for feature requests and bug reports only. For troubleshooting and general questions, you should ask on Stack Overflow and/or chat!

We also have a wiki, where you can find user-supplied guides and other content.

General tips for support

On Github, UserFrosting Chat, and Stack Overflow, please keep in mind the following:

  1. Remember that courtesy and proper grammar go a long way. Please take the time to craft a precise, polite issue. We will do our best to help, but remember that this is an open-source project - none of us are getting paid a salary to develop this project, or act as your personal support hotline ;-)

  2. Report any errors in detail. Vague issues like "it doesn't work when I do this" are not helpful. Show that you have put some effort into identifying the cause of the error. See the previous section for information on how to get more details about errors and other problems.

  3. You should always test your code in a local development environment, to separate code-related issues from server issues. In general, we recommend that you install a local development server on your computer, rather than testing your code directly on the production server. This means you can test your code directly on your own computer, making development faster and without the risk of exposing sensitive information to the public. We recommend installing Vagrant and Homestead if you don't already have a local server set up.