I am facing this issue while saving the release template. I have added a new stage in this template, copied another stage to the new one and started editing the values. On saving the template this error is showing, please see the error message screen below.
Related
When generating a Search Report for any collection, the report status appears as "Complete". However, when i attempt to View or Export the report i am getting an error indicating "Internal error on generating report.".
I am able to 'Update' the report to regenerate the report however, the same issue occurs when i view/edit the new report.
Event logs don't show anything other than the report generation event.
I'm pretty sure that's a known bug that's fixed in one of the most recently released patches. Log a ticket with Google and they'll give you the details and should be able to give you a support script that you can run for a temporary fix until you apply the patch.
Do anyone known how to revert my mistake? it is normal don't be allowed to save this file?
this is the file that I can't save it, please see line 21
I was use the developing mode in Odoo 10 when I editing product.template.product.form file with Formview option, when I miss < in my sentence and I saved. I made this syntax mistake in line 21 field name="x_season"/> sentence. After that I trying to reedit again and again, stop servers, start server, log in, log out, etc... but when I try to save I can't. Why ????
TypeError
**Odoo Client Error
TypeError: undefined is not an object (evaluating 'field.attrs.name')
http://localhost:8080/web/static/src/js/views/list_view.js:381
If you made a mistake modifying a view in the developer mode, you only have to restart the Odoo service updating the module which generated the views you modified. I guess in your case you have to update the views of the module product. To do that, in console:
python /your-odoo-path/odoo-bin -c /your-config-file-path/.odoo.conf -d your-database-name -u product
It will restore the XML code and remove the developer mode modifications in product module view.
I'm running birt 3.7.2 using the Birt Web Viewer and have recently been encountering an error when opening my reports / changing the report parameters.
The error is as follows:
An error occurred while getting report parameters. The specified report: /$$$Transient/acfile20.rptdocument was not found. The report may have expired or may not have been generated.
It also throws a "Get page count failed." error message too. I'm sure it's related to the message above.
It's not happening on all of the different instances of BIRT that I'm using. I've checked what I think is the Transient folder and it is not generating these files, yet sometimes, if I refresh the report, it will run.
What might be causing this?
If you are using either a dynamic parameter or computed column, try disabling either. For example if there is a dynamic parameter make it static, if there is a computed column try removing it.
I receive the following message when I select an image to upload and then click "send it to the Server":
Unable to get property 'setCustomData' of undefined or null reference.
I searched for CKEditor setcustomdata but came up with nothing...
Making an assumption that you are using the CKSource Image plugin. I received this error when I used the advice from this post about setting the default open tab to the Upload tab. I moved the this.selectPage('Upload'); into the onLoad event and no longer receive the error but it doesn't default the selected tab to upload on subsequent show events.
I hope this helps or at least gives you a direction to look.
How Can I show a custom view instead of the generic error attached in cases of the database going down unexpectedly?
In applications folder there is a folder named errors. There are all error files which comes up when an error is occurred.
When database error is occured, error_db.php file is shown in browser. You can edit it or replace that with your custom file.
Hope this helps.
You should set $db_debug = FALSE; in your config database settings on your production server - you should NEVER show a raw database error message to your users, as it is a massive security risk