- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
🔗☑️ Accept all incoming shares #16828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| There is currently an inconsistence with remote shares to normal user shares and group shares. User shares trigger an individual email, federated shares had a notification to accept and group shares had nothing. Now since you need to accept all of them, they will all trigger a notification. Should be enough? Or will there be complains again from people how dont have the notifications app installed, or no client set up and therefor dont notice notifications. And then I think this is just working around the mail notification topic again, so in the end notifications should have an option to come via mail | 
| 
 We require notifications to be installed and activated. Makes no sense otherwise. 
 Yeah, fire out emails as much as possible. Not all people have NC or clients open all day (like us 😉 ) | 
4e8bf0b    to
    860617b      
    Compare
  
    78462ce    to
    c77bf7c      
    Compare
  
    | User and group shares are now ready for testing and the tech is ready for review. I think we should look at the other share providers in a follow up. Remarks
 | 
| } | ||
|  | ||
| if (!$this->canAccessShare($share)) { | ||
| throw new OCSNotFoundException($this->l->t('Wrong share ID, share doesn\'t exist')); | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adjust error message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied this behaviour from updateShare and I think it's okay to not leak the existence if the user can not interact with the share
| * @return IShare The share object | ||
| * @since 17.0.0 | ||
| */ | ||
| // public function acceptShare(IShare $share, string $recipient): IShare; | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
temporary until the other implementeations are adjusted then the interface will require it #TechnicalReviewOnly
| Please don't let this get forgotten. Thx. | 
| @nickvergessen What's the status on this? | 
| $manager->registerNotifierService(Notifier::class); | ||
|  | ||
| $dispatcher = $this->getContainer()->getServer()->getEventDispatcher(); | ||
| $dispatcher->addListener('OCP\Share::postShare', function(GenericEvent $event) { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah those crappy old events...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't seem to work for me. I share a folder to a user. The get the notifiation. But the folder already shows up directly...
9fdda51    to
    3dfd13f      
    Compare
  
    | 
 My last commit was missing here. Pushed it now while I rebased on top of 620 missing commits from master 😅 | 
| Hm. For me it also does not work, but with 
 | 
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
3dfd13f    to
    d3b6289      
    Compare
  
    | Rebased due to the heavy conflicts with roelands work of the share expiration notification. After that I retested it again and it worked fine here. But @tobiasKaminsky your URL looks like the configuration of the URLs is not dont correctly, because I don't juggle with URLs at all: 
 | 
| I tested it and now it works 🎉 Two things I noticed, which should then be handled in a new PR, if approved: 
 | 
| Yay works now indeed. | 
| @rullzer do you want me to report QA findings in separate issues just like @tobiasKaminsky earlier? | 
| Yes track sepratly please | 
Uh oh!
There was an error while loading. Please reload this page.