From a5b8ea41c096df88dd3814f3680c86dfea6f2216 Mon Sep 17 00:00:00 2001 From: pilarvargas-tecnativa Date: Mon, 16 Dec 2024 07:55:40 +0100 Subject: [PATCH] [IMP] event_sale_reservation: pre-commit stuff --- event_sale_reservation/README.rst | 129 +++++++++--------- event_sale_reservation/pyproject.toml | 3 + .../readme/{CONFIGURE.rst => CONFIGURE.md} | 1 - event_sale_reservation/readme/CONTRIBUTORS.md | 2 + .../readme/CONTRIBUTORS.rst | 3 - .../{DESCRIPTION.rst => DESCRIPTION.md} | 5 +- event_sale_reservation/readme/INSTALL.md | 5 + event_sale_reservation/readme/INSTALL.rst | 4 - event_sale_reservation/readme/ROADMAP.md | 4 + event_sale_reservation/readme/ROADMAP.rst | 3 - event_sale_reservation/readme/USAGE.md | 61 +++++++++ event_sale_reservation/readme/USAGE.rst | 58 -------- .../static/description/index.html | 78 ++++++----- 13 files changed, 188 insertions(+), 168 deletions(-) create mode 100644 event_sale_reservation/pyproject.toml rename event_sale_reservation/readme/{CONFIGURE.rst => CONFIGURE.md} (99%) create mode 100644 event_sale_reservation/readme/CONTRIBUTORS.md delete mode 100644 event_sale_reservation/readme/CONTRIBUTORS.rst rename event_sale_reservation/readme/{DESCRIPTION.rst => DESCRIPTION.md} (62%) create mode 100644 event_sale_reservation/readme/INSTALL.md delete mode 100644 event_sale_reservation/readme/INSTALL.rst create mode 100644 event_sale_reservation/readme/ROADMAP.md delete mode 100644 event_sale_reservation/readme/ROADMAP.rst create mode 100644 event_sale_reservation/readme/USAGE.md delete mode 100644 event_sale_reservation/readme/USAGE.rst diff --git a/event_sale_reservation/README.rst b/event_sale_reservation/README.rst index 3d54f2155..918e050ca 100644 --- a/event_sale_reservation/README.rst +++ b/event_sale_reservation/README.rst @@ -17,20 +17,21 @@ Sell event reservations :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html :alt: License: AGPL-3 .. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fevent-lightgray.png?logo=github - :target: https://github.com/OCA/event/tree/15.0/event_sale_reservation + :target: https://github.com/OCA/event/tree/17.0/event_sale_reservation :alt: OCA/event .. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png - :target: https://translation.odoo-community.org/projects/event-15-0/event-15-0-event_sale_reservation + :target: https://translation.odoo-community.org/projects/event-17-0/event-17-0-event_sale_reservation :alt: Translate me on Weblate .. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png - :target: https://runboat.odoo-community.org/builds?repo=OCA/event&target_branch=15.0 + :target: https://runboat.odoo-community.org/builds?repo=OCA/event&target_branch=17.0 :alt: Try me on Runboat |badge1| |badge2| |badge3| |badge4| |badge5| This module extends the functionality of event_sale to support selling -reservations of events that still don't exist and to allow you to schedule the -creation of events based on how many reservations already exist. +reservations of events that still don't exist and to allow you to +schedule the creation of events based on how many reservations already +exist. **Table of contents** @@ -42,86 +43,90 @@ Installation To install this module, you need to: -#. Install ``web_ir_actions_act_multi`` from https://github.com/OCA/web -#. Install ``web_ir_actions_act_view_reload`` from https://github.com/OCA/web +1. Install ``web_ir_actions_act_multi`` from https://github.com/OCA/web +2. Install ``web_ir_actions_act_view_reload`` from + https://github.com/OCA/web Configuration ============= - To make use of this module, a user needs these minimal permissions: -- Sales / User: Own Documents Only -- Events / User +- Sales / User: Own Documents Only +- Events / User Usage ===== To know how many reservations exist for a given event type: -#. Go to *Events > Configuration > Event Templates* and pick or create one. -#. There's a new smart button called *Reserved seats* with that count. -#. Click on it to get to the sales orders where the seats got reserved. +1. Go to *Events > Configuration > Event Templates* and pick or create + one. +2. There's a new smart button called *Reserved seats* with that count. +3. Click on it to get to the sales orders where the seats got reserved. -But that counter will be probably zero when you install, so let's see how to -increase it. +But that counter will be probably zero when you install, so let's see +how to increase it. To create an event reservation product: -#. Go to *Sales > Products > Products*. -#. Create one and set *Product Type* to *Event Reservation*. -#. Select one *Event type for reservations*. -#. Save. +1. Go to *Sales > Products > Products*. +2. Create one and set *Product Type* to *Event Reservation*. +3. Select one *Event type for reservations*. +4. Save. -From now on, you can sell event reservations for that event type. To do it: +From now on, you can sell event reservations for that event type. To do +it: -#. Go to *Sales > Orders > Quotations*. -#. Create one. -#. Set its basic info (customer, date...) and go to *Order lines* tab. -#. Click *Add a product*. -#. Select the event reservation product you created above. -#. Set its info (quantity, price...). -#. Save that line and the quotation. +1. Go to *Sales > Orders > Quotations*. +2. Create one. +3. Set its basic info (customer, date...) and go to *Order lines* tab. +4. Click *Add a product*. +5. Select the event reservation product you created above. +6. Set its info (quantity, price...). +7. Save that line and the quotation. -At this point, the reservation is not yet confirmed, so if you go to the event -type, the smart button will still count zero. +At this point, the reservation is not yet confirmed, so if you go to the +event type, the smart button will still count zero. To confirm those reservations: -#. Go to the quotation you just created (if you are not there yet). -#. Click on *Confirm*. +1. Go to the quotation you just created (if you are not there yet). +2. Click on *Confirm*. -Now, if you go to the event type form, the smart button will indicate how many -reserved seats exist. +Now, if you go to the event type form, the smart button will indicate +how many reserved seats exist. If you want to convert those reservations into real event registrations: -#. Go to the quotation you just created (if you are not there yet). -#. Click on *Register in event*. -#. In the wizard you see, set the *Event* and *Event Ticket* for all the order - lines you want to convert into registrations. -#. If there is any line you still don't want to convert, remove it from the - wizard. -#. Click on *Next*. -#. A new wizard will appear, where you will be able to specify the name, email - and phone of each one of the attendees. If you don't do it, they will get - that info from the sales order customer. -#. After that's done, click on *Apply*. - -At this point, the sales order lines will be modified to include the ticket -product instead of the reservation product, and the event reservations have -been created, linked to those lines. - -If the event is set to autoconfirmation, the registrations are confirmed., otherwise, they are -kept as draft until an invoice is created for the sales order, and paid. But -that is just upstream ``event_sale`` module in action. +1. Go to the quotation you just created (if you are not there yet). +2. Click on *Register in event*. +3. In the wizard you see, set the *Event* and *Event Ticket* for all the + order lines you want to convert into registrations. +4. If there is any line you still don't want to convert, remove it from + the wizard. +5. Click on *Next*. +6. A new wizard will appear, where you will be able to specify the name, + email and phone of each one of the attendees. If you don't do it, + they will get that info from the sales order customer. +7. After that's done, click on *Apply*. + +At this point, the sales order lines will be modified to include the +ticket product instead of the reservation product, and the event +reservations have been created, linked to those lines. + +If the event is set to autoconfirmation, the registrations are +confirmed., otherwise, they are kept as draft until an invoice is +created for the sales order, and paid. But that is just upstream +``event_sale`` module in action. Known issues / Roadmap ====================== -Some addons (event_registration_multi_qty + event_sale_registration_multi_qty) -makes totals wrong because they depend currently on count and not sum of qtys; -integrating with them would require a glue module. +Some addons (event_registration_multi_qty + +event_sale_registration_multi_qty) makes totals wrong because they +depend currently on count and not sum of qtys; integrating with them +would require a glue module. Bug Tracker =========== @@ -129,7 +134,7 @@ Bug Tracker Bugs are tracked on `GitHub Issues `_. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed -`feedback `_. +`feedback `_. Do not contact contributors directly about support or help with technical issues. @@ -137,19 +142,19 @@ Credits ======= Authors -~~~~~~~ +------- * Tecnativa Contributors -~~~~~~~~~~~~ +------------ -* `Tecnativa `_: +- `Tecnativa `__: - * Jairo Llopis + - Jairo Llopis Maintainers -~~~~~~~~~~~ +----------- This module is maintained by the OCA. @@ -169,6 +174,6 @@ Current `maintainer `__: |maintainer-Yajo| -This module is part of the `OCA/event `_ project on GitHub. +This module is part of the `OCA/event `_ project on GitHub. You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute. diff --git a/event_sale_reservation/pyproject.toml b/event_sale_reservation/pyproject.toml new file mode 100644 index 000000000..4231d0ccc --- /dev/null +++ b/event_sale_reservation/pyproject.toml @@ -0,0 +1,3 @@ +[build-system] +requires = ["whool"] +build-backend = "whool.buildapi" diff --git a/event_sale_reservation/readme/CONFIGURE.rst b/event_sale_reservation/readme/CONFIGURE.md similarity index 99% rename from event_sale_reservation/readme/CONFIGURE.rst rename to event_sale_reservation/readme/CONFIGURE.md index e6f8effa4..3e1ff454b 100644 --- a/event_sale_reservation/readme/CONFIGURE.rst +++ b/event_sale_reservation/readme/CONFIGURE.md @@ -1,4 +1,3 @@ - To make use of this module, a user needs these minimal permissions: - Sales / User: Own Documents Only diff --git a/event_sale_reservation/readme/CONTRIBUTORS.md b/event_sale_reservation/readme/CONTRIBUTORS.md new file mode 100644 index 000000000..0ca814b0e --- /dev/null +++ b/event_sale_reservation/readme/CONTRIBUTORS.md @@ -0,0 +1,2 @@ +- [Tecnativa](https://www.tecnativa.com): + - Jairo Llopis diff --git a/event_sale_reservation/readme/CONTRIBUTORS.rst b/event_sale_reservation/readme/CONTRIBUTORS.rst deleted file mode 100644 index 8c4d96846..000000000 --- a/event_sale_reservation/readme/CONTRIBUTORS.rst +++ /dev/null @@ -1,3 +0,0 @@ -* `Tecnativa `_: - - * Jairo Llopis diff --git a/event_sale_reservation/readme/DESCRIPTION.rst b/event_sale_reservation/readme/DESCRIPTION.md similarity index 62% rename from event_sale_reservation/readme/DESCRIPTION.rst rename to event_sale_reservation/readme/DESCRIPTION.md index 95aced0ec..529ab77f3 100644 --- a/event_sale_reservation/readme/DESCRIPTION.rst +++ b/event_sale_reservation/readme/DESCRIPTION.md @@ -1,3 +1,4 @@ This module extends the functionality of event_sale to support selling -reservations of events that still don't exist and to allow you to schedule the -creation of events based on how many reservations already exist. +reservations of events that still don't exist and to allow you to +schedule the creation of events based on how many reservations already +exist. diff --git a/event_sale_reservation/readme/INSTALL.md b/event_sale_reservation/readme/INSTALL.md new file mode 100644 index 000000000..8ddf2472a --- /dev/null +++ b/event_sale_reservation/readme/INSTALL.md @@ -0,0 +1,5 @@ +To install this module, you need to: + +1. Install `web_ir_actions_act_multi` from +2. Install `web_ir_actions_act_view_reload` from + diff --git a/event_sale_reservation/readme/INSTALL.rst b/event_sale_reservation/readme/INSTALL.rst deleted file mode 100644 index 8870fa25c..000000000 --- a/event_sale_reservation/readme/INSTALL.rst +++ /dev/null @@ -1,4 +0,0 @@ -To install this module, you need to: - -#. Install ``web_ir_actions_act_multi`` from https://github.com/OCA/web -#. Install ``web_ir_actions_act_view_reload`` from https://github.com/OCA/web diff --git a/event_sale_reservation/readme/ROADMAP.md b/event_sale_reservation/readme/ROADMAP.md new file mode 100644 index 000000000..21378e686 --- /dev/null +++ b/event_sale_reservation/readme/ROADMAP.md @@ -0,0 +1,4 @@ +Some addons (event_registration_multi_qty + +event_sale_registration_multi_qty) makes totals wrong because they +depend currently on count and not sum of qtys; integrating with them +would require a glue module. diff --git a/event_sale_reservation/readme/ROADMAP.rst b/event_sale_reservation/readme/ROADMAP.rst deleted file mode 100644 index 5199b37a1..000000000 --- a/event_sale_reservation/readme/ROADMAP.rst +++ /dev/null @@ -1,3 +0,0 @@ -Some addons (event_registration_multi_qty + event_sale_registration_multi_qty) -makes totals wrong because they depend currently on count and not sum of qtys; -integrating with them would require a glue module. diff --git a/event_sale_reservation/readme/USAGE.md b/event_sale_reservation/readme/USAGE.md new file mode 100644 index 000000000..0a3d7b742 --- /dev/null +++ b/event_sale_reservation/readme/USAGE.md @@ -0,0 +1,61 @@ +To know how many reservations exist for a given event type: + +1. Go to *Events \> Configuration \> Event Templates* and pick or + create one. +2. There's a new smart button called *Reserved seats* with that count. +3. Click on it to get to the sales orders where the seats got reserved. + +But that counter will be probably zero when you install, so let's see +how to increase it. + +To create an event reservation product: + +1. Go to *Sales \> Products \> Products*. +2. Create one and set *Product Type* to *Event Reservation*. +3. Select one *Event type for reservations*. +4. Save. + +From now on, you can sell event reservations for that event type. To do +it: + +1. Go to *Sales \> Orders \> Quotations*. +2. Create one. +3. Set its basic info (customer, date...) and go to *Order lines* tab. +4. Click *Add a product*. +5. Select the event reservation product you created above. +6. Set its info (quantity, price...). +7. Save that line and the quotation. + +At this point, the reservation is not yet confirmed, so if you go to the +event type, the smart button will still count zero. + +To confirm those reservations: + +1. Go to the quotation you just created (if you are not there yet). +2. Click on *Confirm*. + +Now, if you go to the event type form, the smart button will indicate +how many reserved seats exist. + +If you want to convert those reservations into real event registrations: + +1. Go to the quotation you just created (if you are not there yet). +2. Click on *Register in event*. +3. In the wizard you see, set the *Event* and *Event Ticket* for all + the order lines you want to convert into registrations. +4. If there is any line you still don't want to convert, remove it from + the wizard. +5. Click on *Next*. +6. A new wizard will appear, where you will be able to specify the + name, email and phone of each one of the attendees. If you don't do + it, they will get that info from the sales order customer. +7. After that's done, click on *Apply*. + +At this point, the sales order lines will be modified to include the +ticket product instead of the reservation product, and the event +reservations have been created, linked to those lines. + +If the event is set to autoconfirmation, the registrations are +confirmed., otherwise, they are kept as draft until an invoice is +created for the sales order, and paid. But that is just upstream +`event_sale` module in action. diff --git a/event_sale_reservation/readme/USAGE.rst b/event_sale_reservation/readme/USAGE.rst deleted file mode 100644 index 2185c15d5..000000000 --- a/event_sale_reservation/readme/USAGE.rst +++ /dev/null @@ -1,58 +0,0 @@ -To know how many reservations exist for a given event type: - -#. Go to *Events > Configuration > Event Templates* and pick or create one. -#. There's a new smart button called *Reserved seats* with that count. -#. Click on it to get to the sales orders where the seats got reserved. - -But that counter will be probably zero when you install, so let's see how to -increase it. - -To create an event reservation product: - -#. Go to *Sales > Products > Products*. -#. Create one and set *Product Type* to *Event Reservation*. -#. Select one *Event type for reservations*. -#. Save. - -From now on, you can sell event reservations for that event type. To do it: - -#. Go to *Sales > Orders > Quotations*. -#. Create one. -#. Set its basic info (customer, date...) and go to *Order lines* tab. -#. Click *Add a product*. -#. Select the event reservation product you created above. -#. Set its info (quantity, price...). -#. Save that line and the quotation. - -At this point, the reservation is not yet confirmed, so if you go to the event -type, the smart button will still count zero. - -To confirm those reservations: - -#. Go to the quotation you just created (if you are not there yet). -#. Click on *Confirm*. - -Now, if you go to the event type form, the smart button will indicate how many -reserved seats exist. - -If you want to convert those reservations into real event registrations: - -#. Go to the quotation you just created (if you are not there yet). -#. Click on *Register in event*. -#. In the wizard you see, set the *Event* and *Event Ticket* for all the order - lines you want to convert into registrations. -#. If there is any line you still don't want to convert, remove it from the - wizard. -#. Click on *Next*. -#. A new wizard will appear, where you will be able to specify the name, email - and phone of each one of the attendees. If you don't do it, they will get - that info from the sales order customer. -#. After that's done, click on *Apply*. - -At this point, the sales order lines will be modified to include the ticket -product instead of the reservation product, and the event reservations have -been created, linked to those lines. - -If the event is set to autoconfirmation, the registrations are confirmed., otherwise, they are -kept as draft until an invoice is created for the sales order, and paid. But -that is just upstream ``event_sale`` module in action. diff --git a/event_sale_reservation/static/description/index.html b/event_sale_reservation/static/description/index.html index c6185c806..c80307468 100644 --- a/event_sale_reservation/static/description/index.html +++ b/event_sale_reservation/static/description/index.html @@ -1,4 +1,3 @@ - @@ -9,10 +8,11 @@ /* :Author: David Goodger (goodger@python.org) -:Id: $Id: html4css1.css 8954 2022-01-20 10:10:25Z milde $ +:Id: $Id: html4css1.css 9511 2024-01-13 09:50:07Z milde $ :Copyright: This stylesheet has been placed in the public domain. Default cascading style sheet for the HTML output of Docutils. +Despite the name, some widely supported CSS2 features are used. See https://docutils.sourceforge.io/docs/howto/html-stylesheets.html for how to customize this style sheet. @@ -275,7 +275,7 @@ margin-left: 2em ; margin-right: 2em } -pre.code .ln { color: grey; } /* line numbers */ +pre.code .ln { color: gray; } /* line numbers */ pre.code, code { background-color: #eeeeee } pre.code .comment, code .comment { color: #5C6576 } pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold } @@ -301,7 +301,7 @@ span.pre { white-space: pre } -span.problematic { +span.problematic, pre.problematic { color: red } span.section-subtitle { @@ -369,10 +369,11 @@

