CipherParcel is now in the WordPress plugin directory. It gives me a way to send someone a file from WordPress with a password and an expiry date, and to revoke the link when they no longer need it.
I had the plugin ready for submission under the name DanceVault when a fresh search turned up several unrelated products using that name. Changing the name people see was straightforward. The question was what would happen to files people had already stored.
What changed when DanceVault became CipherParcel
I changed the public name, package directory, text domain and release filenames. The existing dancevault database keys, routes, PHP classes, encrypted file format and storage directory stayed in place. A regression check now guards that compatibility boundary so a future tidy-up doesn’t accidentally turn the rename into a data migration. See the rename and compatibility checks on GitHub.
What a protected download looks like
I create a parcel with a password and an expiry date, then give the recipient the link and share the password separately. They enter the password on the download page. I can revoke the link from the same screen where I created it.
The ZIP people can actually download
Version 1.0.3 was the package WordPress.org approved. There was already a newer GitHub release by the time I published it, so the publisher retrieved the approved ZIP and checked its contents against the original source tag. After publishing, I downloaded the WordPress.org ZIP and compared the files inside. WordPress.org repackaged the archive, and all 14 files inside matched the tested GitHub package byte for byte.
View CipherParcel on WordPress.org · Download the verified 1.0.3 ZIP · See the tested GitHub release
The bit I like about the rename is how little it asked of the files that were already there. They can still be opened using the same records and format, even though the plugin has a new name.


Leave a Reply