How to submit bug report with sensitive data: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
Line 19: Line 19:
* Scribus version >=1.4.x (?)
* Scribus version >=1.4.x (?)
* Greg Pittman's [[Scrambling Text]] Scribus python script – there are 3 versions:
* Greg Pittman's [[Scrambling Text]] Scribus python script – there are 3 versions:
** replacetext.py will scramble the text of a selected individual frame
** '''replacetext.py''' will scramble the text of a selected individual frame
** replacetext_v3.py will scramble all text frames in a document
** '''replacetext_v3.py''' will scramble all text frames in a document
** replacetext_v2.py will scramble all text frames on the current page
** '''replacetext_v2.py''' will scramble all text frames on the current page


====Important Note====
====Important Note====

Revision as of 01:05, 11 June 2014

 Hourglass1.png This feature/option is considered experimental

Encountering a critical bug in a confidential project

This may be subject to occuring. In this case there is an option that the Scribus community has set up a few options:

Option #1 Submit the bug report as Private status in the Mantis Bugtracker

Only the core devs will see the issue.

Figure 1: Scribus MantisBT Bug Report form attachment function

Option #2 Use Scrambling Script

A Python script called Scrambing Text (written by Greg Pittman) can be run on the Scribus .sla file and obfuscate any text (not the pictures...Yet).

Screenshots

  • ToDo: Add side-by-side before/after screenshot

Requirements

  • Scribus version >=1.4.x (?)
  • Greg Pittman's Scrambling Text Scribus python script – there are 3 versions:
    • replacetext.py will scramble the text of a selected individual frame
    • replacetext_v3.py will scramble all text frames in a document
    • replacetext_v2.py will scramble all text frames on the current page

Important Note

  • Backup the .sla file before executing script
  • The script may wipe out the bug so you will need to confirm the bug is still there after the contents of the .sla have been 'scrambled'.

Related