Sell event reservations

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! source digest: sha256:7f402a5051fbd1d8c17cb2c10f60695a927d60a2db3f72db6320350077c363b4 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! --> -

Beta License: AGPL-3 OCA/event Translate me on Weblate Try me on Runboat

+

Beta License: AGPL-3 OCA/event Translate me on Weblate Try me on Runboat

This module extends the functionality of event_sale to support selling -reservations of events that still don’t exist and to allow you to schedule the -creation of events based on how many reservations already exist.

+reservations of events that still don’t exist and to allow you to +schedule the creation of events based on how many reservations already +exist.

Table of contents

@@ -409,12 +411,13 @@

Configuration

Usage

To know how many reservations exist for a given event type:

    -
  1. Go to Events > Configuration > Event Templates and pick or create one.
    2. +
  2. Go to Events > Configuration > Event Templates and pick or create +one.
  3. There’s a new smart button called Reserved seats with that count.
  4. Click on it to get to the sales orders where the seats got reserved.
-

But that counter will be probably zero when you install, so let’s see how to -increase it.

+

But that counter will be probably zero when you install, so let’s see +how to increase it.

To create an event reservation product:

  1. Go to Sales > Products > Products.
    2. @@ -422,7 +425,8 @@

    Usage

  2. Select one Event type for reservations.
  3. Save.
