You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm adding quota feature to elFinder: when an user goes "over-quota", some actions will be disabled until he/she gets back under the quota limit.
To disable actions, connector tests quota status and returns a different array to 'disabled' parameter based on user over/under quota status. Connector binds a callback to "sensitive" actions like paste, rm, duplicate which updates quota and returns TRUE to let elFinder update itself.
The expected effect is actions disabled immediately after the action that caused the over-quota (and restore them after, say, deleting some files), but actually only toolbar actions are updated (i.e. Paste disappears) but not the context menu.
To demonstrate this "misbehavior" I've setup a sample repository here.
It features a simpler quota algorithm (to keep things simple): quota is not "folder size" but "files count" related: you're allowed to store up to 3 files in the volume, when you add the 4th you'll switch to readonly access.
Since a video is better then a thousand words, take a look to sample video in the same repo.
The text was updated successfully, but these errors were encountered:
I'm adding quota feature to elFinder: when an user goes "over-quota", some actions will be disabled until he/she gets back under the quota limit.
To disable actions, connector tests quota status and returns a different array to 'disabled' parameter based on user over/under quota status. Connector binds a callback to "sensitive" actions like paste, rm, duplicate which updates quota and returns TRUE to let elFinder update itself.
The expected effect is actions disabled immediately after the action that caused the over-quota (and restore them after, say, deleting some files), but actually only toolbar actions are updated (i.e. Paste disappears) but not the context menu.
To demonstrate this "misbehavior" I've setup a sample repository here.
It features a simpler quota algorithm (to keep things simple): quota is not "folder size" but "files count" related: you're allowed to store up to 3 files in the volume, when you add the 4th you'll switch to readonly access.
Since a video is better then a thousand words, take a look to sample video in the same repo.
The text was updated successfully, but these errors were encountered: