From john.thurston at alaska.gov Tue Apr 1 19:22:22 2025 From: john.thurston at alaska.gov (John Thurston) Date: Tue, 1 Apr 2025 10:22:22 -0800 Subject: [ZendTo] Making an instance read-only References: <713ae86e-4110-4f4e-84af-92c12edddb86@alaska.gov> Message-ID: Is there a simple way to render an instance of ZendTo 'read only' from the user-perspective? That is, to allow the use of existing links to download files, but to prevent anyone from creating new 'drops' ? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska -------------- next part -------------- An HTML attachment was scrubbed... URL: From klou at themusiclink.net Tue Apr 1 20:39:43 2025 From: klou at themusiclink.net (Kris Lou) Date: Tue, 1 Apr 2025 12:39:43 -0700 Subject: [ZendTo] Making an instance read-only In-Reply-To: References: <713ae86e-4110-4f4e-84af-92c12edddb86@alaska.gov> Message-ID: On Tue, Apr 1, 2025 at 11:22?AM John Thurston via ZendTo wrote: > Is there a simple way to render an instance of ZendTo 'read only' from the > user-perspective? > > That is, to allow the use of existing links to download files, but to > prevent anyone from creating new 'drops' ? > > > Maybe block ./req.php and ./verify.php ? I suppose it would be nicer to redirect those requests to an error page explaining that it's read only. And should probably inflate "numberOfDaysToRetain" as necessary. Kris Lou klou at themusiclink.neto -------------- next part -------------- An HTML attachment was scrubbed... URL: