flarum / framework

Simple forum software for building great communities.

About Flarum

Flarum is a delightfully simple discussion platform for your website. It's fast and easy to use, with all the features you need to run a successful community. It is designed to be:

• Fast and simple. No clutter, no bloat, no complex dependencies. Flarum is built with PHP so it’s quick and easy to deploy. The interface is powered by Mithril, a performant JavaScript framework with a tiny footprint.

• Beautiful and responsive. This is forum software for humans. Flarum is carefully designed to be consistent and intuitive across platforms, out-of-the-box.

• Powerful and extensible. Customize, extend, and integrate Flarum to suit your community. Flarum’s architecture is amazingly flexible, with a powerful Extension API.

Installation

This repository contains Flarum's core code. If you want to set up a forum, visit the Flarum skeleton repository. For support, refer to the documentation, and ask questions on Flarum Discuss (our community forum) or Discord server.

Contributing

Thank you for considering contributing to Flarum! Please read the Contributing guide to learn how you can help.

Security Vulnerabilities

If you discover a security vulnerability within Flarum, please send an e-mail to [email protected]. All security vulnerabilities will be promptly addressed. More details can be found in our security policy.

License

Flarum is open-source software licensed under the MIT License.

framework's Issues

Possible mail server problem at flarum.com

Hello!

I tried to sign up on the forum located at discuss.flarum.org but didn't receive a confirmation email. After I have re-sent it, but still nothing happens. I wrote a letter to [email protected] but mail delivery failed. Can you check it please?

Implement discussion title editing

Title editing should work similarly to how it does in esoTalk. Hovering over the title should indicate that it is editable with a dotted border; clicking it should turn it into an input; pressing Enter or Tab should save it, and pressing Escape should revert it.

The API for all of this should(?) be working. I can’t quite remember :3

After registration: make link to email provider open in new tab

This small change would improve the user experience :-)

Cannot reply after logging in

I just visited a thread on the demo forum that I wanted to reply to, but wasn't logged in.
After logging in, the reply button still read "Cannot reply"... needs to be updated when permissions change.

select-input styles broken on Firefox

Styles are in ember/app/styles/flarum/components.less.

New thread: the page doesn't load nothing until you refresh

as per chat:
In the demo of Flarum at demo.flarum.org - I just created a new thread called Test in the category Sandbox. Nothing happens. The browser URL change to this: http://demo.flarum.org/#/d/114/test/1, but I'm still in the discussions list view. Refreshing with that URL and I'm in the discussion now.

Mobile view: No apparent way to close left menu

...apart from clicking on the back arrow file on the right part (which then turns into the menu icon) and then clicking on the menu icon again.

In a perfect world, there would probably be two ways to close the menu: a button as well as the possibility to swipe left to hide the menu.

Implement replying, post editing, discussion creation

The "composer" is the name of the interface component in Flarum's Ember app which handles all post composition, whether it's writing a reply, starting a discussion, or editing a post. It's been prototyped for demoing purposes, but at the moment is completely unfunctional.

The post and discussion-writing APIs are done and should be working for the most part, but may need to be tweaked.

• Redesign, subject to #1
• Make replying functional
• Make editing posts functional
• Make creating discussions functional

Design admin interfaces

This is subject to the finalization of #1.

The administration interface will be wrapped in the default theme. It will be broken up into separate "panes", listed in a sidebar — something like:

• Dashboard: flexible "widgetized" interface (similar to OctoberCMS dashboard)
• Settings: forum title, default language, basic settings
• Appearance: change the colours of the default theme, or change to a different theme
• Permissions: manage user groups and permissions
• Extensions

What needs to be done:

• Define the contents of each pane more precisely
• Mock up each pane

Skinning aspect

I know this is somewhat off the plan path but have you thought about giving more power to designers?

