Warn that imported data is public #538
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
plugins/csv-import/src/App.tsx
Outdated
| CMS data is publicly viewable. | ||
| <br /> | ||
| Avoid importing personal data. | ||
| </p> |
There was a problem hiding this comment.
Warning hidden during drag-and-drop file import
High Severity
The public data warning is placed inside the {!isDragging && ...} conditional block, causing it to disappear when users drag files over the interface. Users who import CSV files via drag-and-drop won't see the warning about CMS data being publicly viewable, defeating the PR's core purpose of preventing accidental PII imports.
plugins/csv-import/src/App.tsx
Outdated
| CMS data is publicly viewable. | ||
| <br /> | ||
| Avoid importing personal data. | ||
| </p> |
There was a problem hiding this comment.
Paste import bypasses public data warning
High Severity
The public data warning only appears in the UI but doesn't cover the paste-to-import functionality. Users can paste CSV data directly into the plugin (handled by the clipboard event listener starting at line 139), which calls processAndImport() and imports data without ever displaying the warning about CMS data being publicly viewable.
jeysal
force-pushed
the
personal-data-warning
branch
from
06d83d6 to
b5ce8e0
Compare
|
After rebase, Open Development Plugin doesn't load for me anymore, so not sure I did the rebase correctly |
Description
People CSV-imported personally identifiable information into the CMS and were surprised it was visible to the internet.
Wdyt about warning about this here, and then potentially also for other import avenues?
We were also thinking about warning about this in the app UI because people might also enter such data manually, but aren't sure yet if we have a good place. Via import people are probably most likely to carelessly do this without thinking about it.
Testing