Split Flarum posts into a new discussion
License: MIT License
Allows splitting posts from discussions.
composer require fof/split:"*"The initial release was patched up, forked and released by Davis under his name with our permission. Without that last burst of effort this extension would have most likely been delayed for ages, thank you!
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
This feature will be a good addition to this extension only if split posts and add to an existing discussion enhancement is done
#44
allow splitting the first post too, if the discussion has no posts after splitting the first post soft delete it.
if this feature is possible we no longer need the merge extension too
Liberty reported he was unable to split two posts from the meta, blog tag. He's able to see the controls but the api throws a 401. The permission grid looks fine though.
Flarum by default only allow titles with max length of 80 chars, but when you split a discussion and write the new title, you can insert unlimited chars. I think that the same limit of 80 chars should be applied.
It was tested under Flarum Beta 11.1 with latest version of split extension. Tryed to clear cache and retry, but the problem remains.
Hope it can be fixed.
Steps to reproduce:
Screenshot (the button is missing after a certain post):
To make our logic a little more sane, let's no longer save the full slug to the discussion to the database.
Current Behavior
If you start the split from a post with [deleted] user, the split fails with a 500 error.
Steps to Reproduce
Error message from log file:
[2021-06-02 23:13:04] flarum.ERROR: TypeError: Argument 2 passed to Flarum\Discussion\Discussion::start() must be an instance of Flarum\User\User, null given, called in /home/clark/Projects/flarum-1.0/vendor/fof/split/src/Api/Commands/SplitDiscussionHandler.php on line 97 and defined in /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Discussion/Discussion.php:120
Stack trace:
#0 /home/clark/Projects/flarum-1.0/vendor/fof/split/src/Api/Commands/SplitDiscussionHandler.php(97): Flarum\Discussion\Discussion::start()
#1 /home/clark/Projects/flarum-1.0/vendor/illuminate/bus/Dispatcher.php(122): FoF\Split\Api\Commands\SplitDiscussionHandler->handle()
#2 /home/clark/Projects/flarum-1.0/vendor/illuminate/pipeline/Pipeline.php(128): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}()
#3 /home/clark/Projects/flarum-1.0/vendor/illuminate/pipeline/Pipeline.php(103): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}()
#4 /home/clark/Projects/flarum-1.0/vendor/illuminate/bus/Dispatcher.php(132): Illuminate\Pipeline\Pipeline->then()
#5 /home/clark/Projects/flarum-1.0/vendor/illuminate/bus/Dispatcher.php(78): Illuminate\Bus\Dispatcher->dispatchNow()
#6 /home/clark/Projects/flarum-1.0/vendor/fof/split/src/Api/Controllers/SplitController.php(61): Illuminate\Bus\Dispatcher->dispatch()
#7 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Api/Controller/AbstractSerializeController.php(110): FoF\Split\Api\Controllers\SplitController->data()
#8 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/RouteHandlerFactory.php(41): Flarum\Api\Controller\AbstractSerializeController->handle()
#9 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/ExecuteRoute.php(27): Flarum\Http\RouteHandlerFactory->Flarum\Http\{closure}()
#10 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\ExecuteRoute->process()
#11 /home/clark/Projects/flarum-1.0/workbench/flarum-ext-audit/src/Middlewares/ExtendSetPermissionController.php(19): Laminas\Stratigility\Next->handle()
#12 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Kilowhat\Audit\Middlewares\ExtendSetPermissionController->process()
#13 /home/clark/Projects/flarum-1.0/workbench/flarum-ext-audit/src/Middlewares/SetLoggerActor.php(28): Laminas\Stratigility\Next->handle()
#14 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Kilowhat\Audit\Middlewares\SetLoggerActor->process()
#15 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Api/Middleware/ThrottleApi.php(33): Laminas\Stratigility\Next->handle()
#16 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Api\Middleware\ThrottleApi->process()
#17 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/CheckCsrfToken.php(44): Laminas\Stratigility\Next->handle()
#18 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\CheckCsrfToken->process()
#19 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/ResolveRoute.php(67): Laminas\Stratigility\Next->handle()
#20 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\ResolveRoute->process()
#21 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/SetLocale.php(51): Laminas\Stratigility\Next->handle()
#22 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\SetLocale->process()
#23 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/AuthenticateWithHeader.php(56): Laminas\Stratigility\Next->handle()
#24 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\AuthenticateWithHeader->process()
#25 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/AuthenticateWithSession.php(31): Laminas\Stratigility\Next->handle()
#26 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\AuthenticateWithSession->process()
#27 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/RememberFromCookie.php(52): Laminas\Stratigility\Next->handle()
#28 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\RememberFromCookie->process()
#29 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/StartSession.php(61): Laminas\Stratigility\Next->handle()
#30 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\StartSession->process()
#31 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Api/Middleware/FakeHttpMethods.php(29): Laminas\Stratigility\Next->handle()
#32 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Api\Middleware\FakeHttpMethods->process()
#33 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/ParseJsonBody.php(28): Laminas\Stratigility\Next->handle()
#34 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\ParseJsonBody->process()
#35 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/HandleErrors.php(57): Laminas\Stratigility\Next->handle()
#36 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\HandleErrors->process()
#37 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/InjectActorReference.php(25): Laminas\Stratigility\Next->handle()
#38 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\InjectActorReference->process()
#39 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(84): Laminas\Stratigility\Next->handle()
#40 /home/clark/Projects/flarum-1.0/vendor/middlewares/request-handler/src/RequestHandler.php(84): Laminas\Stratigility\MiddlewarePipe->process()
#41 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Middlewares\RequestHandler->process()
#42 /home/clark/Projects/flarum-1.0/vendor/middlewares/base-path-router/src/BasePathRouter.php(101): Laminas\Stratigility\Next->handle()
#43 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Middlewares\BasePathRouter->process()
#44 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Middleware/OriginalMessages.php(42): Laminas\Stratigility\Next->handle()
#45 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Laminas\Stratigility\Middleware\OriginalMessages->process()
#46 /home/clark/Projects/flarum-1.0/vendor/middlewares/base-path/src/BasePath.php(73): Laminas\Stratigility\Next->handle()
#47 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Middlewares\BasePath->process()
#48 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Middleware/ProcessIp.php(24): Laminas\Stratigility\Next->handle()
#49 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/Next.php(61): Flarum\Http\Middleware\ProcessIp->process()
#50 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(84): Laminas\Stratigility\Next->handle()
#51 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(73): Laminas\Stratigility\MiddlewarePipe->process()
#52 /home/clark/Projects/flarum-1.0/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(96): Laminas\Stratigility\MiddlewarePipe->handle()
#53 /home/clark/Projects/flarum-1.0/vendor/flarum/core/src/Http/Server.php(44): Laminas\HttpHandlerRunner\RequestHandlerRunner->run()
#54 /home/clark/Projects/flarum-1.0/public/index.php(26): Flarum\Http\Server->listen()
#55 {main}
Screenshots
(modal backdrop altered to better show what's behind it)
Environment
Possible solution(s)
The problem is that Flarum's Discussion::start() method does not accept null as the author. I don't think there's an issue for it at the Flarum level yet.
A workaround would be to create the discussion model without using Discussion::start.
Before stable release design and use a nice logo 😄
Tag changing modal doesn't disappear when I split post from the original one to under the new discussion. I don't know it's happening because of FoF Split but I wanted to report it.
Steps to Reproduce
Expected Behavior
The modal should be closed after saving the changes or closing the model.
Environment
Flarum core: 1.8.5
PHP version: 8.0.26
MySQL version: 8.0.31-cll-lve
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bz2, calendar, ctype, curl, hash, filter, ftp, gettext, gmp, SPL, iconv, json, pcntl, readline, Reflection, session, standard, shmop, SimpleXML, mbstring, tokenizer, xml, i360, bcmath, dom, fileinfo, gd, igbinary, imagick, imap, intl, exif, mcrypt, mysqlnd, mysqli, PDO, pdo_mysql, pdo_sqlite, Phar, posix, soap, sockets, xmlreader, xmlwriter, xsl, zip, Zend OPcache
+------------------------------------+---------+--------+
| Flarum Extensions | | |
+------------------------------------+---------+--------+
| ID | Version | Commit |
+------------------------------------+---------+--------+
| flarum-tags | v1.8.0 | |
| flarum-mentions | v1.8.3 | |
| flarum-subscriptions | v1.8.0 | |
| fof-sitemap | 2.2.1 | |
| fof-impersonate | 1.1.1 | |
| flamarkt-backoffice | 0.1.3 | |
| fof-follow-tags | 1.2.2 | |
| flarum-markdown | v1.8.0 | |
| webbinaro-calendar | 1.7.0 | |
| v17development-user-badges | v1.1.0 | |
| v17development-seo | v1.8.0 | |
| tohsakarat-tags-filter | v1.0.5 | |
| sycho-private-facade | v0.1.16 | |
| nearata-internal-links-noreload | v2.2.0 | |
| ianm-boring-avatars | 1.0.0 | |
| ganuonglachanh-search | 0.5.2 | |
| fof-upload | 1.5.4 | |
| fof-split | 1.1.1 | |
| fof-pretty-mail | 1.1.2 | |
| fof-polls | 2.1.2 | |
| fof-moderator-notes | 1.2.2 | |
| fof-merge-discussions | 1.4.1 | |
| fof-links | 1.2.2 | |
| fof-linguist | 1.1.2 | |
| fof-formatting | 1.0.3 | |
| fof-default-user-preferences | 1.2.1 | |
| fof-best-answer | 1.4.1 | |
| flarum-suspend | v1.8.1 | |
| flarum-sticky | v1.8.0 | |
| flarum-pusher | v1.8.0 | |
| flarum-nicknames | v1.8.0 | |
| flarum-lock | v1.8.0 | |
| flarum-lang-turkish | 1.25.0 | |
| flarum-extension-manager | v1.0.2 | |
| datlechin-simple-tour-guide | v0.0.1 | |
| datlechin-offline-indicator | v0.1.0 | |
| datlechin-keyboard-shortcuts | v0.1.1 | |
| datlechin-discussion-overview | v0.0.1 | |
| club-1-cross-references | v1.1.1 | |
| clarkwinkelmann-who-read | 1.4.1 | |
| clarkwinkelmann-post-stream-search | 1.1.0 | |
| blomstra-turnstile | 0.1.4 | |
| blomstra-sort-order-toggle | 0.2.0 | |
| blomstra-database-queue | 1.1.0 | |
| blomstra-cache-assets | 0.5 | |
| betterflarum-bettermobiledrawer | 2.2.0 | |
| askvortsov-pwa | v3.3.3 | |
| askvortsov-markdown-tables | v1.2.1 | |
| askvortsov-help-tags | v1.1.0 | |
| askvortsov-checklist | v1.3.1 | |
| acpl-lscache | v2.3.1 | |
+------------------------------------+---------+--------+
Base URL: https://support.bw.agency
Installation path: /home/samsunek/support.bw.agency
Queue driver: database
Session driver: file
Scheduler status: Aktif
Mail driver: smtp
Debug mode: off
Current Behavior
When the split function is used to move posts to another discussion, then the source discussion is shown as read even when there are new posts in it.
Steps to Reproduce
Expected Behavior
The discussion should be marked as unread if there are new posts
Additional Context
According to the user matteocontrini who first reported the issue on Discuss, the issue will resolve itself once the number of new posts exceeds the number of moved posts. Also, he said the issue is observable only by the user who performed the split, I cannot confirm this, hasn't tested with many different users.
Hi There,
great repo!
problem : I make a new split, I go to the split page, I change the title, I go to the main thread but the title & url is not changed (although the redirect works fine) .
question : is this work by design? potential bug of flarum or flagrow/split ?
thanks
Let's validate that splitting from post 1 in a dicussion does not break our functionality. It should set the first not-split post as OP in this case.
When renaming a discussion, I'm seeing he following exception logged. The discussion is renamed, but the API request returns 500 and the user is shown an error.
[2019-06-21 11:30:29] production.ERROR: BadMethodCallException: Call to undefined method Illuminate\Database\Query\Builder::getContent() in /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/database/Query/Builder.php:2483
Stack trace:
#0 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/database/Eloquent/Builder.php(1286): Illuminate\Database\Query\Builder->__call('getContent', Array)
#1 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/database/Eloquent/Model.php(1477): Illuminate\Database\Eloquent\Builder->__call('getContent', Array)
#2 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flarum/core/src/Database/AbstractModel.php(204): Illuminate\Database\Eloquent\Model->__call('getContent', Array)
#3 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flagrow/split/src/Listeners/UpdateSplitTitleAfterDiscussionWasRenamed.php(63): Flarum\Database\AbstractModel->__call('getContent', Array)
#4 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/support/Collection.php(339): Flagrow\Split\Listeners\UpdateSplitTitleAfterDiscussionWasRenamed->Flagrow\Split\Listeners\{closure}(Object(Flagrow\Split\Posts\DiscussionSplitPost), 0)
#5 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flagrow/split/src/Listeners/UpdateSplitTitleAfterDiscussionWasRenamed.php(69): Illuminate\Support\Collection->each(Object(Closure))
#6 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/database/Concerns/BuildsQueries.php(39): Flagrow\Split\Listeners\UpdateSplitTitleAfterDiscussionWasRenamed->Flagrow\Split\Listeners\{closure}(Object(Illuminate\Database\Eloquent\Collection), 1)
#7 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flagrow/split/src/Listeners/UpdateSplitTitleAfterDiscussionWasRenamed.php(70): Illuminate\Database\Eloquent\Builder->chunk(10, Object(Closure))
#8 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/events/Dispatcher.php(350): Flagrow\Split\Listeners\UpdateSplitTitleAfterDiscussionWasRenamed->whenRenamed(Object(Flarum\Discussion\Event\Renamed))
#9 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/events/Dispatcher.php(200): Illuminate\Events\Dispatcher->Illuminate\Events\{closure}('Flarum\\Discussi...', Array)
#10 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flarum/core/src/Foundation/DispatchEventsTrait.php(35): Illuminate\Events\Dispatcher->dispatch('Flarum\\Discussi...')
#11 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flarum/core/src/Discussion/Command/EditDiscussionHandler.php(85): Flarum\Discussion\Command\EditDiscussionHandler->dispatchEventsFor(Object(Flarum\Discussion\Discussion), Object(Flarum\User\User))
#12 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/bus/Dispatcher.php(90): Flarum\Discussion\Command\EditDiscussionHandler->handle(Object(Flarum\Discussion\Command\EditDiscussion))
#13 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/pipeline/Pipeline.php(114): Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}(Object(Flarum\Discussion\Command\EditDiscussion))
#14 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/pipeline/Pipeline.php(102): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Flarum\Discussion\Command\EditDiscussion))
#15 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/bus/Dispatcher.php(98): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#16 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/illuminate/bus/Dispatcher.php(76): Illuminate\Bus\Dispatcher->dispatchNow(Object(Flarum\Discussion\Command\EditDiscussion))
#17 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flarum/core/src/Api/Controller/UpdateDiscussionController.php(52): Illuminate\Bus\Dispatcher->dispatch(Object(Flarum\Discussion\Command\EditDiscussion))
#18 /usr/local/openresty/nginx/www/fibraclick-forum/vendor/flarum/core/src/Api/Controller/AbstractSerializeController.php(98): Flarum\Api\Controller\UpdateDiscussionController->data(Object(Zend\Diactoros\ServerRequest), Object(Tobscure\JsonApi\Document))
[... omitted]
It happens only with a particular discussion (or maybe others as well, but not all), and only after updating to beta8.
The exception seems to refer to something happening in this extension, although the discussion having the issue is not a discussion that was generated with a split. Some messages inside it were split to new discussions though.
Flarum info:
Flarum core 0.1.0-beta.8.2
PHP version: 7.2.17-0ubuntu0.18.04.1
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, pcntl, Reflection, SPL, sodium, session, standard, mysqlnd, PDO, xml, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, iconv, json, exif, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xmlreader, xmlwriter, xsl, Zend OPcache
+------------------------------+-----------------+------------------------------------------+
| Flarum Extensions | | |
+------------------------------+-----------------+------------------------------------------+
| ID | Version | Commit |
+------------------------------+-----------------+------------------------------------------+
| flarum-bbcode | v0.1.0-beta.8 | |
| flarum-emoji | v0.1.0-beta.8 | |
| flarum-flags | v0.1.0-beta.8.1 | |
| flarum-likes | v0.1.0-beta.8.1 | |
| flarum-markdown | v0.1.0-beta.8 | |
| flarum-sticky | v0.1.0-beta.8 | |
| flarum-suspend | v0.1.0-beta.8 | |
| flarum-tags | v0.1.0-beta.8.2 | |
| flarum-approval | v0.1.0-beta.8 | |
| flarum-mentions | dev-fc8 | ad509a766e73f14b8bb04e13d0b33c86d315f47b |
| flarum-lock | v0.1.0-beta.8 | |
| flarum-subscriptions | dev-fc8 | 83964f639e54276167b58153e6d4e97da5b0a4f4 |
| flarum-lang-english | v0.1.0-beta.8 | |
| flarum-statistics | v0.1.0-beta.8 | |
| flarum-auth-github | v0.1.0-beta.8 | |
| flarum-auth-facebook | v0.1.0-beta.8 | |
| flarum-auth-twitter | v0.1.0-beta.8 | |
| flarum-pusher | v0.1.0-beta.8.1 | |
| flagrow-analytics | 0.8.0 | |
| fof-links | 0.2.0 | |
| flagrow-split | 0.3.2 | |
| fof-user-bio | 0.1.2 | |
| matteocontrini-imgur-upload | v3.3.0 | |
| clarkwinkelmann-emojionearea | 0.2.0 | |
| flagrow-ads | 0.2.0-beta.1 | |
| botfactoryit-italian | dev-master | dd79523a18c18c7583926c1f863804ed2bfc09e5 |
| reflar-stopforumspam | 0.1.5 | |
| flagrow-impersonate | 0.2.0 | |
| flagrow-sitemap | 0.2.0 | |
| fof-share-social | 0.1.0 | |
| v17development-seo | 1.0.1 | |
| fof-default-user-preferences | 0.1.0 | |
+------------------------------+-----------------+------------------------------------------+
Base URL: https://forum.fibra.click
Installation path: /usr/local/openresty/nginx/www/fibraclick-forum
Debug mode: off
as we already know sometimes we are getting errors while merging comments
split extension is only useful to create new discussion, we can only separate single comment but If we use split to separate the comment and try to merge newly created discussion into different old discussion our merge discussions extension pops out a error.
We need "move single reply" to another discussion feature.
so we can just move the comments to different discussions without splitting or merging.
Once we move single comment from newly created discussion we can manually delete empty discussion
We request you to bring a "move comment feature"
Hi, i love this extension and believe is very useful but seems are missing some useful functions.
Seems right now you can split a message in the thread to a new thread.
I believe will be nice to be able to split a post to another existent post too also with different tags, if this is not possible directly from the first thread will be useful split the post in a new thread than be able in this thread to use again the split function that now is not showed in a first post for split into an existing thread with different tags.
Actually seems you can split a message only in a new thread not in existent discussion, will be nice to be able to do this, in future.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