-

From now on, you can sell event reservations for that event type. To do it:

+

From now on, you can sell event reservations for that event type. To do +it:

  1. Go to Sales > Orders > Quotations.
  2. Create one.
    3. @@ -432,48 +436,50 @@

    Usage

  3. Set its info (quantity, price…).
  4. Save that line and the quotation.
-

At this point, the reservation is not yet confirmed, so if you go to the event -type, the smart button will still count zero.

+

At this point, the reservation is not yet confirmed, so if you go to the +event type, the smart button will still count zero.

To confirm those reservations:

  1. Go to the quotation you just created (if you are not there yet).
  2. Click on Confirm.
-

Now, if you go to the event type form, the smart button will indicate how many -reserved seats exist.

+

Now, if you go to the event type form, the smart button will indicate +how many reserved seats exist.

If you want to convert those reservations into real event registrations:

  1. Go to the quotation you just created (if you are not there yet).
  2. Click on Register in event.
    3. -
  3. In the wizard you see, set the Event and Event Ticket for all the order -lines you want to convert into registrations.
    4. -
  4. If there is any line you still don’t want to convert, remove it from the -wizard.
    5. +
  5. In the wizard you see, set the Event and Event Ticket for all the +order lines you want to convert into registrations.
    6. +
  6. If there is any line you still don’t want to convert, remove it from +the wizard.
  7. Click on Next.
    8. -
  8. A new wizard will appear, where you will be able to specify the name, email -and phone of each one of the attendees. If you don’t do it, they will get -that info from the sales order customer.
    9. +
  9. A new wizard will appear, where you will be able to specify the name, +email and phone of each one of the attendees. If you don’t do it, +they will get that info from the sales order customer.
  10. After that’s done, click on Apply.
