FriendsOfFlarum Byōbu, well integrated, advanced private discussions

Justman10000

IanM

composer require fof/byobu:^1.0.0-beta.7

Why didn't you just set that to composer require fof/byobu?

IanM

Justman10000 because this extension is not yet stable, hence the beta tag

Justman10000

IanM

Oh, as a hint, so to speak?

shebaoting

shebaoting How do I solve this problem?

shebaoting

Solved. Because this extension was previously installed.
But it did not make a judgment on the database when it was installed again.

Solution, add migration records

2019_07_08_000000_add_blocks_pd_to_users
2019_07_09_000000_blocks_pd_index

shebaoting

I would like to know how to involve specific groups in the discussion?

Walys

Like this extension!
But some questions

have any date to go with stable version? Maybe some days, weeks, months....
have any future idea to implement this extension to flarum core @luceos ? Or go with other system in the future for private message? I am little scared about install this in my community and then flarum core go with other private system.
have the possibility in the admin panel a option to avoid the private message are listed in "all discussion" and only view when you go to private discussion tag?

luceos

Walys But some questions

have any date to go with stable version? Maybe some days, weeks, months....

No. @IanM and I want to make sure everything works as intended before tagging a stable version. We haven't entirely resolved all performance issues.

have any future idea to implement this extension to flarum core @luceos ? Or go with other system in the future for private message? I am little scared about install this in my community and then flarum core go with other private system.

It is extremely unlikely the flarum core team will build another private messaging extension. I think that outlook/promise needs to be changed.

have the possibility in the admin panel a option to avoid the private message are listed in "all discussion" and only view when you go to private discussion tag?

There is no private discussion tag. And whether we will split private discussions, read

IanM It is by design that private messages that the logged in user has access to are included in all discussions. The nature of byobu is that it's simply a normal discussion that is private.

stryguardian

I keep getting this when trying to install Byobu. I searched and found nothing that seems to help.

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - fof/byobu[0.1.0, ..., 0.1.2] require flarum/core ^0.1.0-beta.7 -> found flarum/core[v0.1.0-beta.7, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
    - fof/byobu[0.2.0, ..., 0.3.4] require flarum/core ^0.1.0-beta.8 -> found flarum/core[v0.1.0-beta.8, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
    - fof/byobu[0.4.0, ..., 0.5.0] require flarum/core ^0.1.0-beta.10 -> found flarum/core[v0.1.0-beta.10, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
    - fof/byobu[0.5.1, ..., 0.5.8] require flarum/core ^0.1.0-beta.13 -> found flarum/core[v0.1.0-beta.13, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
    - fof/byobu[0.6.0, ..., 0.6.1] require flarum/core ^0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.15, v0.1.0-beta.16] but it does not match your minimum-stability.
    - Root composer.json requires fof/byobu * -> satisfiable by fof/byobu[0.1.0, ..., 0.6.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

clarkwinkelmann

stryguardian see above, there's a different command to install the beta version we have for Flarum 1.0 luceos

The command in the first post of the discussion will not work. I don't really think we want to change it though because hopefully the non-beta version will be available soon.

GreXXL

Never noticed. But in a private discussion the list of participating users are linked to "true" (eg. https://discuss.flarum.org/d/true) which is of course an invalid URL not known to Flarum. Here is an example below.

Silverteal

GreXXL YESS!
It only happens above the post, but not on main page and sidebar

ornanovitch

Do you encounter any problem with byobu & websocket? With the Kyrne's one, I got a js bug each time I publish a new discussion (byobu or not). Quoting myself from ornanovitch on the Websockets thread:

[...] On the front side, it works perfectly for posts into discussions. But there is a problem regarding the discussion list. Whenever I publish a new discussion, the index empties and I have this message into the console (and the ones who are connected too):
TypeError: e.recipientUsers().find is not a function
    Pt Discussion.js:98
    e extend.js:35
    e extend.js:33
    controls DiscussionControls.js:28
    controls DiscussionControls.js:27
    view DiscussionListItem.js:68
    a render.js:30
    l render.js:155
    l render.js:160
    l render.js:66
 [...]
    exports render.js:964
    a mount-redraw.js:14
    c mount-redraw.js:25
mount-redraw.js:15:23
    a mount-redraw.js:15
    c mount-redraw.js:25
recipientUsers... it seems to be directly related to byobu, but I have no problem with byobu otherwise.

FYI desactivating byobu resolves this problem.

juzi

Does it adapt to 1.0.4?

GreXXL

juzi it is compatible - but in beta. You need to run:
composer require fof/byobu:"*@beta"

luceos

sibidharan you can read all about it in my post luceos

edit:

sibidharan seeing that you now have spammed several issues and pull requests on the repository I am going to state this here as well:

This extension is provided as open source. Nothing forbids you from forking the extension and reintroducing the features you miss. Understand that the maintenance and support of such a fork will fall onto you as well. We - the maintainers of this extension - decided against maintaining some features in order for it to survive in at least some form.

Harassing maintainers here and on GitHub I cannot appreciate. We invest so much time just to keep extensions available to the wider public. Blaming us will get you nowhere.

sibidharan

luceos I do not intend to blame or harass you! I just got panic seeing a major feature I was relying on was broken. I already forked and started the development process. Thanks for replying.

xasharma

Which version should I install for Flarum 1.0.4 ?

luceos

xasharma

composer require fof/byobu:"*@beta"

xasharma

luceos

Thank you

xasharma

luceos

I am having a problem ... Its working but

« Previous Page Next Page »