FriendsOfFlarum Byōbu, well integrated, advanced private discussions

0.6.0-beta.3

Fixed

• New private discussions required approval
• 'Alert' notifications were not triggered
• Prevent private discussion started notifications from being delivered to the discussion author
• Flagged private discussions appeared in 'All discussions'

Added

• Admins can now customize the icon used for Byobu discussion badges and post events FriendsOfFlarum/byobu135
• Fully translatable email notification templates
• Flarum beta 15 support

Changed

• Support for Flarum beta 14 dropped, minimum requirement is now beta 15

IanM Any chance you can update these changes for beta 13 supported version?
I'm facing 'Alert' notifications were not triggered issue for ages, been waiting for help here

luceos I have updated Flarum to b15 and installed Byobu 0.6.0. Still have the same "Oops" error when sending the messages. When I reload a page manually I see that the messages are there but the error doesn't allow the page to refresh normally.

Here's my flarum info (nothing fancy's there):

Flarum core 0.1.0-beta.15
PHP version: 7.2.18
Loaded extensions: Core, bcmath, calendar, ctype, date, filter, hash, iconv, json, SPL, pcre, readline, Reflection, session, standard, mysqlnd, tokenizer, zip, zlib, libxml, dom, PDO, bz2, SimpleXML, xml, wddx, xmlreader, xmlwriter, openssl, curl, fileinfo, gd, gettext, gmp, intl, imap, ldap, mbstring, exif, mysqli, Phar, pdo_mysql, pdo_sqlite, soap, sockets, xmlrpc, xsl
+----------------------+----------------+--------+
| Flarum Extensions | | |
+----------------------+----------------+--------+
| ID | Version | Commit |
+----------------------+----------------+--------+
| flarum-approval | v0.1.0-beta.15 | |
| flarum-bbcode | v0.1.0-beta.15 | |
| flarum-emoji | v0.1.0-beta.15 | |
| flarum-lang-english | v0.1.0-beta.15 | |
| flarum-flags | v0.1.0-beta.15 | |
| flarum-lock | v0.1.0-beta.15 | |
| flarum-markdown | v0.1.0-beta.15 | |
| flarum-mentions | v0.1.0-beta.15 | |
| flarum-statistics | v0.1.0-beta.15 | |
| flarum-sticky | v0.1.0-beta.15 | |
| flarum-subscriptions | v0.1.0-beta.15 | |
| flarum-suspend | v0.1.0-beta.15 | |
| flarum-tags | v0.1.0-beta.15 | |
| flarum-likes | v0.1.0-beta.15 | |
| fof-byobu | 0.6.0 | |
+----------------------+----------------+--------+

And these are errors from debug:

Fatal error: Uncaught InvalidArgumentException: Unable to encode data to JSON in Laminas\Diactoros\Response\JsonResponse: Malformed UTF-8 characters, possibly incorrectly encoded in \www\flarum\vendor\laminas\laminas-diactoros\src\Response\JsonResponse.php on line 165

InvalidArgumentException: Unable to encode data to JSON in Laminas\Diactoros\Response\JsonResponse: Malformed UTF-8 characters, possibly incorrectly encoded in \www\flarum\vendor\laminas\laminas-diactoros\src\Response\JsonResponse.php on line 165

Does this extension work correctly in beta 15 ? I am able to reproduce the same issue in beta 15 as I could in 14. I don't have access to my PC presently, but it's easily replicated (for me anyway) in the sense that if I click on private messages, open a new message, close it, then click any tag, I can't open a new discussion window.

There's definitely a console error which I'll post as soon as I can, but I wondered if anyone else has noticed this ?

It looks like there is a new notification bug : when I receive a message, a notification number appears, it's ok. But when I try to open the notifications panel, it stays in loading state and it doesn't display any notification anymore until I read the private message. Is it only in my website or anyone has the same behaviour ?

Edit : I noticed this javascript error when opening panel

TypeError: this.props is undefined
href DiscussionCreatedNotification.js:10
view Notification.js:21
a render.js:30
l render.js:155
l render.js:160
l render.js:66
u render.js:50
l render.js:134
l render.js:63
u render.js:50
l render.js:134
l render.js:63
u render.js:50
l render.js:134
l render.js:63
u render.js:50
l render.js:103
l render.js:62
u render.js:50
l render.js:103
l render.js:62
f render.js:423
h render.js:302
f render.js:477
f render.js:416
h render.js:302
f render.js:477
f render.js:416
f render.js:488
f render.js:419
h render.js:302
f render.js:477
f render.js:416
h render.js:302
f render.js:477
f render.js:416
f render.js:488
f render.js:419
h render.js:302
f render.js:477
f render.js:416
h render.js:315
f render.js:477
f render.js:416
f render.js:488
f render.js:419
h render.js:302
exports render.js:964
a mount-redraw.js:14
c mount-redraw.js:25
c mount-redraw.js:23
loadMore NotificationListState.js:63
promise callback*flarum.core</Ee</e.loadMore NotificationListState.js:61
load NotificationListState.js:43
onclick NotificationsDropdown.js:50
handleEvent render.js:888
I render.js:910
k render.js:735
l render.js:730
l render.js:122
l render.js:63
u render.js:50
l render.js:134
l render.js:63
l render.js:162
l render.js:66
u render.js:50
l render.js:134
l render.js:63
u render.js:50
l render.js:134
l render.js:63
l render.js:162
l render.js:66
u render.js:50
h render.js:277
exports render.js:964
mount mount-redraw.js:45
mount ForumApplication.js:123
boot Application.js:176
<anonymous> (index):219
mount-redraw.js:15:23

luceos

[deleted]

Just looking now, actualy. The polls issue, I believe would be temporarily resolved by removing pusher.. Still checking byobu

Edit: @[deleted] for the error related to polls - please try composer require fof/polls:dev-master. I'm not able to test as I don't have pusher setup locally, but I think the issue should be resolved.

The composer related issue however, will require some more investigation