Add clone/move/remove project commands #5940
Commits on Mar 17, 2017
-
-
-
-
- clear existing scores before checking dummy scores - use datetime for dummy events
-
-
-
-
-
-
-
-
-
Commits on Mar 18, 2017
-
-
-
-
for suggestion, submission and unit_create, and to trigger tp.update when storescores are changed
-
-
-
Adjust update_data_after to allow multiple signals
and include update_scores in default suppression
-
Removed setting of the script prefix
Removed setting of the script prefix
-
-
-
-
-
-
-
Use py.test testpaths config variable
This allows to again run selected tests by specifying paths on the command line.
Commits on Mar 19, 2017
-
Rename Log.filter_user to Log.filter_users
and allow filtering on multiple users
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Commits on Mar 20, 2017
-
-
This info is still recorded in the store's creation timestamp
-
-
Opti: dont select_related for updater units
wierdly this was causing an additional query
-
-
-
-
-
-
-
-
Commits on Mar 21, 2017
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Pass updater.user as arg to unit.save
and dont set change attribution for comments in updater
-
-
-
-
use unit.change.commented create subs after unit.save
-
use unit.change for reverting comments use update to prevent triggering new submissions
-
-
-
-
-
-
use unit.change.reviewed create subs after unit.save
-
-
-
-
-
-
-
state changes that are not also target changes are regarded as a review, depending on the resulting state. if reviewed_by is explicitly set, this also updates reviewed info
-
-
-
-
-
-
Checks sub creation times against unit.mtime Dont expect review is suggestion.user == reviewer
Commits on Mar 22, 2017
-
-
- always use unit.mtime (or creation_time) for change and subs - only allow user and/or reviewer to be passed to unit.save - responsibility is now only (hopefully) with unit.save for setting attribution -
-
-
Checks sub creation times against unit.mtime Dont expect reviewed if suggestion.user == reviewer
Commits on Mar 23, 2017
-
-
-
-
Fix: use pootle.core.batch in migration
the existing migration was not correctly accounting for the fact that the source qs was reducing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Migration: Use replaces to prevent it from being run again
The replaced migration landed recently, but lets prevent failures for everybody.
-
Contact: Just use DEFAULT_FROM_EMAIL in from_email
contact_form app already provides it.
-
-
-
-
Use the reviewer for attrib if state was changed more recently than the target
-
-
-
-
-
-
-
-
-
-
Commits on Mar 25, 2017
-
i18n: plurals strings also need the value to be interpolated
ungettxt(singular, plural, count, vars)
-
-
-
-
Commits on Mar 27, 2017
-
-
-
-
-
Tests: Add tests for ReportFormView
This will increase coverage and help catching errors.
-
Ensure POOTLE_TITLE is Unicode
This ensures that setting POOTLE_TITLE to a Unicode string will work in emails. allauth expects this to be unicode. Fixes translate#6193
-
Contact: Do not expose report_email report error form
Note that unit is retrieved after self.request is populated. This fixes sending report string error emails with broken subject (no unit number, no language, no project). It is unperformant to retrieve it several times, but it is safer to do it like this as it was not possible to identify any method that is called always after `as_view()` (which is where self.request is being set) but before the methods that need the unit.
-
Contact: Do not expose subject field in report error form
It is not expected to be edited by humans.
-
Contact: Set unit on ReportForm action
ReportForm was passed the unit only the first time it was called (the first time is only to render and display it) but without an action that identifies the unit it was not possible to retrieve and pass the unit the second time ReportForm was being rendered (this would be the time when the form is validated, and if valid emails would be sent) thus sending emails with broken subject (no unit, no language, no project).
-
-
Contact: Move string context to separate field in ReportForm
This way we can: - Prevent the reporter alters the string context - Ensure the reporter provide some question or comment
-
Avoid testing with admin unless we actually need to test superuser.
Commits on Mar 28, 2017
Commits on Mar 29, 2017
Commits on Mar 30, 2017
-
-
-
-
-
-
Migration: Drop stale virtualfoldertreeitem contenttype
So when upgrading user is not prompted.
-
Cleanup: use cached_property in pootle_store.field
the existing implementation for caching a ttk repr of the store was hard to understand, and seemed to be inefficient. this brings it into line with other caching patterns
-
-
Commits on Mar 31, 2017
-
-
-
-
Remove __repr__ as it is not needed
If __repr__ is present X.objects.all() will use it. But in that case you are resppnsible to create a printable string, i.e. UTF8 NOT Unicode. Without __repr__ X.objects.all() will use __unicode__ and will handle all the UTF8 decode/encode required. Moral of the story, just don't create a __repr__ for any objects, rather create __unicode__ and all will be happy and well.
Commits on Apr 1, 2017
-
Cleanup: remove old resource caching
this also saves a couple of hits on db when stores are saved
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Commits on Apr 2, 2017
Commits on Apr 3, 2017
-
-
-
-
Rename get_suggestions, get_submissions, get_created_units
to get_suggestion_events, get_submission_events, get_created_unit_events
-
Add include_meta class var to Log class
This commit allows UnitLog and StoreLog to include META_USERS events.
Commits on Apr 8, 2017
-
Replaced force_unicode by force_text
Those are aliases, but force_text is compatible with Python 3.
Commits on Apr 10, 2017
-
Make tp_tool.update_from_tp() cross project
- allow TP updating from TP from another project
-
-
-
-
-
-
-
-
- Raise error if project directory exists on disk - Add support to move TPs to existing project
-
-
-
-
-
-
-
-
-
-
-
-
-
-