A slim, lean forum package designed for quick and easy integration in Laravel projects

I'm just getting to grips with the codebase at the moment, and have written a set of importers to import our current forum from phpBB.

We have about 2000 threads and 20,000 posts - I have successfully imported our users separately, and then populated forum_categories, forum_threads and forum_posts and everything appears to be working the only issue at the moment is the massive number of queries that occurs on the forum index.

I am currently getting 4082 queries on forum index, which is 9 categories (under 3 title categories) - which seems way too much.

Taking a look at laravel debugbar I am seeing this - http://i.imgur.com/SCw1DSa.png

It repeats alternating between querying users and forum_posts for the majority of the 4000 queries.

So, two questions I suppose;

• Is there another table I should be populating with additional information? I thought perhaps threads read might be the issue, perhaps?
• Any ideas what else could be causing this? Have you tested the forums with a large amount of threads and posts?

Cheers

Hi! Now category format in url represent as like "https://forum.site/category/thread/post". How use subdomains with names equal category, like "https://category.forum.site/thread/post" for all content? I see you have a complex routing system, I would like to use something like:

Route::group(['domain' => '{subdomain}.forum.site'], function () {

in router file like /vendor/riari/laravel-forum/routes.php

Also, how publish it to it not changing if I update package?

this is what i currently see when upgrading to PHP7

Specifically it has to deal with this line:

$this->collections[$model] = $this->$map_model_repos[$model]->getByID($id, $with);

would you have any idea on how to fix this?

i followed bellow instructions

1.composer require riari/laravel-forum:~3.0

2.Then add the service provider to your config/app.php: Riari\Forum\ForumServiceProvider::class,

3.composer require riari/laravel-forum-frontend:~1.0 Riari\Forum\Frontend\ForumFrontendServiceProvider::class,

4.php artisan vendor:publish

5.php artisan migrate

6.then click on mydomaiin.com/forum

i got a this error

Invalid argument supplied for foreach() (View: /var/www/html/resources/views/vendor/forum/category/index.blade.php)

in Category_controller you guys are mention columns name 'category_id ' but in db table only 'id ' column there .any reason for that ?

Can you add the ability to move threads to different categories and Edit thread titles cause sometimes someone makes a mistake and there isnt a way to edit the title besides the db)

Hello Rick.

The short story: I'm having issues with your system when integrated with Wave SAAS (https://github.com/thedevdojo/wave). Would you be able to help?

A bit more info: Devdojo is kindly working with me quite some time after I integrated laravel-forum. But it's getting kind of difficult now since seems that any possible solution might be done at laravel-forum. Here is the post related to this issue: https://devdojo.com/question/404-not-found

Would you be able to do the same effort? I mean, install their software and then your package. If you kindly be able to do so, then here is my installation process:

1. Install Wave SAAS

• https://wave.devdojo.com/docs/installation
• If you get redis error, try composer update --ignore-platform-req=ext-redis
• If you get migration error copy the below code at config/database php, Ln: 60 (mysql engine) --> 'engine' => 'InnoDB ROW_FORMAT=DYNAMIC',

2. Proof that Wave Blog works before laravel-forum.

• Visit: Wave Blog link, click any article. You should be able to read any article. Meaning, that there no error.

3. Install laravel-forum 5.0 --> You might want to ignore redis if you had trouble before. --> composer require riari/laravel-forum:~5.0 --ignore-platform-req=ext-redis

4. Re-visit Wave Blog Page and click any article. You should get an 404 | NOT FOUND error.

Thank you in advance

Hi, I’ve noticed that paging doesn’t work on API methods (not implemented). I’ve added support to enable paging on the API calls (thread, categories, posts). Only category list is not perfect - there is a filter which removes private categories after the query is done. The paginate will return data, but the total count is not accurate (based on the private settings).

We can disable paging for categories by setting 0.

To enable paging set true in the config: forum.preferences.pagination.enabled

i have succeeded in integrating laravel and forum but one thing is left, the web guard middleware enbles session in laravel 5.2, so when i run /forum i get this errors:

ErrorException in 6829460faf86e4b23bc8a19c8baa92dc4b035c9e.php line 7: Undefined variable: errors (View: C:\wamp\www\agron\resources\views\vendor\forum\partials\alerts.blade.php) (View: C:\wamp\www\agron\resources\views\vendor\forum\partials\alerts.blade.php) (View: C:\wamp\www\agron\resources\views\vendor\forum\partials\alerts.blade.php)

Hello, thanks for the amazing work!

I've finally managed to get it working, but there's one problem that I can't seem to solve after reading documents and articles online, which is to use policy to permit certain action.

What I wanna do is just like the demo, different user has their own permission, however no matter how I configure the code it's always allowed any users to do something only the admin should be able to do.

I have been searching for the policy code, but can't find it, I was wondering if you could help~

I'm trying to override the create and store method in the Thread Controller. I extended it, and made a create method, but it doesn't work. The reason for this is because i disabled the integrated permissions and would like to use my own and the one you have is directly in the controller file.

Missing required parameter for [Route: forum.thread.show] [URI: forum/t/{thread}-{thread_slug}] [Missing parameter: thread_slug].

Hello, it's me again it's kinda werid that it works fine on my localhost, but when I uploaded it onto my server and when I tried to test it, I accidently leave content as blank, and it gave me the above message.

and when I am typing this here, I figure I might as well just delete the post from the DB, and when I went in there I found five or six same posts, and when delete them it's back and works fine.

I was wondering if this could cause any problem since user tend to make this kind of mistake.

The package should support an optional 'accepted post' feature, whereby a post can be marked as accepted by a user who has permission (by default, the thread author) to do so. This can be useful for Q&A categories, but could have other use cases.

The package should support optional feeatures via a feature flagging system. Initially, the API and web routes could be enabled/disabled via this system.

The package should have configurable and overridable pipelines for transforming post content before it's written to or after it's read from the database. This will make integration of WYSIWYGs much easier.

By default, it should provide a pipeline for Markdown support.

More details in https://github.com/Team-Tea-Time/laravel-forum/issues/275.

The package should be able to provide multiple presets, similar to how Laravel UI works. Initially, it should support Bootstrap and Tailwind presets.

• It should support UIs that consume the API using Vue (either as an SPA or using Inertia, or possibly both).
• It should retain the option to publish a specific UI to the application directory for easier overriding.
• It will require changes to config to support more than one UI, as well as UIs that use the API routes instead of web routes.