FriendsOfFlarum Byōbu, well integrated, advanced private discussions

clarkwinkelmann

DCar no, other FriendsOfFlarum extensions could also be the cause.

I say that because most extensions, including FoF extensions, are usually tested together with Flarum core extensions during development. But it's a lot more difficult to test all FoF extensions together with realistic production configurations and data so this is rarely done.

Permissions issues are complicated to troubleshoot because the message doesn't say which part of the code or which extension triggered the denial. Even when we know which particular gate ability was designed, there could still be multiple extensions extending the logic for the same ability. Usually the problem is either a different extension denying something unrelated (hypothetical example, an extension requiring the discussion to have a poll, while at the same time private discussions not supporting it) or 2 extensions having priority issues over the same ability (example: tags extension could say something is permitted in a tag, while the extension itself says it's not)

Sometimes the only way to find out for sure is to replicate on a development setup. But for that we need to know which extensions and which settings will allow reproducing the issue, ideally limited to as few extensions as required for the problem to still occur.

DCar

clarkwinkelmann

I understand, the process of elimination. I disabled all non-FOF extensions and the issue continues. The next step would be to disable all extensions to determine if the issue continues.

This is an evaluation forum to determine whether Flarum will meet the requirements of the organization ~ it also has some 'features' which are not available in the alternative forum.

Deanna

DCar

clarkwinkelmann I disabled all extensions, with the exception of Byobu, the condition continues to exist.

Next steps in resolving this issues would be?

Deanna

DCar

clarkwinkelmann I have determined the cause of this issue, the Permission (Global) to "Start Discussions" when turned on for the users will permit the creation of private discussions. However, for this particular organization's 'use case' / requirements, users may only create discussions within specific 'tags' (accomplished via "restrict by tag").

I will 'chat' with the organization to determine whether private discussions / messages between users are an actual requirement or just a 'nice to have'.

Deanna

GreXXL

DCar do users have the permission to search users? Maybe you can share a screenshot of your permission setup. Also you should query FreeFlarum if the extension has been updated to the latest version that also fixed a permission error.

DCar

GreXXL the users have permission to search users. I will query FreeFlarum to determine if the latest version of the extension has been applied.

Thank you

luceos

DCar oh, so if the global "start discussions" permissions is disabled, then you cannot create private discussions either? Seems like a bug if the permission to make private discussions is actually allowing that.

DCar

luceos That is correct. If I enable the Permission (Global) to "Start Discussions" then they are able to create private discussions. If the Permission (Global) to "Start Discussions" is disabled, the users are unable to create private discussions.

I would call it a bug ... it appears the Global Permissions to Start Discussions takes precedence over the permission to create private discussions. On the other hand, that may be 'as designed'.

Deanna

DCar

luceos Just following up to inquire about 'how to' determine if the encountered behaviour is by design or a 'bug'. If a 'bug' how would one go about reporting the 'bug'?

Trc4

Is there some way that admins and moderators can't be blocked from private messages by user?

chenwynn

Has anyone encountered a similar problem?
Successfully installed the extension, but once activated, the following error appears on the front-end page.

mount-redraw.js:15 TypeError: Cannot read properties of undefined (reading 'type') at e.pushObject (Store.ts:125:27) at e.pushPayload (Store.ts:103:110) at e.preloadedApiDocument (Application.tsx:363:22) at n.oninit (TagsPage.js:23:27) at Function.a (render.js:30:16) at M (render.js:917:53) at render.js:153:3 at render.js:160:3 at c (render.js:66:8) at l (render.js:50:5)

"use strict"

var Vnode = require("../render/vnode")

