YusufYldrm
This extension is marked with abandoned tags, so this is not compatible with beta 8.1 flarum, as you can see here. So before installing an extension, make sure it is not marked abandoned
FriendsOfFlarum User Directory
Ok, so is there any alternative for beta 8?
petr_kazda They are going to update this extension. I see that there is a pull request for it. I am sure they are busy and will get to it when they get a chance. I am looking forward to this working as well.
I look forward to updating this extension.
The day has finally come, User Directory is now compatible with beta 8.
A merge of the extension with Users List is still planned, but in the meantime Glowing Blue sponsored the migration of the User Directory part to beta 8
Run composer require flagrow/user-directory
on your beta 8 forum to get the version 0.2.0
of the extension.
clarkwinkelmann Expected add-on. Nice job. Congratulations...
I translate this plugin into my language, but it doesn't work. I'm uploading the file tr.yml to vendor / flagrow / user-directory / resources / locale. Or should I upload my own language to my directory? I am having such a problem with other flagroW extensions. What should I do?
wwwn while not a safe method (all files in vendor might be removed/overriden on composer actions) it should work. Make sure your file name matches the extension language ID (it might be tr-COUNTRYCODE
). Also make sure you're running in debug mode on your local setup or clear the cache if you're doing that on a production forum.
Ralkage as a matter of fact, we already have a Turkish PR waiting, but we'd need some peer review before merging it https://github.com/flagrow/user-directory/pull/19
Approving PRs for languages we don't understand is still a problematic question I don't know how we should solve. Probably a topic for another discussion...
clarkwinkelmann https://github.com/flagrow/user-directory/pull/19
The translations in Turkish are correct.
- Edited
Why is there a permanent "Loading" icon on the plugin page?
Artuu this is just a PHP warning. You should change your PHP configuration to not output warnings (look at the error_reporting
configuration)
The second issue (EmitterException) is because the warning was printed to the page, the remaining of the response can't be sent.
Ok, I added to index.php
this line:
error_reporting(0);
and now is working. Thanks clarkwinkelmann!
Artuu that's one way, ideally you should change this in the php config if you can.
Also I'm really not familiar with that php setting but I believe what you did also suppressed the errors, not only the warnings. There's a way to just disable warnings by passing some constants instead of 0
but I won't copy anything here as I'm never sure how it works
clarkwinkelmann To be honest, I do not know either. It's important that it works. I do not have access to the php configuration by the fact that it is web hosting.
clarkwinkelmann this is just a PHP warning. You should change your PHP configuration to not output warnings (look at the error_reporting configuration)
Suppressing all warnings is not a solution, this is really bad advice...
rob006 yes it might not be clear but I was talking about hiding them from page output here, which is an industry standard for web application. No visitor needs to see them anyway.
It doesn't mean we shouldn't log them or investigate the underlying issue. If somebody has the time to find out what exactly causes it, an issue or PR is welcome