-

At this point, the sales order lines will be modified to include the ticket -product instead of the reservation product, and the event reservations have -been created, linked to those lines.

-

If the event is set to autoconfirmation, the registrations are confirmed., otherwise, they are -kept as draft until an invoice is created for the sales order, and paid. But -that is just upstream event_sale module in action.

+

At this point, the sales order lines will be modified to include the +ticket product instead of the reservation product, and the event +reservations have been created, linked to those lines.

+

If the event is set to autoconfirmation, the registrations are +confirmed., otherwise, they are kept as draft until an invoice is +created for the sales order, and paid. But that is just upstream +event_sale module in action.

Known issues / Roadmap

-

Some addons (event_registration_multi_qty + event_sale_registration_multi_qty) -makes totals wrong because they depend currently on count and not sum of qtys; -integrating with them would require a glue module.

+

Some addons (event_registration_multi_qty + +event_sale_registration_multi_qty) makes totals wrong because they +depend currently on count and not sum of qtys; integrating with them +would require a glue module.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed -feedback.

+feedback.

Do not contact contributors directly about support or help with technical issues.

@@ -496,13 +502,15 @@

Contributors

Maintainers

This module is maintained by the OCA.

-Odoo Community Association + +Odoo Community Association +

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainer:

Yajo

-

This module is part of the OCA/event project on GitHub.

+

This module is part of the OCA/event project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.