-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[17.0][MIG] delivery_correos_express: Migration to 17.0 #906
base: 17.0
Are you sure you want to change the base?
[17.0][MIG] delivery_correos_express: Migration to 17.0 #906
Conversation
9f1c376
to
2b42409
Compare
27143df
to
9378e94
Compare
9378e94
to
9c7b656
Compare
9c7b656
to
70e2c17
Compare
Take into account this fix done in 15.0 migration: 19b2722#diff-fc0ee4a55021761bea7e0737694662bf7ab7b58450fa901711ec03027a5062d0R44 |
db5057a
to
ace1707
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you checked the SSL issues in test mode? Maybe we could change the test-to-prod and debug buttons to booleans so they are easier to understand.
('delivery_type', '!=', 'correos_express'), | ||
('state', '!=', 'done') | ||
]}" | ||
invisible="(carrier_tracking_ref != True) or (delivery_type != 'correos_express') or (state != 'done')" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like the button is not displaying correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
En este repositorio se puede hablar en español para facilitar la colaboración.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solucionado, era al realizar la comprobación:
delivery_carrier_ref != True
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pues seguramente varias cosas, hay que tener un número de seguimiento válido, y para eso hace falta un usuario, contraseña, codigo de cliente... que crea el envío y con ese número de seguimiento ya puedes hacer la petición, que en realidad descarga la etiqueta en .pdf y se adjunta al picking.
El entorno de pruebas no funciona, así que solamente se puede probar en producción, yo lo he hecho y funciona correctamente.
Puedes intentarlo con un número de seguimiento real.
"dato": picking.carrier_tracking_ref, | ||
} | ||
|
||
def correos_express_tracking_state_update(self, picking): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this working?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@juancarlosonate-tecnativa te refieres a la función def correos_express_tracking_state_update(self, picking)
?
ace1707
to
7169ca2
Compare
7169ca2
to
8a73c56
Compare
8a73c56
to
d18b821
Compare
Valid for Spain and Portugal
International deliveries require a different field to be used as ZIP code
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: delivery-carrier-14.0/delivery-carrier-14.0-delivery_correos_express Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-14-0/delivery-carrier-14-0-delivery_correos_express/
d18b821
to
3a837dd
Compare
Depends on: