As soon as I hear confirmation that this release works, I will do a full "production" release. So the more of you test it for me, the faster you can get those pesky bugs fixed on your production systems. The "autorequest" automation script should now work correctly again, and offer all the available options it can.
Also I have extended the length of database fields that contained organization names to characters, instead of As usual, your DB schema should automatically update itself on installation. The main improvements are to the "request a drop-off" page, which I have overhauled. You can now specify an opening and closing time and date for the resulting drop-off. So if people try to submit too late or too early, they can't.
Also a bunch of minor improvements and bug-fixes. The Change Log will tell you more. A few logging improvements and logging bug fixes that have been requested, and more detailed logging about users creating new drop-offs.
The Change Log should tell you more. All known bugs fixed, including one that could cause users to be reminded about the wrong near-expiry drop-offs. Also updated translations. See the Change Log for details. Fixed reported bugs in the chunk upload error handling code. New Turkish translation, some bug-fixes and speed optimisation to template library.
This fixes a bug where totally incorrect expiry times were shown in reminder emails. Thanks to Susoczki Attila for reporting this. Download instructions are on the beta page. Exporting as CSV will now only export the visible columns, and you can make all the columns visible with 1 click. This is very close to a production release, so please check the pages look okay on all browsers! More info on the beta page and in the Change Log. Also all of those pages now have a means to toggle the visibility of each column.
The main addition is that users can now edit the "Subject" line used when telling recipients about the new drop-off. More details are on the beta page and in the Change Log. If, for any reason, the passphrase cannot be read when creating a new drop-off in response to a request, the new drop-off is now rejected immediately. This allows you to change which columns are visible in the global list of all drop-offs.
Also "autolist" has been improved to be able to handle much larger numbers of drop-offs. This is a bug-fix release, no new features. See the SAML documentation for instructions on how to use this. The big features in this release are: Login via OAuth, Yubikeys etc with SAML-based authentication Uploaded files are sent in small chunks with auto-retries Users can reduce the lifetime of a drop-off Recipients can be made to read a legal waiver before downloading files plus many other new features and fixes which are listed in the Change Log.
See the automation page for more info on automating ZendTo and driving it from your own application code. See the beta page for instructions on how to download and install it. See the beta page for more information. The preferences. Admin logins are now restricted to your local IP subnets by default, for improved security. This can be used to automatically split the drop-off process into many pieces, to work around size limits imposed by network security appliances and services e.
It's not as complicated as it looks, just work through it carefully. This should allow you to use all sorts of different additional authentication mechanisms such as Microsoft Azure, OAuth, Shibboleth, Yubikeys, and even Twitter and Facebook.
See the beta page for how to get started. If you have this problem, download the Installer again and just tell it to do the ClamAV stage.
Fixed a problem which would make requesting a drop-off fail. New Hungarian, Polish and Russian translations. New optional "terms and conditions waiver" feature, internaldomains. See the Change Log for all the details. New preferences. See the setting in preferences. So no hurry!
Please see the newly updated documentation for simple instructions on configuring ZendTo and your ZendTo server's OS to enable this. New Polish and Russian translations, some security fixes and new config options as requested by various users. Please see the Change Log. For installation, please read the Beta page. I have also fixed a bunch of other problems, please see the Change Log.
A few important bug-fixes, plus more intelligence when adding recipients so that you can just enter email addresses in "Name" boxes and not worry about it. Also improved the Installer so it configures zendto. The main new features are 1 a "Download all files as a zip" button on the download pages, which is useful if are picking up a drop-off containing lots of files, you're using Firefox and are sick of saying "yes, just save it, don't open it!
The person sending the files to you cannot find out the passphrase, nor disable the encryption. Below is a list of possible problems. If you are sure that all of these reasons do not exist in your case or have already been eliminated , the ZPK file should operate with your programs without any problem.
If the problem with the ZPK file has not been solved, it may be due to the fact that in this case there is also another rare problem with the ZPK file. In this case, the only you can do is to ask for assistance of a professional staff. If you want to associate a file with a new program e. ZPK you have two ways to do it.
The first and the easiest one is to right-click on the selected ZPK file. From the drop-down menu select "Choose default program" , then click "Browse" and find the desired program. The whole operation must be confirmed by clicking OK. The second and more difficult to do is associate the ZPK file extension to the corresponding software in the Windows Registry.
Many files contain only simple text data. If you want additional files and folders to be added to the project, click Add Folder or Add File and browse to the required source.
A symbolic link often shortened to symlink and also known as a soft link consists of a special type of file that serves as a reference to another file or directory. Unix-like operating systems in particular often feature symbolic links. Which files to encode - Lists the file extensions for Guard to encode extensions not listed will not be encoded. File extensions that are not listed here and in "Patterns to Ignore" will be sent as-is to the output folder.
Which patterns to ignore - Files matching these patterns will not be encoded when encoding a directory, nor will they be copied as-is to the target directory. Your project will be opened in Zend Guard and can be encoded using Zend Guard's functionality. Installation Tutorials Concepts Tasks Reference.
0コメント