One problem I see with most of frameworks as well a lot of scripts (from end user POV) is the lack of power when it comes to designing. After browsing the source a little and digging into framework behind it, I see it's taking similar approach as ESO did. It's more or less stripping power from designers and limiting them to CSS/LESS tricks with no actual ability to control actual output on per-page render?

I know that with power comes responsibility but there's also freedom with it. :)

Vagrant?

_1 Upvote_ Have you considered dropping in a vagrant box to ensure consistent development environments when developers start forking and working with the codebase?

Set up PHP testing framework and write initial tests

When building this foundational prototype, I neglected to learn how to write tests in the interest of time. However, I realise that tests will be extremely important for the longevity of the project, and I am very keen to adopt a test-driven development approach for Flarum.

I personally need to read up properly about how to actually write and use tests in PHP/Laravel. If anyone would be willing to discuss/set up the necessary testing frameworks (again, I'm pretty uneducated as to what is what - unit? behavioural? acceptance?) that would be great. Don’t worry, I will be making an effort to learn soon!

• Set up backend testing framework(s)
• Write tests for current behaviour (domain and API)
• Proceed with test-driven development

Design user profile interface

_2 Upvotes_ This is subject to the finalization of #1.

The user profile interface needs to be mocked up.

The title area should contain at least the avatar, username, and possibly some other stuff. The background of the title area could potentially be an average color from their avatar (like in iTunes)? Otherwise it can default to the primary/secondary color, depending on the header mode.

Other stuff that needs to be included, either in the title area or just below it:

• Short bio
• Group icons
• Last active, joined
• Basic stats (number of posts, discussions)

Then there will be a content area with a sidebar:

• Activity: display more of the user’s recent activity
• Discussions: display the user’s most recent discussions
• Posts: display the user’s most recent posts

Better API security

Currently all endpoints of the API are open to the public, which may not be ideal. There are some ideas here which we can look at implementing: TryGhost/Ghost#4004

Empty Search Results

When searching for posts that returns zero matches, the page is simply left blank rather than an error message. For instance, when searching for "an awesome search query", zero posts are found, and the page remains completely empty (http://puu.sh/gehn2/9dfeebf485.png).

Show a loading indicator before the Ember app boots

http://discuss.flarum.org/73-performance-flarum-vs-esotalk/p1#p147

Can't install

When I enter this in the terminal git clone [email protected]:flarum/flarum, I get this:

Cloning into 'flarum'...
Warning: Permanently added the RSA host key for IP address '192.30.252.130' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Old browser support

As Ember doesn't support old browser but many users still use them. I think instead show a notification about user update. We should show the information inside 'noscript' tag to user.
More information https://meta.discourse.org/t/make-old-browsers-e-g-opera-mobile-classic-use-the-noscript-version-of-discourse/20716

Refer: #19

db seed error

When i install flarum, i run 'php artisan flarum:seed', throw error below:

PHP Fatal error: Access to undeclared static property: Flarum\Core\Models\Post::$type in /vagrant/system/core/src/Core/Models/Post.php on line 61

well, change to :$post->type = $post::$types; on line61,

Go on running: 'php artisan flarum:seed, throw the error:

preg_replace(): Parameter mismatch, pattern is a string while replacement is an array ,

In the error logs:

[2015-05-08 06:28:39] local.ERROR: exception 'ErrorException' with message 'preg_replace(): Parameter mismatch, pattern is a string while replacement is an array' in /vagrant/system/vendor/laravel/framework/src/Illuminate/Support/helpers.php:703
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'preg_replace():...', '/vagrant/system...', 703, Array)
#1 /vagrant/system/vendor/laravel/framework/src/Illuminate/Support/helpers.php(703): preg_replace('/\\?/', Array, 'insert into `po...', 1)
#2 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/QueryException.php(55): str_replace_array('\\?', Array, 'insert into `po...')
#3 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/QueryException.php(37): Illuminate\Database\QueryException->formatMessage('insert into `po...', Array, Object(ErrorException))
#4 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Connection.php(626): Illuminate\Database\QueryException->__construct('insert into `po...', Array, Object(ErrorException))
#5 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Connection.php(580): Illuminate\Database\Connection->runQueryCallback('insert into `po...', Array, Object(Closure))
#6 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Connection.php(363): Illuminate\Database\Connection->run('insert into `po...', Array, Object(Closure))
#7 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Connection.php(320): Illuminate\Database\Connection->statement('insert into `po...', Array)
#8 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Query/Processors/Processor.php(30): Illuminate\Database\Connection->insert('insert into `po...', Array)
#9 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(1718): Illuminate\Database\Query\Processors\Processor->processInsertGetId(Object(Illuminate\Database\Query\Builder), 'insert into `po...', Array, 'id')
#10 [internal function]: Illuminate\Database\Query\Builder->insertGetId(Array, 'id')
#11 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(933): call_user_func_array(Array, Array)
#12 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1609): Illuminate\Database\Eloquent\Builder->__call('insertGetId', Array)
#13 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1609): Illuminate\Database\Eloquent\Builder->insertGetId(Array, 'id')
#14 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1579): Illuminate\Database\Eloquent\Model->insertAndSetId(Object(Illuminate\Database\Eloquent\Builder), Array)
#15 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1485): Illuminate\Database\Eloquent\Model->performInsert(Object(Illuminate\Database\Eloquent\Builder), Array)
#16 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(529): Illuminate\Database\Eloquent\Model->save()
#17 /vagrant/system/core/src/Core/Seeders/DiscussionsTableSeeder.php(43): Illuminate\Database\Eloquent\Model::create(Array)
#18 /vagrant/system/vendor/laravel/framework/src/Illuminate/Database/Console/SeedCommand.php(57): Flarum\Core\Seeders\DiscussionsTableSeeder->run()
#19 [internal function]: Illuminate\Database\Console\SeedCommand->fire()
#20 /vagrant/system/vendor/laravel/framework/src/Illuminate/Container/Container.php(523): call_user_func_array(Array, Array)
#21 /vagrant/system/vendor/laravel/framework/src/Illuminate/Console/Command.php(115): Illuminate\Container\Container->call(Array)
#22 /vagrant/system/core/vendor/symfony/console/Command/Command.php(259): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArrayInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#23 /vagrant/system/vendor/laravel/framework/src/Illuminate/Console/Command.php(101): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArrayInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#24 /vagrant/system/vendor/laravel/framework/src/Illuminate/Console/Command.php(131): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArrayInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#25 /vagrant/system/core/src/Console/SeedCommand.php(46): Illuminate\Console\Command->call('db:seed', Array)
#26 [internal function]: Flarum\Console\SeedCommand->fire()
#27 /vagrant/system/vendor/laravel/framework/src/Illuminate/Container/Container.php(523): call_user_func_array(Array, Array)
#28 /vagrant/system/vendor/laravel/framework/src/Illuminate/Console/Command.php(115): Illuminate\Container\Container->call(Array)
#29 /vagrant/system/core/vendor/symfony/console/Command/Command.php(259): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#30 /vagrant/system/vendor/laravel/framework/src/Illuminate/Console/Command.php(101): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#31 /vagrant/system/core/vendor/symfony/console/Application.php(878): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#32 /vagrant/system/core/vendor/symfony/console/Application.php(195): Symfony\Component\Console\Application->doRunCommand(Object(Flarum\Console\SeedCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#33 /vagrant/system/core/vendor/symfony/console/Application.php(126): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#34 /vagrant/system/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(94): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#35 /vagrant/system/artisan(11): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#36 {main}  

It's a sql insert error..

Interface redesign

Since revealing Flarum in the Kickstarter campaign, I've been thinking more about the interface design from three equally important aspects:

• Usability. How simple and intuitive the interface is to use for the average joe.
• Theming. How simple and intuitive the interface is to customise for forum admins — both in terms of basic customisation (changing colours) and advanced customisation (changing CSS).
• Extensions. How easy it is for extensions to add functionality to the interface in a consistent manner.

I don't think I quite hit the sweet spot with Flarum's current design:

• Most importantly, there are instances where the sidebar layout doesn't make complete sense. For example, when the two-pane interface is activated, the discussion scrollbar ends up being separated from the discussion itself, which is really counterintuitive.
• It involves some reasonably complex LESS styling, which wouldn't be ideal for themers.
• Overall, the design doesn't convey the level of simplicity and openness that I want it to.

Thus, I'm working on a redesign. The goals for the redesign are:

• To make complete paradigmic sense in terms of the content (which the sidebar concept didn't quite)
• To be very open, clean, and easy to style in an aesthetic sense
• For the CSS behind it to be simpler for ease of customization

Here are some initial mockups:

• Discussion list
• Discussion
• Discussion with multi-pane (Flarum theme)

Some notes:

• Two colors will be configurable by a color picker: a dark primary color and a light secondary color. By default, both of these will be blue. As an example in the Flarum theme, the primary color is orange and the secondary color is blue.
• The header will be able to be switched between two modes: white and colored. By default, it will be in white mode. As an example in the Flarum theme, it is in the colored mode.
• The forum title will be able to be replaced with an image, as in the Flarum theme.
• The links in the header, just to the right of the forum title, won’t display by default when there is only one (Discussions). Extensions will be able to add links (e.g. Members, Website, FAQ).
• The “Welcome” area on the discussion list will be the primary color if the header is in white mode, or the secondary color if the header is in colored mode.
• The title area on a discussion page changes background color according to the channel the discussion is in.
• Hovering over the “back” button in the far left of the discussion title area will cause the discussion list pane to slide out over the content. If the “pin” button is clicked, the content is pushed over and the pane stays there permanently, as shown in the “discussion with multi-pane" mockup.
• I’ve made an effort to keep all interface elements as simple and consistent as possible. For example, all buttons and inputs will be the same height.

Feedback appreciated!

Todo:

• Mock up elements with fixed positioning
• Mock up the post composer
• Mock up modal box
• Style guide
• Begin implementing this design!

User profiles not working

Hi.

After front-end update it is not possible to open user's profile when clicking his login in the thread.

Fix compatibility with latest version of ember-cli

I've been developing with 0.0.40, and I think 0.1.4 is breaking stuff.

User bio not updating

Well, I have entered @tobscure's page at demo.flarum.org.

After I click on my nickname at the top of the page and select "Profile". It opens my profile and shows all information correctly but the bio is still Toby's.

Of course it shows the right bio after reloading the page.

P.S.:Just have discovered that page title is also named as Toby's page.

No migration for forum model

This causes the topic loading on the index page to fail. Crazy hard to debug. The error happens somewhere in the DiscussionSearcher class.

EsoTalk importer for flarum

Hi, am a big fan of you.

I have decided to use Esotalk for my forum. I know Flarum is its successor. my question is

When flarum becomes stable and matured, any plan of an importer that will move esotalk forum content to flarum?

Should we(users of esotalk) expect development / bug fixes for esotalk?

WARNING discussion model

javascript WARNING.

WARNING: The payload for 'flarum@model:discussion:' contains these unknown keys: [readTime]. 
Make sure they've been defined in your model.

The key readTime isn't in discussion, but in discussion-state.

cant close panel on mobile

when I signed in,
and try to change my setting.
it change to setting page,
but the menu panel does't close.

Testing

Hi, I'm lead developer of Codeception testing framework.

I feel your project is really promising. I'm also fan of EmberJS )
If you have any questions on testing with Codeception (I see you already bootstrapped it) or on testing with Ember (which I do for my project as well), please contact me in twitter @davert or directly in Skype: davert.ua.

I hope I can help and long live to flarum!

Use requestAnimationFrame for scroll events

https://gist.github.com/Warry/4254579

Flarun on share hosting

I know its build on Laravel.. is there a chance/way flarum can be installed on a shared-hosting?

JavaScript style guide

• Decide on style guide (this one seems reasonable)
• Implement code sniffer
• Clean up existing code

Starting Post Highlighting Off

When the first unread post is highlighted, it is not centered around the post as one would expect. There is more padding at the top of the post than the bottom.

Install - NFS timeout

When trying to install the vagrant image, everything works great until the point of mounting NFS shared folders, which fails.

Experiment with restructuring app into pods

This is the way Ember 2.0 is heading, and it's probably a better structure for a large-scale app like this. ember-cli documentation contains some info about it.

SEO Features!

Hey Toby and other contributors, I would like to suggest some basic and standard SEO features that should be included inside Flarum core.

1. SEO Friendly Url
2. Canonical tag
3. Noindex for subpages (page/2 for posts)
4. Auto generate meta description using post exceprt
5. A box under editor box for post starter to enter meta keywords (this could be enable and disable based on role (admin, mod, user, etc)

I will be adding more if necessary. Thanks for the forum software.

CommonMark as default markup syntax

Using CommonMark as default markup syntax?
https://github.com/jgm/CommonMark

Click+dragging horizontally on the stream scrubber produces 'NaN of # posts'

Couldn't reproduce consistently, but managed here: http://demo.flarum.org/#/d/107/update-introducing-flarum-s-fast-new-front-end/1

Implement post deletion

_1 Upvote_ Posts should be able to be soft-deleted (hidden) so that they only appear to people who have permission to restore them (author + whichever groups have permission.)

Additionally, users with the correct permissions should be able to delete a hidden post permanently.

The API for all of this should(?) be working. I can’t quite remember :3

Develop user authentication strategy

Users will need to be able to authenticate (log in) through the API. It needs to be reasonably secure over both HTTP and HTTPS, just like a standard PHP form login.

I'm unsure of the best way to approach this — presumably just have an endpoint that takes a username/password and gives back a token?

Discuss. Does anyone want to lead this?

Upgrade to Laravel 5

Currently Flarum is running on Laravel 4.2. We will want to begin the transition to Laravel 5 sooner rather than later.

I don't know how stable Laravel 5 is at the moment, but I can't imagine that the changes will really affect Flarum's code that much. Can anyone who is more familiar with the changes in Laravel 5 comment?

Error when clicking notification of moved topic

I get this error when I click the notification saying you had moved my "http://demo.flarum.org/#/d/109/pinned-discussion-should-be-above-me/1" topic to the sandbox.

NotFoundHttpException inRouteCollection.php line 145:

in RouteCollection.php line 145at RouteCollection->match(object(Request)) inRouter.php line 729at Router->findRoute(object(Request)) in Router.php line 652at Router->dispatchToRoute(object(Request)) inRouter.php line 628at Router->dispatch(object(Request)) in Kernel.php line 214at Kernel->Illuminate\Foundation\Http{closure}(object(Request))at call_user_func(object(Closure), object(Request)) inPipeline.php line 141at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in ShareErrorsFromSession.php line 55at ShareErrorsFromSession->handle(object(Request),object(Closure)) in Pipeline.php line 125at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in StartSession.php line 61at StartSession->handle(object(Request),object(Closure)) in Pipeline.php line 125at Pipeline->Illuminate\Pipeline{closure}(object(Request)) inAddQueuedCookiesToResponse.php line 36at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 125at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in EncryptCookies.php line 40at EncryptCookies->handle(object(Request),object(Closure)) in Pipeline.php line 125at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in CheckForMaintenanceMode.php line 42at CheckForMaintenanceMode->handle(object(Request),object(Closure)) in Pipeline.php line 125at Pipeline->Illuminate\Pipeline{closure}(object(Request))at call_user_func(object(Closure), object(Request)) inPipeline.php line 101at Pipeline->then(object(Closure)) in Kernel.php line 115at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 84at Kernel->handle(object(Request)) in index.php line 9

Set up JavaScript testing framework and write initial tests

Now that we're using Mithril, we have complete freedom over what we use and how we use it.

A good starting point might be to copy whatever Mithril does itself.

CLA explanation

I suck at legalese, but does this mean you can (at any point in time) put a closed source license on the project (including all 3rd party contributions)?

By contributing your code to Flarum you grant Toby Zerner a non-exclusive, irrevocable, worldwide, royalty-free, sublicenseable, transferable license under all of Your relevant intellectual property rights (including copyright, patent, and any other rights), to use, copy, prepare derivative works of, distribute and publicly perform and display the Contributions on any licensing terms, including without limitation: (a) open source licenses like the MIT license; and (b) binary, proprietary, or commercial licenses.

Build Notifications system

_1 Upvote_ Flarum's core will need to have a notification framework in place for extensions to make use of.

This should be loosely based on esoTalk's notifications/activity model. You can read about how that works in the esoTalk documentation. Also, the esoTalk source is well-commented — take a look at that if you are interested in this.

I’ll write more about this as it becomes more of a priority.

Installing Flarum

Hello. As I understand I need to use virtual machines and other virtualization stuff to use the forum.
Is it possible to install it as esoTalk by uploading to the hosting and just going to installation page?

can see the UI to upload user image in everyone's profile page.

http://demo.flarum.org/#/u/Toby
I signed as my account,
but I can see the upload UI on orther's profile page

install exception

 [Illuminate\Database\QueryException]
  SQLSTATE[HY000]: General error: 1364 Field 'html_content' doesn't have a default value (SQL: insert i
  nto `posts` (`discussion_id`, `number`, `time`, `user_id`, `type`, `content`) values (1, 1, 2014-04-0
  1 03:31:06, 92, comment, WAS a curious dream!' said Alice, who felt very curious thing, and she said
  to herself 'Suppose it should be free of them with the words came very queer to ME.' 'You!' said the
  cook. 'Treacle,' said the Queen, the royal children, and everybody else. 'Leave off that!' screamed t
  he Pigeon. 'I can tell you what year it is?' 'Of course you know why it's called a whiting?' 'I never
   went to work nibbling at the Duchess said to herself; 'I should like to be true): If she should push
   the matter on, What would become of me? They're dreadfully fond of pretending to be rude, so she wen
  t on at last, with a bound into the air, mixed up with the birds and animals that had a vague sort of
   way, 'Do cats eat bats, I wonder?' As she said to Alice, that she wasn't a bit of the evening, beaut
  iful Soup! Soup of the shepherd boy--and the sneeze of the teacups as the.))

  [PDOException]
  SQLSTATE[HY000]: General error: 1364 Field 'html_content' doesn't have a default value

  [Illuminate\Database\QueryException]
  SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'number_index' cannot be null (SQL: upda
  te `discussions` set `posts_count` = 38, `start_post_id` = 1404, `last_time` = 2014-05-14 19:49:12, `
  last_user_id` = 12, `last_post_id` = 1442, `last_post_number` = , `number_index` =  where `id` = 72)


  [PDOException]
  SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'number_index' cannot be null

SEO

_1 Upvote_ For SEO, Flarum's Laravel app needs to respond to the same URLs as in the Ember app, serving up very basic semantically-correct HTML within <noscript> tags. Additionally, the Laravel app should preload the page's data into the Ember Data store to avoid the need for additional requests after the page loads.

Add validation to limit discussion title length

There should be a smaller limit on the length of a discussion title (60 characters?)

Implement discussion deletion

Discussions should be able to be deleted, taking all their posts with them. No soft-delete for now.

The API for all of this should(?) be working. I can’t quite remember :3