module.exports = function(render, schedule, console) {
var subscriptions = []
var rendering = false
var pending = false

function sync() {
	if (rendering) throw new Error("Nested m.redraw.sync() call")
	rendering = true
	for (var i = 0; i < subscriptions.length; i += 2) {
		try { render(subscriptions[i], Vnode(subscriptions[i + 1]), redraw) }
		catch (e) { ~~console.error(e)~~ }
	}
	rendering = false
}

Flarum core: 1.8.1
PHP version: 7.4.33
MySQL version: 5.7.40-log
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, ctype, curl, dom, filter, ftp, gd, gettext, hash, iconv, intl, json, mbstring, SPL, session, pcntl, standard, PDO, mysqlnd, pdo_sqlite, Phar, posix, Reflection, pdo_mysql, shmop, SimpleXML, soap, sockets, sodium, mysqli, sysvsem, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, zip, fileinfo
+---------------------------------+---------+--------+
| Flarum Extensions | | |
+---------------------------------+---------+--------+
| ID | Version | Commit |
+---------------------------------+---------+--------+
| flarum-flags | v1.8.0 | |
| flarum-approval | v1.8.0 | |
| flarum-tags | v1.8.0 | |
| flarum-suspend | v1.8.0 | |
| fof-nightmode | 1.5.2 | |
| fof-byobu | 1.3.1 | |
| flarum-subscriptions | v1.8.0 | |
| flarum-sticky | v1.8.0 | |
| flarum-statistics | v1.8.0 | |
| flarum-mentions | v1.8.2 | |
| flarum-markdown | v1.8.0 | |
| flarum-lock | v1.8.0 | |
| flarum-likes | v1.8.0 | |
| flarum-lang-english | v1.8.0 | |
| flarum-lang-chinese-traditional | v1.14.0 | |
| flarum-lang-chinese-simplified | v1.3.0 | |
| flarum-emoji | v1.8.0 | |
| flarum-bbcode | v1.8.0 | |
+---------------------------------+---------+--------+

clarkwinkelmann

DCar I haven't read the full conversation above but if you can describe steps from a fresh Flarum install that lead to the issue it would be the most helpful report!

Looking at the report about the global permission I think it should be pretty easy to test if that's a general issue even without detailed steps. I haven't personally had time to investigate though.

DCar

The original issue manifested on Flarum forum installed on FreeFlarum (used to evaluate product for organization's requirements). We have subsequently installed Flarum on the organization's hosting site.

In the FreeFlarum installation, disabled extensions (all) in order to test. In this particular organization's use case / requirements, users may only create discussions within specific 'tag' (accomplished via 'restrict by tag') and are unable to Globally 'Start Discussions'. When configured in this manner, the users are unable to Start Private Discussions despite the permissions being set to allow for Create private discussions with users and Add more than 2 user recipients to private discussion. As a step in trouble-shooting I enabled the Global Permission to Start discussions for those users and they were then able to Start Private Discussions.

In the newly installed Flarum forum, on the organization's hosting site, this exact same behaviour is observed. Same conditions, when users are configured to only Start Discussions is specific tags they are unable to Start Private Discussions (even if Create private discussions with users and Add more than 2 user recipients to private discussion. is enabled for them). If I enable the users with the Start Discussions (Global) they are able to Create Private Discussions

Unfortunately, the organization's requirements are such that users may only Start Discussions within specific tags.

Deanna

luceos

v.1.3.2

Fixes:

nullsafe operator throws errors on environments with php 7, this fixes an issue introduced in 1.3.1 for sites running php 7

Communities running Byobu on PHP 7 need to update their PHP to at least 8.0, but 8.1 is recommended. As the last PHP 7 release (7.4) is end of life, now would be a good time to upgrade anyway: https://www.php.net/supported-versions.php

Arnold

luceos tell please, is there a way to downgrade the plugin to latest version compatible with php 7.4 which will work on Flarum 1.8.1? As a temporary solution before php upgrade. It was updatetd to 1.3.1 and now doesn't work with my hosting configuration

GreXXL

JRay PHP version: 7.3.33-10+ubuntu20.04.1+deb.sury.org+1

Did you see the above announcement? Would it be possible to update your hosting environment to a PHP version that is still being maintained and fulfilling the mentioned requirements?

luceos Communities running Byobu on PHP 7 need to update their PHP to at least 8.0, but 8.1 is recommended. As the last PHP 7 release (7.4) is end of life, now would be a good time to upgrade anyway: https://www.php.net/supported-versions.php

luceos

Arnold

composer require for/byobu:"1.2.*"
php flarum cache:clear

I am not entirely sure this will work though, so make a backup!

Arnold

luceos thanks, it worked! 🤝

marionline

Sorry but I didn't find a solution. Is it possible for an Administrator (or a Moderator) to view the private discussion of normal users?

hrvoje_hr

marionline admin/mod can see private discussions only when they are reported

marionline

hrvoje_hr Ok, so... no "big brother" function. Thanks

« Previous Page Next Page »