diff --git a/frappe/docs/user/en/bench/guides/settings-limits.md b/frappe/docs/user/en/bench/guides/settings-limits.md index b6ca06265c..8d2a9e4b1d 100644 --- a/frappe/docs/user/en/bench/guides/settings-limits.md +++ b/frappe/docs/user/en/bench/guides/settings-limits.md @@ -36,4 +36,4 @@ Example: You can check your usage by opening the "Usage Info" page from the toolbar / AwesomeBar. A limit will only show up on the page if it has been set. -Doctype Saved +Doctype Saved diff --git a/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md b/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md index fba6397b94..1e41bcfa16 100644 --- a/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md +++ b/frappe/docs/user/en/guides/app-development/adding-custom-button-to-form.md @@ -24,7 +24,7 @@ We should edit `frappe\core\doctype\user\user.js` You should be seeing a button on user form as shown below, -Custom Button +Custom Button diff --git a/frappe/docs/user/en/guides/app-development/dialogs-types.md b/frappe/docs/user/en/guides/app-development/dialogs-types.md index 31f2ccbbb4..3c28a78316 100755 --- a/frappe/docs/user/en/guides/app-development/dialogs-types.md +++ b/frappe/docs/user/en/guides/app-development/dialogs-types.md @@ -4,7 +4,7 @@ Frappe provides a group of standard dialogs that are very useful while coding. ## Alert Dialog - + Alert Dialog is used for showing non-obstructive messages. @@ -21,7 +21,7 @@ It has 2 parameters: ## Prompt Dialog - + Prompt Dialog is used for collecting data from users. @@ -47,7 +47,7 @@ It has 4 parameters: --- ## Confirm Dialog - + Confirm Dialog is used to get a confirmation from the user before executing an action. @@ -73,7 +73,7 @@ It has 3 arguments: ## Message Print - + Message Print is used for showing information to users. @@ -96,7 +96,7 @@ It has 2 arguments: ### Custom Dialog - + You can extend and build your own custom dialogs using `frappe.ui.Dialog` diff --git a/frappe/docs/user/en/guides/app-development/exporting-customizations.md b/frappe/docs/user/en/guides/app-development/exporting-customizations.md index 710db1d3e5..7010a74d18 100644 --- a/frappe/docs/user/en/guides/app-development/exporting-customizations.md +++ b/frappe/docs/user/en/guides/app-development/exporting-customizations.md @@ -4,12 +4,12 @@ A common use case is to extend a DocType via Custom Fields and Property Setters You will see a button for **Export Customizations** - + Here you can select the module and whether you want these particular customizations to be synced after every update. The customizations will be exported to a new folder `custom` in the module folder of your app. The customizations will be saved by the name of the DocType - + When you do `bench update` or `bench migrate` these customizations will be synced to the app. \ No newline at end of file diff --git a/frappe/docs/user/en/guides/app-development/fetch-custom-field-value-from-master-to-all-related-transactions.md b/frappe/docs/user/en/guides/app-development/fetch-custom-field-value-from-master-to-all-related-transactions.md index 7e47d63f5f..ef430a7929 100755 --- a/frappe/docs/user/en/guides/app-development/fetch-custom-field-value-from-master-to-all-related-transactions.md +++ b/frappe/docs/user/en/guides/app-development/fetch-custom-field-value-from-master-to-all-related-transactions.md @@ -5,11 +5,11 @@ Let's say, there is a custom field "VAT Number" in Supplier, which should be fet #### Steps: 1. Create a Custom Field **VAT Number** for *Supplier* document with *Field Type* as **Data**. - + 1. Create another Custom Field **VAT Number** for *Purchase Order* document, but in this case with *Field Type* as **Read Only** or check **Read Only** checkbox. Set the **Options** as `supplier.vat_number`. - + 1. Go to the user menu and click "Reload". 1. Now, on selection of Supplier in a new Purchase Order, **VAT Number** will be fetched automatically from the selected Supplier. - + diff --git a/frappe/docs/user/en/guides/app-development/generating-docs.md b/frappe/docs/user/en/guides/app-development/generating-docs.md index 72db83324d..70a2fba7b0 100755 --- a/frappe/docs/user/en/guides/app-development/generating-docs.md +++ b/frappe/docs/user/en/guides/app-development/generating-docs.md @@ -50,7 +50,7 @@ While linking make sure you add `/docs` to all your links. You can add images in the `/docs/assets` folder. You can add links to the images as follows: - {% raw %}{% endraw %} + {% raw %}{% endraw %} --- diff --git a/frappe/docs/user/en/guides/automated-testing/qunit-testing.md b/frappe/docs/user/en/guides/automated-testing/qunit-testing.md index 10d40999ed..4287712808 100644 --- a/frappe/docs/user/en/guides/automated-testing/qunit-testing.md +++ b/frappe/docs/user/en/guides/automated-testing/qunit-testing.md @@ -12,7 +12,7 @@ To run your files, you can use the **Test Runner**. The **Test Runner** gives a In the CI, all QUnit tests are run by the **Test Runner** using `frappe/tests/test_test_runner.py` - + ### Running Tests diff --git a/frappe/docs/user/en/guides/data/using-data-migration-tool.md b/frappe/docs/user/en/guides/data/using-data-migration-tool.md index ca6285031e..35e237318d 100644 --- a/frappe/docs/user/en/guides/data/using-data-migration-tool.md +++ b/frappe/docs/user/en/guides/data/using-data-migration-tool.md @@ -11,7 +11,7 @@ A Data Migration Plan encapsulates a set of mappings. Let's make a new *Data Migration Plan*. Set the plan name as 'Atlas Sync'. We also need to add mappings in the mappings child table. -New Data Migration Plan +New Data Migration Plan ### Data Migration Mapping @@ -27,7 +27,7 @@ To define a mapping, we need to put in some values that define the structure of 1. Mapping Type: A Mapping can be of type 'Push' or 'Pull', depending on whether the data is to be mapped remotely or locally. It can also be 'Sync', which will perform both push and pull operations in a single cycle. 1. Page Length: This defines the batch size of the sync. -New Data Migration Mapping +New Data Migration Mapping #### Specifying field mappings: @@ -35,11 +35,11 @@ The most basic form of a field mapping would be to specify fieldnames of the rem Let's add the field mappings and save: -Add fields in Data Migration Mapping +Add fields in Data Migration Mapping We can now add the 'Item to Atlas Item' mapping to our Data Migration Plan and save it. -Save Atlas Sync Plan +Save Atlas Sync Plan #### Additional layer of control with pre and post process: @@ -47,24 +47,24 @@ Migrating data frequently involves more steps in addition to one-to-one mapping. In our case, an `item_to_atlas_item` module is created under the `data_migration_mapping` directory in `Integrations` (module for the 'Atlas Sync' plan). -Mapping __init__.py +Mapping __init__.py You can implement the `pre_process` (receives the source doc) and `post_process` (receives both source and target docs, as well as any additional arguments) methods, to extend the mapping process. Here's what some operations could look like: -Pre and Post Process +Pre and Post Process ### Data Migration Connector Now, to connect to the remote source, we need to create a *Data Migration Connector*. -New Data Migration Connector +New Data Migration Connector We only have two connector types right now, let's add another Connector Type in the Data Migration Connector DocType. -Add Connector Type in Data Migration Connector +Add Connector Type in Data Migration Connector Now, let's create a new Data Migration Connector. -Atlas Connector +Atlas Connector As you can see we chose the Connector Type as Atlas. We also added the hostname, username and password for our Atlas instance so that we can authenticate. @@ -74,18 +74,18 @@ Create a new file called `atlas_connection.py` in `frappe/data_migration/doctype We just have to implement the `insert`, `update` and `delete` methods for our atlas connector. We also need to write the code to connect to our Atlas instance in the `__init__` method. Just see `frappe_connection.py` for reference. -Atlas Connection file +Atlas Connection file After creating the Atlas Connector, we also need to import it into `data_migration_connector.py` -Edit Connector file +Edit Connector file ### Data Migration Run Now that we have our connector, the last thing to do is to create a new *Data Migration Run*. A Data Migration Run takes a Data Migration Plan and Data Migration Connector and execute the plan according to our configuration. It takes care of queueing, batching, delta updates and more. -Data Migration Run +Data Migration Run Just click Run. It will now push our Items to the remote Atlas instance and you can see the progress which updates in realtime. diff --git a/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md b/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md index fbd75636fd..44eb70ccc0 100755 --- a/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md +++ b/frappe/docs/user/en/guides/deployment/how-to-enable-social-logins.md @@ -5,7 +5,7 @@ Use Facebook, Google or GitHub authentication to login to Frappe, and your users The system uses the **Email Address** supplied by these services to **match with an existing user** in Frappe. If no such user is found, **a new user is created** of the default type **Website User**, if Signup is not disabled in Website Settings. Any System Manager can later change the user type from **Website User** to **System User**, so that the user can access the Desktop. #### Login screen with Social Logins enabled -Login screen with Social Logins enabled +Login screen with Social Logins enabled To enable these signups, you need to have **Client ID** and **Client Secret** from these authentication services for your Frappe site. The Client ID and Client Secret are to be set in Website > Setup > Social Login Keys. Here are the steps to obtain these credentials. diff --git a/frappe/docs/user/en/guides/integration/how_to_setup_oauth.md b/frappe/docs/user/en/guides/integration/how_to_setup_oauth.md index 27f9746eae..37fd85de85 100644 --- a/frappe/docs/user/en/guides/integration/how_to_setup_oauth.md +++ b/frappe/docs/user/en/guides/integration/how_to_setup_oauth.md @@ -26,7 +26,7 @@ Go to > Setup > Integrations > OAuth Provider Settings - + ### Add Primary Server @@ -40,7 +40,7 @@ As a System Manager go to > Setup > Integrations > OAuth Client - + To add a client fill in the following details diff --git a/frappe/docs/user/en/guides/integration/openid_connect_and_frappe_social_login.md b/frappe/docs/user/en/guides/integration/openid_connect_and_frappe_social_login.md index 75f9086ee9..8efb92fd8e 100644 --- a/frappe/docs/user/en/guides/integration/openid_connect_and_frappe_social_login.md +++ b/frappe/docs/user/en/guides/integration/openid_connect_and_frappe_social_login.md @@ -40,33 +40,35 @@ Now you will see Frappe icon on the login page. Click on this icon to login with ### Part 1 : on Frappe Identity Provider (IDP) Login to IDP - + Add OAuth Client on IDP - + Set Server URL on IDP - + ### Part 2 : on Frappe App Server -Set `Frappe Client ID` and `Frappe Client Secret` on App server (refer the client set on IDP) - + +Set `Frappé Client ID` and `Frappé Client Secret` on App server (refer the client set on IDP) + + **Note**: Frappe Server URL is the main server where identities from your organization are stored. Login Screen on App Server (login with frappe) - + ### Part 3 : Redirected on IDP login with user on IDP - + Confirm Access on IDP - + ### Part 4 : Back on App Server Logged in on app server with ID from IDP - + diff --git a/frappe/docs/user/en/guides/integration/social_login_key.md b/frappe/docs/user/en/guides/integration/social_login_key.md index d0896e8fa9..f53fde4092 100644 --- a/frappe/docs/user/en/guides/integration/social_login_key.md +++ b/frappe/docs/user/en/guides/integration/social_login_key.md @@ -10,7 +10,7 @@ To add Social Login Key go to Social Login Key - + 1. Select the Social Login Provider or select "Custom" 2. If required for provider enter "Base URL" diff --git a/frappe/docs/user/en/guides/integration/using_oauth.md b/frappe/docs/user/en/guides/integration/using_oauth.md index 208e07b452..48bb853d0a 100644 --- a/frappe/docs/user/en/guides/integration/using_oauth.md +++ b/frappe/docs/user/en/guides/integration/using_oauth.md @@ -20,7 +20,7 @@ redirect_uri = #### Confirmation Dialog - + Click 'Allow' to receive authorization code in redirect uri. diff --git a/frappe/docs/user/en/guides/integration/webhooks.md b/frappe/docs/user/en/guides/integration/webhooks.md index ff7df4015f..d453791051 100644 --- a/frappe/docs/user/en/guides/integration/webhooks.md +++ b/frappe/docs/user/en/guides/integration/webhooks.md @@ -10,7 +10,7 @@ To add Webhook go to Webhook - + 1. Select the DocType for which hook needs to be triggered e.g. Note 2. Select the DocEvent for which hook needs to be triggered e.g. on_trash diff --git a/frappe/docs/user/en/guides/portal-development/generators.md b/frappe/docs/user/en/guides/portal-development/generators.md index 8bf52d7299..78d83d20f6 100644 --- a/frappe/docs/user/en/guides/portal-development/generators.md +++ b/frappe/docs/user/en/guides/portal-development/generators.md @@ -22,7 +22,7 @@ We added `published`, `route` in the DocType **Note:** The field `route` is mandatory -Generator fields +Generator fields #### 2. Added Website Generator to Hooks diff --git a/frappe/docs/user/en/guides/portal-development/portal-roles.md b/frappe/docs/user/en/guides/portal-development/portal-roles.md index 2248bb0b55..d3f5be7287 100644 --- a/frappe/docs/user/en/guides/portal-development/portal-roles.md +++ b/frappe/docs/user/en/guides/portal-development/portal-roles.md @@ -8,7 +8,7 @@ Roles can be assigned to Website Users and they will see menu based on their rol 1. Each Portal Menu Item can have a role associated with it. If that role is set, then only those users having that role can see that menu item 1. Rules can be set for default roles that will be set on default users on hooks -Portal Settings +Portal Settings #### Rules for Default Role diff --git a/frappe/docs/user/en/guides/portal-development/web-forms.md b/frappe/docs/user/en/guides/portal-development/web-forms.md index 7cca8de2cc..533790952e 100644 --- a/frappe/docs/user/en/guides/portal-development/web-forms.md +++ b/frappe/docs/user/en/guides/portal-development/web-forms.md @@ -2,7 +2,7 @@ Web Forms are a powerful way to add forms to your website. Web forms are powerful and scriptable and from Version 7.1+ they also include tables, paging and other utilities -Web Form +Web Form ### Standard Web Forms diff --git a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md index c4c047a63f..32ed2a016e 100755 --- a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md +++ b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-query-report.md @@ -8,7 +8,7 @@ To create a new Query Report: ### 1. Create a new Report -Query Report +Query Report 1. Set type as "Query Report" 1. Set the reference DocType - Users that have access to the reference DocType will have access to the report @@ -37,7 +37,7 @@ You can define complex queries such as: ### 3. Check the Report -Query Report +Query Report ### 4. Advanced (adding filters) diff --git a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-script-reports.md b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-script-reports.md index 80522d435b..74479a8b9c 100755 --- a/frappe/docs/user/en/guides/reports-and-printing/how-to-make-script-reports.md +++ b/frappe/docs/user/en/guides/reports-and-printing/how-to-make-script-reports.md @@ -10,7 +10,7 @@ Since these reports give you unrestricted access via Python scripts, they can on ### 1. Create a new Report -Script Report +Script Report 1. Set Report Type as "Script Report" 1. Set "Is Standard" as "Yes" diff --git a/frappe/docs/user/en/guides/reports-and-printing/print-format-for-reports.md b/frappe/docs/user/en/guides/reports-and-printing/print-format-for-reports.md index 07a7bc222b..f663816757 100755 --- a/frappe/docs/user/en/guides/reports-and-printing/print-format-for-reports.md +++ b/frappe/docs/user/en/guides/reports-and-printing/print-format-for-reports.md @@ -58,7 +58,7 @@ Here is how the General Ledger Report is built: Here is what the report looks like: -General Ledger +General Ledger ##### Comments: diff --git a/frappe/docs/user/en/tutorial/controllers.md b/frappe/docs/user/en/tutorial/controllers.md index 09edce15d0..b994f71971 100755 --- a/frappe/docs/user/en/tutorial/controllers.md +++ b/frappe/docs/user/en/tutorial/controllers.md @@ -48,7 +48,7 @@ In this script: Check if your validations work by creating new records -Transaction +Transaction #### Debugging diff --git a/frappe/docs/user/en/tutorial/doctypes.md b/frappe/docs/user/en/tutorial/doctypes.md index b57aca5afa..2e70ab4146 100755 --- a/frappe/docs/user/en/tutorial/doctypes.md +++ b/frappe/docs/user/en/tutorial/doctypes.md @@ -6,7 +6,7 @@ To create a new **DocType**, go to: > Developer > Documents > Doctype > New -New Doctype +New Doctype In the DocType, first the Module, which in our case is **Library Management** @@ -25,7 +25,7 @@ Fields are much more than database columns, they can be: Let us add the fields of the Article. -Adding Fields +Adding Fields When you add fields, you need to enter the **Type**. **Label** is optional for Section Break and Column Break. **Name** (`fieldname`) is the name of the database table column and also the property of the controller. This has to be *code friendly*, i.e. it has to have small cases are _ instead of " ". If you leave the Fieldname blank, it will be automatically set when you save it. @@ -47,7 +47,7 @@ We can add the following fields: After adding the fields, hit done and add a new row in the Permission Rules section. For now, let us give Read, Write, Create, Delete and Report access to **Librarian**. Frappe has a finely grained Role based permission model. You can also change permissions later using the **Role Permissions Manager** from **Setup**. -Adding Permissions +Adding Permissions #### Saving diff --git a/frappe/docs/user/en/tutorial/naming-and-linking.md b/frappe/docs/user/en/tutorial/naming-and-linking.md index a3400ae527..dd0fca7245 100755 --- a/frappe/docs/user/en/tutorial/naming-and-linking.md +++ b/frappe/docs/user/en/tutorial/naming-and-linking.md @@ -4,7 +4,7 @@ Then let us create the other DocType and save it too: 1. Library Member (First Name, Last Name, Email Address, Phone, Address) -Doctype Saved +Doctype Saved #### Naming of DocTypes @@ -20,7 +20,7 @@ This can be set by entering the **Autoname** field. For controller, leave blank. > **Search Fields**: A DocType may be named on a series but it still needs to be searched by name. In our case, the Article will be searched by the title or the author name. So this can be entered in search field. -Autonaming and Search Field +Autonaming and Search Field #### Link and Select Fields @@ -30,11 +30,11 @@ In our example, in the Library Transaction DocType, we have to link both the Lib **Note:** Remeber that Link fields are not automatically set as Foreign Keys in the MariaDB database, because that will implicitly index the column. This may not be optimum hence the Foreign Key validation is done by the Framework. -Link Field +Link Field For select fields, as we mentioned earlier, add the various options in the **Options** input box, each option on a new row. -Select Field +Select Field Similary complete making the other models. @@ -44,7 +44,7 @@ A standard pattern is when you select an ID, say **Library Member** in **Library To do this, we can use Read Only fields and in options, we can set the the name of the link and the fieldname of the property we want to fetch. For this example in **Member First Name** we can set `library_member.first_name` -Fetch values +Fetch values ### Complete the Models @@ -52,19 +52,19 @@ In the same way, you can complete all the models so that the final fields look l #### Article -Article +Article #### Library Member -Library Member +Library Member #### Library Membership -Library Membership +Library Membership #### Library Transaction -Library Transaction +Library Transaction > Make sure to give permissions to **Librarian** on each DocType diff --git a/frappe/docs/user/en/tutorial/reports.md b/frappe/docs/user/en/tutorial/reports.md index 6e2a2b6c42..03b61822f2 100755 --- a/frappe/docs/user/en/tutorial/reports.md +++ b/frappe/docs/user/en/tutorial/reports.md @@ -2,6 +2,6 @@ You can also click on the Reports text on the sidebar (left) to see tabulated records -Report +Report {next} diff --git a/frappe/docs/user/en/tutorial/roles.md b/frappe/docs/user/en/tutorial/roles.md index 42b8246bec..d358556083 100755 --- a/frappe/docs/user/en/tutorial/roles.md +++ b/frappe/docs/user/en/tutorial/roles.md @@ -9,6 +9,6 @@ To create a new Role, go to: > Setup > Users > Role > New -Adding Roles +Adding Roles {next} diff --git a/frappe/docs/user/en/tutorial/single-doctypes.md b/frappe/docs/user/en/tutorial/single-doctypes.md index a9f1b853ad..9b0e4171b1 100755 --- a/frappe/docs/user/en/tutorial/single-doctypes.md +++ b/frappe/docs/user/en/tutorial/single-doctypes.md @@ -4,6 +4,6 @@ A application will usually have a Settings page. In our application, we can defi To create an new Single DocType, mark the **Is Single** property as checked. -Single Doctypes +Single Doctypes {next} diff --git a/frappe/docs/user/en/tutorial/start.md b/frappe/docs/user/en/tutorial/start.md index 4b7f60db73..0182654494 100755 --- a/frappe/docs/user/en/tutorial/start.md +++ b/frappe/docs/user/en/tutorial/start.md @@ -14,7 +14,7 @@ To start the development server, run `bench start` You can now open your browser and go to `http://localhost:8000`. You should see this login page if all goes well: -Login Screen +Login Screen Now login with : @@ -24,7 +24,7 @@ Password : **Use the password that was created during installation** When you login, you should see the "Desk" home page -Desk +Desk As you can see, the Frappe basic system comes with several pre-loaded applications like To Do, File Manager etc. These apps can integrated in your app workflow as we progress. diff --git a/frappe/docs/user/en/tutorial/users-and-records.md b/frappe/docs/user/en/tutorial/users-and-records.md index fd86030a40..394899a795 100755 --- a/frappe/docs/user/en/tutorial/users-and-records.md +++ b/frappe/docs/user/en/tutorial/users-and-records.md @@ -12,7 +12,7 @@ Create a new User and set the name and first name and new password. Also give the Librarian and Library Member Roles to this user -Add User Roles +Add User Roles Now logout and login using the new user id and password. @@ -20,36 +20,36 @@ Now logout and login using the new user id and password. You will now see an icon for the Library Management module. Click on that icon and you will see the Module page: -Library Management Module +Library Management Module Here you can see the DocTypes that we have created for the application. Let us start creating a few records. First let us create a new Article: -New Article +New Article Here you will see that the DocType you had created has been rendered as a form. The validations and other rules will also apply as designed. Let us fill out one Article. -New Article +New Article You can also add an image. -Attach Image +Attach Image Now let us create a new member: -New Library Member +New Library Member After this, let us create a new membership record for the member. Here if you remember we had set the values of Member First Name and Member Last Name to be directly fetched from the Member records and as soon as you will select the member id, the names will be updated. -New Library Membership +New Library Membership As you can see that the date is formatted as year-month-day which is a system format. To set / change date, time and number formats, go to > Setup > Settings > System Settings -System Settings +System Settings {next} diff --git a/frappe/docs/user/en/tutorial/web-views.md b/frappe/docs/user/en/tutorial/web-views.md index 1affecea77..2953104958 100755 --- a/frappe/docs/user/en/tutorial/web-views.md +++ b/frappe/docs/user/en/tutorial/web-views.md @@ -16,11 +16,11 @@ Let us look at the standard Web Views: If you are logged in as the test user, go to `/article` and you should see the list of articles: -web list +web list Click on one article and you will see the default web view -web view +web view Now if you want to make a better list view for the article, drop a file called `row_template.html` in the `library_management/templates/includes/list/` folder. Here is an example file: @@ -46,7 +46,7 @@ Here, you will get all the properties of the article in the `doc` object. The updated list view looks like this! -new web list +new web list #### Home Page diff --git a/frappe/docs/user/es/bench/guides/settings-limits.md b/frappe/docs/user/es/bench/guides/settings-limits.md index a481db66da..a72ddc2d79 100644 --- a/frappe/docs/user/es/bench/guides/settings-limits.md +++ b/frappe/docs/user/es/bench/guides/settings-limits.md @@ -36,4 +36,4 @@ Ejemplo: Puedes verificar el uso abriendo la página de "Usage Info" ubicada en el toolbar / AwesomeBar. Un límite solo va a mostrarse en la página si ha sido configurado. -Doctype Saved +Doctype Saved diff --git a/frappe/docs/user/es/tutorial/controllers.md b/frappe/docs/user/es/tutorial/controllers.md index 7053719970..e9ea7527e8 100644 --- a/frappe/docs/user/es/tutorial/controllers.md +++ b/frappe/docs/user/es/tutorial/controllers.md @@ -48,7 +48,7 @@ En este script: Verifica si sus validaciones funcionan creando nuevos registros. -Transaction +Transaction #### Depurando diff --git a/frappe/docs/user/es/tutorial/doctypes.md b/frappe/docs/user/es/tutorial/doctypes.md index 3e0a9583f8..6d574ac721 100644 --- a/frappe/docs/user/es/tutorial/doctypes.md +++ b/frappe/docs/user/es/tutorial/doctypes.md @@ -6,7 +6,7 @@ Para crear un nuevo **DocType**, ir a: > Developer > Documents > Doctype > New -New Doctype +New Doctype En el DocType, primero el módulo, lo que en nuestro caso es **Library Management** @@ -26,7 +26,7 @@ Fields are much more than database columns, they can be: Vamos a agregar los campos de el Article. -Adding Fields +Adding Fields Cuando agredas los campos, necesitas llenar el campo **Type**. **Label** es opcional para los Section Break y Column Break. **Name** (`fieldname`) es el nombre de la columna en la tabla de la base de datos y tambien el nombre de la propiedad para el controlador. Esto tiene que ser *code friendly*, i.e. Necesitas poner _ en lugar de " ". Si dejas en blanco este campo, se va a llenar automáticamente al momento de guardar. @@ -48,7 +48,7 @@ Podemos agregar los siguientes campos: Despues de agregar los campos, dar click en hecho y agrega una nueva fila en la sección de Permission Roles. Por ahora, vamos a darle accesos Lectura, Escritura, Creación y Reportes al Role **Librarian**. Frappe cuenta con un sistema basados en el modelo de Roles finamente granulado. Puedes cambiar los permisos más adealante usando el **Role Permissions Manager** desde **Setup**. -Adding Permissions +Adding Permissions #### Guardando diff --git a/frappe/docs/user/es/tutorial/naming-and-linking.md b/frappe/docs/user/es/tutorial/naming-and-linking.md index be951f323c..da929b0272 100644 --- a/frappe/docs/user/es/tutorial/naming-and-linking.md +++ b/frappe/docs/user/es/tutorial/naming-and-linking.md @@ -4,7 +4,7 @@ Vamos a crear otro DocType y guardarlo: 1. Library Member (First Name, Last Name, Email Address, Phone, Address) -Doctype Saved +Doctype Saved #### Nombrando DocTypes @@ -20,7 +20,7 @@ Esto puede ser seteado a traves del campo **Autoname**. Para el controlador, dej > **Search Fields**: Un DocType puede ser nombrado por serie pero seguir teniendo la necesidad de ser buscado por nombre. En nuestro caso, el Article va ser buscado por el título o el nombre del autor. Por lo que vamos a poner esos campos en el campo de search. -Autonaming and Search Field +Autonaming and Search Field #### Campo de Enlace y Campo Select @@ -30,11 +30,11 @@ En nuestro ejemplo, en el DocType de Library Transaction,tenemos que enlazar los **Nota:** Recuerda que los campos de Enlace no son automáticamente establecidos como claves foraneas en la base de datos MariaDB, porque esto crearía un indice en la columna. Las validaciones de claves foraneas son realizadas por el Framework. -Link Field +Link Field Por campos de tipo Select, como mencionamos antes, agrega varias opciones en la caja de texto **Options**, cada una en una nueva linea. -Select Field +Select Field De manera similar continua haciendo los otros modelos. @@ -44,7 +44,7 @@ Un patrón estandar es que cuando seleccionas un ID, dice **Library Member** en Para hacer esto, podemos usar campos de solo lectura y en opciones, podemos especificar el nombre del link (enlace) y el campo o propiedad que deseas obtener. Para este ejempo en **Member First Name** podemos especificar `library_member.first_name`. -Fetch values +Fetch values ### Completar los modelos @@ -52,19 +52,19 @@ En la misma forma, puedes completar todos los modelos, todos los campos deben ve #### Article -Article +Article #### Library Member -Library Member +Library Member #### Library Membership -Library Membership +Library Membership #### Library Transaction -Library Transaction +Library Transaction > Asegurate de dar permiso a **Librarian** en cada DocType diff --git a/frappe/docs/user/es/tutorial/reports.md b/frappe/docs/user/es/tutorial/reports.md index 99d6655792..3fb5a9d76e 100644 --- a/frappe/docs/user/es/tutorial/reports.md +++ b/frappe/docs/user/es/tutorial/reports.md @@ -2,6 +2,6 @@ Puedes dar click en el texto que dice Reportes en el panel lateral izquierdo para ver los registros de manera tabulada. -Report +Report {next} diff --git a/frappe/docs/user/es/tutorial/roles.md b/frappe/docs/user/es/tutorial/roles.md index 017cd064c9..d65aed184c 100644 --- a/frappe/docs/user/es/tutorial/roles.md +++ b/frappe/docs/user/es/tutorial/roles.md @@ -9,6 +9,6 @@ Para crear un nuevo Role, ir a: > Setup > Users > Role > New -Adding Roles +Adding Roles {next} diff --git a/frappe/docs/user/es/tutorial/single-doctypes.md b/frappe/docs/user/es/tutorial/single-doctypes.md index a091a2a2ec..0b8d7745c2 100644 --- a/frappe/docs/user/es/tutorial/single-doctypes.md +++ b/frappe/docs/user/es/tutorial/single-doctypes.md @@ -4,6 +4,6 @@ Una aplicación normalmente va a tener una página de configuración. En nuestra Para crear un Single DocType, marca el checkbox **Is Single**. -Single Doctypes +Single Doctypes {next} diff --git a/frappe/docs/user/es/tutorial/start.md b/frappe/docs/user/es/tutorial/start.md index f086371ccc..f8abb4d675 100644 --- a/frappe/docs/user/es/tutorial/start.md +++ b/frappe/docs/user/es/tutorial/start.md @@ -14,7 +14,7 @@ Para iniciar el servidor de desarrollo, ejecuta `bench start`. Ahora abre tu navegador y ve a la dirección `http://localhost:8000`. Deberías ver la páagina de inicio de sesión si todo salió bien.: -Login Screen +Login Screen Ahora accede con : @@ -24,7 +24,7 @@ Password : **Usa la contraseña que creaste durante la instalación** Cuando accedas, deberías poder ver la página de inicio (Desk). -Desk +Desk Como puedes ver, el sistema básico de Frappe viene con algunas aplicaciones preinstaladas como To Do, File Manager etc. Estas aplicaciones pueden integrarse en el flujo de trabajo de su aplicació a medida que avancemos. diff --git a/frappe/docs/user/es/tutorial/users-and-records.md b/frappe/docs/user/es/tutorial/users-and-records.md index 6020e80fe7..e599c4301b 100644 --- a/frappe/docs/user/es/tutorial/users-and-records.md +++ b/frappe/docs/user/es/tutorial/users-and-records.md @@ -12,7 +12,7 @@ Crea un nuevo Usuario y llena los campos de nombre, primer nombre y nueva contra Luego dale los Roles de Librarian y de Library Member a este usuario. -Add User Roles +Add User Roles Ahora cierra sesión y accede usando las credenciales del nuevo usuario. @@ -20,36 +20,36 @@ Ahora cierra sesión y accede usando las credenciales del nuevo usuario. Debes ver un ícono del módulo de Library Management. Dar click en el ícono para entrar a la página del módulo: -Library Management Module +Library Management Module Aquí puedes ver los DocTypes que fueron creados para la aplicación. Vamos a comenzar a crear nuevos registros. Primero vamos a crear un nuevo Article: -New Article +New Article Aquí vas a ver que los DocTypes que haz creado han sido renderizados como un formulario. Las validaciones y las otras restricciones también están aplicadas según se diseñaron. Vamos a llenar los datos de un Article. -New Article +New Article Puedes agregar una imagen si deseas. -Attach Image +Attach Image Ahora vamos a crear un nuevo miembro: -New Library Member +New Library Member Despues de esto, crearemos una nueva membresía (membership) para el miembro. Si recuerdas, aquí hemos específicado los valores del nombre y apellido del miembro directamente desde el registro del miembro tan pronto selecciones el miembro id, los nombres serán actualizados. -New Library Membership +New Library Membership Como puedes ver la fecha tiene un formato de año-mes-día lo cual es una fecha del sistema. Para seleccionar o cambiar la fecha, tiempo y formatos de números, ir a: > Setup > Settings > System Settings -System Settings +System Settings {next} diff --git a/frappe/docs/user/es/tutorial/web-views.md b/frappe/docs/user/es/tutorial/web-views.md index 8556ed6308..2fe98f1523 100644 --- a/frappe/docs/user/es/tutorial/web-views.md +++ b/frappe/docs/user/es/tutorial/web-views.md @@ -16,11 +16,11 @@ Vamos a ver las Vistas web estandar: Si estas logueado como el usuario de prueba, ve a `/article` y deberías ver la lista de artículos. -web list +web list Da click en uno de los artículos y vas a ver una vista web por defecto -web view +web view Si deseas hacer una mejor vista para la lista de artículos, crea un archivo llamado `row_template.html` en el directorio `library_management/templates/includes/list/`. Aquí hay un archivo de ejemplo: @@ -45,7 +45,7 @@ Aquí, vas a tener todas las propiedades de un artículo en el objeto `doc`. La lista actualizada debe lucir de esta manera! -new web list +new web list #### Página de Inicio diff --git a/frappe/docs/user/fr/tutorial/controllers.md b/frappe/docs/user/fr/tutorial/controllers.md index 2175ffbac8..dd9f2ab69d 100644 --- a/frappe/docs/user/fr/tutorial/controllers.md +++ b/frappe/docs/user/fr/tutorial/controllers.md @@ -50,7 +50,7 @@ Dans ce script: Vérifiez vos validations en créant de nouveaux enregistrements. -Transaction +Transaction #### Debogage diff --git a/frappe/docs/user/fr/tutorial/doctypes.md b/frappe/docs/user/fr/tutorial/doctypes.md index c1810b140b..698e1e6c69 100644 --- a/frappe/docs/user/fr/tutorial/doctypes.md +++ b/frappe/docs/user/fr/tutorial/doctypes.md @@ -6,7 +6,7 @@ Pour créer un nouveau **DocType**, rendez-vous sur: > Developer > Documents > Doctype > New -New Doctype +New Doctype Dans un premier temps, saisissez le module, dans notre cas, **Library Managment** @@ -25,7 +25,7 @@ Les champs sont bien plus que des colonnes d'une base de données, ils peuvent Ajoutons des champs pour l'article. -Adding Fields +Adding Fields Quand vous ajoutez des champs, vous devez entrer le **Type**. Le **Label** est optionnel pour les retours de sections et de colonnes. Le **Name** (`fieldname`) ets le nom de la colonne dans la base de données et aussi la propriété du controleur. Les définitions @@ -54,7 +54,7 @@ ajoutons les droits le lecture, écriture, création et suppression au modèle * permissions sur les modèles. Vous pouvez aussi changer les permissions plus tard en utilisant le gestionnaire de permissions dans la configuration. -Adding Permissions +Adding Permissions #### Sauvegarde diff --git a/frappe/docs/user/fr/tutorial/naming-and-linking.md b/frappe/docs/user/fr/tutorial/naming-and-linking.md index 7f71fc9dfe..28ef965efa 100644 --- a/frappe/docs/user/fr/tutorial/naming-and-linking.md +++ b/frappe/docs/user/fr/tutorial/naming-and-linking.md @@ -4,7 +4,7 @@ Définissons un nouveau **DocType**: 1. Library Member (First Name, Last Name, Email Address, Phone, Address) -Doctype Saved +Doctype Saved #### Le nommage des DocTypes @@ -21,7 +21,7 @@ Cela peut être configuré par le champs **Autoname**. Pour le controleur, laiss > **Search Fields**: Un **DocType** peut être nommé sur la base d'une serie mais nous devons toujours pouvoir le chercher par un nom. Dans notre cas, l'arcicle peut etre cherché par un titre ou par l'auteur. Remplissons donc le champs **Search Fields**. -Autonaming and Search Field +Autonaming and Search Field #### Relation et champs select @@ -34,12 +34,12 @@ Dans notre exemple, pour le **doctype** `Library Transaction`, nous avons un lie d'indexer la colonne. Cela pourrait ne pas être optimum, c'est pour cela que la validation de la clé étrangère est faite par le framework. -Link Field +Link Field Pour les champs **select**, comme mentionné plus tôt, ajoutez chacune des options dans le champs **Options**, chaque option sur une nouvelle ligne. -Select Field +Select Field faites de même pour les autres modèles. @@ -52,7 +52,7 @@ Pour cela, nous pouvons utiliser des champs en lecture seules et, dans les optio et le nom du champs de la propriété que nous voulons parcourir. Dans cet exemple, dans **Member First Name** nous pouvons définir `library_member.first_name` -Fetch values +Fetch values ### Completer les Modeles @@ -60,19 +60,19 @@ De la même facon, vous pouvez compléter les autres modèles pour qu'au final l #### Article -Article +Article #### Library Member -Library Member +Library Member #### Library Membership -Library Membership +Library Membership #### Library Transaction -Library Transaction +Library Transaction > Vérifiez que le modèles **Librarian** aient les permissions sur chaque **DocType**. diff --git a/frappe/docs/user/fr/tutorial/reports.md b/frappe/docs/user/fr/tutorial/reports.md index b9bf4d024d..92b0ef4d45 100644 --- a/frappe/docs/user/fr/tutorial/reports.md +++ b/frappe/docs/user/fr/tutorial/reports.md @@ -2,6 +2,6 @@ Vous pouvez aussi cliquer sur le texte "Rapports" dans la barre latérale de gauche pour voir vos données dans un tableau. -Report +Report {next} diff --git a/frappe/docs/user/fr/tutorial/roles.md b/frappe/docs/user/fr/tutorial/roles.md index e0bc38da5b..ce5add6000 100644 --- a/frappe/docs/user/fr/tutorial/roles.md +++ b/frappe/docs/user/fr/tutorial/roles.md @@ -10,6 +10,6 @@ Pour créer un nouveau rôle, se rendre sur: > Setup > Users > Role > New -Adding Roles +Adding Roles {next} diff --git a/frappe/docs/user/fr/tutorial/single-doctypes.md b/frappe/docs/user/fr/tutorial/single-doctypes.md index 0351761950..e3b10a0523 100644 --- a/frappe/docs/user/fr/tutorial/single-doctypes.md +++ b/frappe/docs/user/fr/tutorial/single-doctypes.md @@ -7,6 +7,6 @@ d'une classe. Appelons le **Library Managment Settings**. Pour créer un DocType de type **Single** cochez la case **Is Single**. -Single Doctypes +Single Doctypes {suite} diff --git a/frappe/docs/user/fr/tutorial/start.md b/frappe/docs/user/fr/tutorial/start.md index 696e903aae..608127c0d5 100644 --- a/frappe/docs/user/fr/tutorial/start.md +++ b/frappe/docs/user/fr/tutorial/start.md @@ -14,7 +14,7 @@ Pour démarrer le serveur de développement, lancez la commande `bench start` Vous pouvez maintenant ouvrir votre navigateur et vous rendre sur `http://localhost:8000`. Si tout se passe bien vous devriez voir: -Login Screen +Login Screen Maintenant, connectez vous avec les identifiants suivants: @@ -24,7 +24,7 @@ Mot de passe: **Le mot de passe que vous avez définis pendant l'installation** Une fois connecté, vous devriez voir le `Desk`, c'est à dire la page d'accueil -Desk +Desk Comme vous pouvez le voir, Frappe fournit quelques applications comme un To Do, un gestionnaire de fichiers etc. Ces applications peuvent être intégrées par la suite. diff --git a/frappe/docs/user/fr/tutorial/users-and-records.md b/frappe/docs/user/fr/tutorial/users-and-records.md index e259369a2b..e0a714c9c4 100644 --- a/frappe/docs/user/fr/tutorial/users-and-records.md +++ b/frappe/docs/user/fr/tutorial/users-and-records.md @@ -12,7 +12,7 @@ Afin de créer des enregistrements, nous avons tout d'abord besoin de créer un Saisissez un nom, un prénom ainsi qu'un mot de passe à votre utilisateur pour le créer et donnez lui les rôles `Librarian` et `Library Member`. -Add User Roles +Add User Roles Maintenant déconnectez-vous puis connectez-vous avec l'utilisateur que vous venez de créer. @@ -21,39 +21,39 @@ Maintenant déconnectez-vous puis connectez-vous avec l'utilisateur que vous ven Vous allez désormais voir une icone pour notre module de gestion de librairie. Cliquez sur cette icone et vous apercevrez la page du module: -Library Management Module +Library Management Module Vous pouvez donc voir les **DocTypes** que nous avons créés pour l'application. Créons quelques enregistrements. Définissons un nouvel Article: -New Article +New Article Le **DocType** que vous avons définis est transformé en formulaire. Les règles de validation seront appliquées selon nos définitions. Remplissons le formulaire pour créer notre premier article. -New Article +New Article Vous pouvez aussi ajouter une image. -Attach Image +Attach Image Maintenant créons un nouveau membre. -New Library Member +New Library Member Après cela, définissons un nouvel abonnement pour ce membre. Ici, si vous vous souvenez, nous avons définis que les noms et prénoms doivent automatiquement être renseignés dès que nous avons selectionné l'ID du membre. -New Library Membership +New Library Membership Comme vous pouvez le voir, la date est formattée en années-mois-jour qui est le format du système. Pour configurer / changer le format de la date et de l'heure, rendez-vous sur: > Setup > Settings > System Settings -System Settings +System Settings {suite} diff --git a/frappe/docs/user/fr/tutorial/web-views.md b/frappe/docs/user/fr/tutorial/web-views.md index 9fc6865a67..9b0f80a0e9 100644 --- a/frappe/docs/user/fr/tutorial/web-views.md +++ b/frappe/docs/user/fr/tutorial/web-views.md @@ -20,11 +20,11 @@ Jettons un oeil aux vues standards: Si vous êtes connecté avec votre utilisateur de test, rendez-vous sur`/article` et vous devriez voir la liste des articles: -web list +web list Cliquez sur un article et vous devriez voir une vue par défaut. -web view +web view Maintenant, si vous voulez une meilleur liste pour vos articles, créez un fichier appelé `row_template.html` dans le repertoire `library_management/templates/includes/list/`. Voici un exemple du contenu de ce fichier: @@ -50,7 +50,7 @@ Ici, vous aurez toutes les propriétés d'un article dans l'object `doc`. La mise à jour de la liste ressemble à ca ! -new web list +new web list #### La page d'accueil diff --git a/frappe/docs/user/pt/tutorial/controllers.md b/frappe/docs/user/pt/tutorial/controllers.md index 85fc8fd1f6..cf657e9d0d 100755 --- a/frappe/docs/user/pt/tutorial/controllers.md +++ b/frappe/docs/user/pt/tutorial/controllers.md @@ -48,7 +48,7 @@ Nesse script: Verifique se suas validações funcionaram, criando de novos registros. -Transaction +Transaction #### Debugging diff --git a/frappe/docs/user/pt/tutorial/doctypes.md b/frappe/docs/user/pt/tutorial/doctypes.md index 666f550bca..fa6c7a26ee 100755 --- a/frappe/docs/user/pt/tutorial/doctypes.md +++ b/frappe/docs/user/pt/tutorial/doctypes.md @@ -6,7 +6,7 @@ Para criar um novo **DocType**, vá para: > Developer > Documents > Doctype > New -New Doctype +New Doctype No DocType, criamos o módulo, que no nosso caso é **Library Managment** @@ -25,7 +25,7 @@ Os campos são muito mais do que colunas de banco de dados, eles podem ser: Vamos adicionar os campos do artigo. -Adding Fields +Adding Fields Quando você adiciona campos, você precisa digitar o **Type**. **Label** é opcional para quebra de seção e quebra de coluna. **Name** (`fieldname`) é o nome da coluna da tabela de banco de dados e também a propriedade do controlador. Isso tem que ser um *código amigável*, ou seja, ele tem que ter caracteres minusculos e _ em vez de "". Se você deixar o nome do campo em branco, ele será ajustado automaticamente quando você salvá-lo. @@ -47,7 +47,7 @@ Nós podemos adicionar os seguintes campos: Depois de adicionar os campos, finalize e adicione uma nova linha na seção Regras de permissão. Por enquanto, vamos dar permissão de Read, Write, Create, Delete and Report, a **Librarian**. Frappe tem uma Role baseado nas permissões do modelo. Você também pode alterar as permissões posteriormente usando o **Role Permissions Manager** do **Setup**. -Adding Permissions +Adding Permissions #### Salvando diff --git a/frappe/docs/user/pt/tutorial/naming-and-linking.md b/frappe/docs/user/pt/tutorial/naming-and-linking.md index e92f656b55..1d72cd55c3 100755 --- a/frappe/docs/user/pt/tutorial/naming-and-linking.md +++ b/frappe/docs/user/pt/tutorial/naming-and-linking.md @@ -4,7 +4,7 @@ Em seguida, vamos criar outro DocType e salva-lo também: 1. Library Member (First Name, Last Name, Email Address, Phone, Address) -Doctype Saved +Doctype Saved #### Nomeação de DocTypes @@ -20,7 +20,7 @@ Isso pode ser definido através do preenchimento do campo **Autoname**. Para o c > **Search Fields**: A DocType pode ser nomeado em uma série, mas ele ainda precisa ser pesquisado por nome. No nosso caso, o artigo será procurado pelo título ou o nome do autor. Portanto, este pode ser inserido no campo de pesquisa. -Autonaming and Search Field +Autonaming and Search Field #### Vinculando e selecionando campos @@ -30,11 +30,11 @@ No nosso exemplo, na Library Transaction DocType, temos que ligar o Membro da Bi **Observação:** Lembre-se que os campos link não são automaticamente configurados como chaves estrangeiras no banco de dados MariaDB, porque isso vai implicitamente indexar a coluna. Isto pode não ser ideal, mas, a validação de chave estrangeira é feito pelo Framework. -Link Field +Link Field Para campos de multipla escolha, como mencionamos anteriormente, adicione as várias opções na caixa de entrada **Options**, cada opção em uma nova linha. -Select Field +Select Field Fazer o mesmo para outros modelos. @@ -44,7 +44,7 @@ Um modelo padrão é quando você seleciona um ID, **Library Member** na **Libra Para fazer isso, podemos usar campos de somente leitura e de opções, podemos definir o nome do link e o nome do campo da propriedade que deseja buscar. Para este exemplo no **Member First Name** podemos definir `library_member.first_name` -Fetch values +Fetch values ### Complete os modelos @@ -52,19 +52,19 @@ Da mesma forma, você pode completar todos os modelos de modo que os campos fina #### Article -Article +Article #### Library Member -Library Member +Library Member #### Library Membership -Library Membership +Library Membership #### Library Transaction -Library Transaction +Library Transaction > Lembre-se de dar permissões para **Librarian** em cada DocType diff --git a/frappe/docs/user/pt/tutorial/reports.md b/frappe/docs/user/pt/tutorial/reports.md index c7a241bbc4..1889705874 100755 --- a/frappe/docs/user/pt/tutorial/reports.md +++ b/frappe/docs/user/pt/tutorial/reports.md @@ -2,6 +2,6 @@ Você também pode clicar sobre o texto Relatórios na barra lateral (esquerda) para ver os registros tabulados -Report +Report {next} diff --git a/frappe/docs/user/pt/tutorial/roles.md b/frappe/docs/user/pt/tutorial/roles.md index 07b687f936..286d39afa7 100755 --- a/frappe/docs/user/pt/tutorial/roles.md +++ b/frappe/docs/user/pt/tutorial/roles.md @@ -9,6 +9,6 @@ Para criar um novo roles, vá para: > Setup > Users > Role > New -Adding Roles +Adding Roles {next} diff --git a/frappe/docs/user/pt/tutorial/single-doctypes.md b/frappe/docs/user/pt/tutorial/single-doctypes.md index 3d1f869083..c21115244e 100755 --- a/frappe/docs/user/pt/tutorial/single-doctypes.md +++ b/frappe/docs/user/pt/tutorial/single-doctypes.md @@ -4,6 +4,6 @@ A aplicação irá normalmente têm uma página de configurações. Em nossa apl Para criar um DocType Single, marque a propriedade **Is Single** como verdadeira. -Single Doctypes +Single Doctypes {next} diff --git a/frappe/docs/user/pt/tutorial/start.md b/frappe/docs/user/pt/tutorial/start.md index da3a81b6b7..c4ed5e5f3c 100755 --- a/frappe/docs/user/pt/tutorial/start.md +++ b/frappe/docs/user/pt/tutorial/start.md @@ -14,7 +14,7 @@ Para iniciar o servidor de desenvolvimento, digite `bench start` Agora você pode abrir o seu navegador e ir para `http://localhost:8000`. Você deve ver esta página de login, se tudo correu bem: -Login Screen +Login Screen Agora logue com : @@ -24,7 +24,7 @@ Senha : **Use a senha que foi criada durante a instalação** Quando voce logar, voce deverá ver o "Desk" da pagine home -Desk +Desk Como você pode ver, o básico do sistema Frappe vem com vários aplicativos pré-carregados como coisas a fazer, o Gerenciador de arquivos etc. Esses aplicativos podem ser integrados no fluxo de trabalho do app à medida que progredimos. diff --git a/frappe/docs/user/pt/tutorial/users-and-records.md b/frappe/docs/user/pt/tutorial/users-and-records.md index 8eb1052f3d..878253bf0b 100755 --- a/frappe/docs/user/pt/tutorial/users-and-records.md +++ b/frappe/docs/user/pt/tutorial/users-and-records.md @@ -12,7 +12,7 @@ Crie um novo usuário e definá o nome, o primeiro nome e uma nova senha. Também de as roles de Librarian e Library Member para este usuario -Add User Roles +Add User Roles Agora saia e se autentique usando o novo ID de usuário e senha. @@ -20,36 +20,36 @@ Agora saia e se autentique usando o novo ID de usuário e senha. Você vai ver agora um ícone para o módulo de Library Management. Clique nesse ícone e você verá a página do modelo: -Library Management Module +Library Management Module Aqui você pode ver os doctypes que criamos para a aplicação. Vamos começar a criar alguns registros. Primeiro, vamos criar um novo artigo: -New Article +New Article Aqui você vai ver que o DocType que você tinha criado foi processado como um formulário. As validações e outras regras também serão aplicadas conforme projetado. Vamos preencher um artigo. -New Article +New Article Você também pode adicionar uma imagem. -Attach Image +Attach Image Agora vamos criar um novo membro: -New Library Member +New Library Member Depois disso, vamos criar um novo registro de membership para o membro. Aqui se você se lembra, nós tinhamos definido os valores do primeiro e do ultimo nome do membro para ser diretamente obtido a partir dos registros de membros e, logo que você selecionar o ID de membro, os nomes serão atualizados. -New Library Membership +New Library Membership Como você pode ver que a data é formatada como ano-mês-dia, que é um formato de sistema. Para definir/mudar a data, hora e número de formatos, acesse > Setup > Settings > System Settings -System Settings +System Settings {next} diff --git a/frappe/docs/user/pt/tutorial/web-views.md b/frappe/docs/user/pt/tutorial/web-views.md index 8547ec7204..de7d5b93c9 100755 --- a/frappe/docs/user/pt/tutorial/web-views.md +++ b/frappe/docs/user/pt/tutorial/web-views.md @@ -16,11 +16,11 @@ Vamos dar uma olhada na standard Web Views: Se você estiver logado como usuário de teste, vá para `/article` e você deverá ver a lista de artigos: -web list +web list Clique em um artigo e você vai ver uma Web View padrão -web view +web view Agora, se você quiser fazer uma List View melhor para o artigo, crie um arquivo chamado `row_template.html` na pasta `library_management/templates/includes/list/`. Aqui está um exemplo de arquivo: @@ -46,7 +46,7 @@ Aqui, você vai ter todas as propriedades do artigo no objeto `doc`. A List View atualizada se parece com isso! -new web list +new web list #### Home Page