We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apostrophecms-legacy/apostrophe-redirects#10 (comment)
Quoth Tom:
There is now a practical path to fix this: npm update 'apostrophe-attachments': { uploadfs: { disabledFileKey: 'very-random-string-please-not-this' } } Deploy as usual. (Please note: I put these steps in this order for reasons) On the server, run this task to complete the transition: node app apostrophe-attachments:migrate-to-disabled-file-key Now files in the trash have their names changed rather than their permissions changed. Recommend verifying an example. BENEFITS You can now sync down without permissions nonsense! Woo You can now create a redirect for the old URL of the file, because the file ain't there no more.
There is now a practical path to fix this:
npm update
'apostrophe-attachments': { uploadfs: { disabledFileKey: 'very-random-string-please-not-this' } }
Deploy as usual. (Please note: I put these steps in this order for reasons)
On the server, run this task to complete the transition:
node app apostrophe-attachments:migrate-to-disabled-file-key
Now files in the trash have their names changed rather than their permissions changed. Recommend verifying an example.
BENEFITS
The text was updated successfully, but these errors were encountered:
abea
No branches or pull requests
apostrophecms-legacy/apostrophe-redirects#10 (comment)
Quoth Tom:
The text was updated successfully, but these errors were encountered: