Ir al contenido
Menú
Se marcó esta pregunta
2 Respuestas
477 Vistas

Hi all, 

Pre-facing this query with I am sadly not a developer/programmer, but I am somewhat tech literate and can perform a bit of studio modifications. 


Details: 

  • Odoo Documentation and Cybrosys docs. I may not be an expert on this, but it seemed relatively simple to do. Drag and drop the Staging branch to Production.
    • From my understanding, it will just transfer some of the configuration and leave the records alone, so I would not lose any recorded data. 
  • When I do this, an error appears: "Whoops! It seems we need additional authorization from GitHub to perform this action. You will be able to retry the action after the redirection." (Error 1). I then click on "Authorize on Github".  
  • It basically reloads the page. 
  • I try to merge the branches again (Staging into Production). This time an error shows as "Ah, well... Not Found" (Error 2).

My query is:

  1. Why are these errors occurring? 
  2. Have I misunderstood the process/am doing this incorrectly? 


Im happy to answer any follow up questions if it helps for clarity - and I apologize in advance if my query is lacking. 


Any guidance is much appreciated. 

Avatar
Descartar

It will only copy the code changes made in the GitHub development branch:

"Merging a staging branch in the production branch only merges the source code: Any configuration changes you made in the staging databases are not passed to the production database."

I am also not a programmer, but individual changes can also be applied directly from GitHub and that may be safer. What changes did you make?

Autor

Hi Chris, 


Thank you for confirming that. 


I created a few fields in Studio (i.e. not via the shell/editor), and created a few report templates. 


No other changes were made. 

Autor

Thanks Chris, much appreciated. 


Apologies, but I do not know how to mark this as solved...

I converted my comment to an answer, maybe someone can mark it as "Best Answer"

Mejor respuesta

Since this ultimately turned out to be about transferring Studio-based customization:

You can actually get Studio customization from one database to another in Odoo 18.

Enable the Developer Mode (https://www.odoo.com/documentation/18.0/applications/general/developer_mode.html), then navigate to Settings -> Technical -> Studio Export. You will most likely see an empty list here. From here you can Export all your current Studio customization:


Once this is done, a customizations.zip will be downloaded. This .zip then can be uploaded in another database by navigating to Apps -> Import Modules (again, with enabled Developer Mode):


Please note that the module downloaded will always have the (technical) name studio_customization - hence, you may not merge Studio customization from multiple databases by just downloading individual Studio exports as any new one should override the previous one.

Avatar
Descartar

Hi Christoph - have you ever got this to work? I normally get errors importing!

I'm avoiding Studio like the plague since it's highly annoying to debug and badly compatible with source-based extensions. I.e customer tells me they've 'just added another field that now needs to do x' - now 'x' needs to happen in a module making that module depend on studio or having you redefine it in a model anyways. Therefore, I've never used that approach on a bigger scale or with other customization. In that reduced scenario however it did work for me, yes.

So, yes, while I did not experience 'oh snap' messages on import, I actually wouldn't wonder if this is the case with rather complex implementations...

Mejor respuesta

Studio changes and report templates can't be moved in that way. It's one of the frustrations with Studio that you have to manually re-apply changes in Production.

Avatar
Descartar
Publicaciones relacionadas Respuestas Vistas Actividad
1
jun 24
1488
0
may 24
1278
1
dic 23
2283
0
ago 25
267
4
may 25
2784