* introduces build status for local fork
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range
* converts xrange to range using six.moves.range
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* converts xrange to range using six.moves.range7
* Revert "introduces build status for local fork"
This reverts commit 61f40983d0.
Mails are not marked as SEEN, when the readonly parameter is True. That's a problem since tickets are being refreshed all few minutes, and, if you have more than 50 unread mails in your inbox, most of them will never be imported to Frappe / ERPNext.
* Add or_filters filter for export_fixtures, to filter by doctype or fieldnames
Eg:
fixtures = [
{
"doctype": "Custom Field",
"or_filters": {
"dt": ["in", [
"Process Payroll",
"Journal Entry Account"
]],
"name": ["in", [
"Print Settings-compact_item_print",
"Account-account_id",
"Account-some_bank_name"
]]
}
}
]
* Passsword Policy Enhancement
In Security Settings, the Password Plociy can be enabled and the passcord strength score can be set.
User will see helpful password validation messages when they change password.
* Enhance Update Password to handle Password Policy
* remove function argument
* update test cases to use strong password
* Add test cases, add default value for minimum password score, make error messages translatable
* make message translatable
* Update update-password.html
* adds new exception to be raised when any improper database configuration is detected
* changes behavior of `check_if_ready_for_barracuda` to raise ImproperDBConfigurationError instead of sys.exit`
* refactors `drop_site` to use a new exactly identical `_drop_site` function.
The reason for this is because the original `drop_site` function is decorated
and cannot be undecorated without nasty hacks. Breaking the function this way
allows me to make use of the `drop-site` logic easily.
* catches the ImproperDBConfigurationError raised from `check_if_ready_for_barracuda` function to drop all the artifacts of the failed new `Site`
We need to pass this event data in field map to show tooltip
field_map: {
"start": "date",
"end": "date",
"id": "name",
"tooltip": "doctor",
"title": "doctor",
"allDay": "allDay",
"child_name": "name"
},