Mikesoft
Forum Replies Created
-
Forum: Reviews
In reply to: [Mikesoft TeamVault] A useful file vault with some permission gapsHi,
Thank you for taking the time to test Mikesoft TeamVault and cover it in your Plugin Check video, I really appreciate it.
I’ve watched the video and I’m glad the core functionality came across well. Your feedback on the three points, the confusing error message for oversized files, the lack of per-folder permissions, and the absence of a read/write distinction, is noted and I’ll take it into account when planning future updates.
Just to give a bit of context on the original intent: TeamVault was designed as a shared private workspace for the members of a single team or organization, a place to exchange and organize internal documents without those files ever touching the public Media Library. With that use case in mind, a flat permission model felt sufficient.
That said, your point about per-folder rights opens up an interesting direction: a large-scale WordPress project, such as a multi-team ecommerce, where, for example, the marketing team manages their own materials, the sales team theirs, and the admin maintains a separate space, each isolated from the others. That’s a scenario I hadn’t fully considered when designing the plugin, but it’s worth evaluating for a future release.
Thanks again for the thoughtful review and for sharing it with your audience.
Best regards,
MichaelForum: Plugins
In reply to: [Mikesoft TeamVault] 404 error when loading folders and filesHi Daniel,
thank you very much for the detailed report and for taking the time to investigate the issue.
You were absolutely right: the problem happened on sites using plain permalinks, where WordPress builds REST API URLs with the
rest_routequery parameter. TeamVault was appending endpoint query parameters incorrectly in that case, which caused the browser endpoint to return a 404.This has been fixed in version 2.0.2, which is now available on WordPress.org.
I also improved the upload error message when PHP rejects a file because it is too large before TeamVault can validate it.
I tested the fix on a local WordPress install with plain permalinks and confirmed that the folders/files endpoint now loads correctly.
Thanks again for the helpful report.
Best,
Michael