luceos Pollux if you are able to report them on github it's easier for us to follow up. We'll look into this soon.
Eldenroot @luceos - hi, any progress with more "realtime" chatting in this great extension? I saw some commits in your GitHub, any ETA for beta testing? Thank you!
luceos Eldenroot I have been silently deliberating to separate such a chat into another extension. There is no sane reason to combine the code into one extension and I think real time chat would be pretty distinctive from private discussions.. The basic integration of a button and modal works, but I think if I make real time chat an extension by itself it will also look differently than my proof of concept under Byobu. Keep you posted.
Pollux I found a serious bug exposing supposedly private discussions to the public, when initiated via the user profile link. I also reported it on Github: flagrow/byobu37
luceos Pollux no worries I follow all Flagrow extension threads. I'll take a look asap and do some catching up on reported items tomorrow.
luceos Tagged 0.1.0-beta.19: German translation added by Kakifrucht Permission can now be configured per tag: check your permissions after updating Fixed issue where only admins could set recipients. Fixed issue where opening a private discussion from a user profile didn't make a discussion private ?. Some improvements to less files and listeners. Update using: composer update flagrow/byobu --prefer-dist --no-dev -o php flarum cache:clear Or use flagrow/bazaar ? I suggest updating IMMEDIATELY!
ajvdeutekom Thank you for the update luceos We run into a small problem after updating, public discussions cannot be started anymore. A discussion can only be started when recipients are selected.. I reported the bug on Github flagrow/byobu40
Pollux @luceos Wonderful, I updated already. Unfortunately the second change (permission can now be configured per tag) doesn't work as intended. I also reported it on Github: flagrow/byobu39
luceos ajvdeutekom and others Tagged 0.1.0-beta.20 Fixes flagrow/byobu40 where discusion creation was no longer possible. Update using composer update flagrow/byobu --prefer-dist --no-dev -o php flarum cache:clear Or use bazaar. Please update immediately. ajvdeutekom thank you so much for reporting this issue. Can't understand why you're the only one ?
Pollux luceos Can't understand why you're the only one ? In my case, our forum is not public yet and our talks right now were in fact only in existing discussions. Thanks once more for your prompt reaction.
sledov I am getting POST http://flarum.loc/api/discussions { "errors": [ { "status": "404", "code": "resource_not_found" } ] } when I specify a recipient. And discussion is created normally if I don't specify a recipient.
Veriael Yeah, I'm getting the same as 2 users above. You can even make private discussion with yourself, but anyone else provides us this error. sledov JRay Well, guys... We are stupid. xD You simply need to add yourself to discussion as well as the others... xD
luceos Veriael right, previously you were added per default. That might have been lost, I will look into this.
JRay luceos right, previously you were added per default Yeah I would expect to be added automatically if I'm the creator. Or at least a more descriptive error message.
YaarBaturalpArtar @luceos what is wrong with my extension? How can I fix this? http://i.imgur.com/hH1kqeY.png
clarkwinkelmann YaarBaturalpArtar you need to clear the cache to reload the translations I guess. Also check Cloudflare cache if you use it.
bikepost YaarBaturalpArtar I get this when I install extensions. Eventually, your (shared?) server will refresh and everything will look normal. It seems to take 1-2 days for me. Cleaning up the browser cache doesn't help in my case. This is something on the server even after I clear cache there too with php flarum migrate php flarum cache:clear
