I installed this in VSCode, created schema, reloaded and yes, I can see a line above my YAML files, telling me it sees and know the schema.
But... it does give me neither completion, nor error messages when I type things that do not exist in the schema.
Here is the shema.
It does not show me errors even on nonsense like this:
my.yaml:
wrong: value
another_wrong: value
- hello
lala
What am I doing incorrectly? Thank you for help!
Related
I want to configurer a product on admin Magento 2.3.0 and an error comes up.
"error: error in [unknown object].fireEvent(): event name: tinymceChange error message: Cannot read property 'createRng' of undefined".
What can i do ?. Thanks in advance.
One of the possible cause of this issue, Sometimes when you create a piece of content and then save and reload it from the database you will see some random characters like  or ? are added to your content. When you see unusual characters like these in your content this is likely a character encoding issue.
One of the Possible solution which I know
Go to path: lib/web/mage/adminhtml/wysiwyg/tiny_mce/setup.js
Comment out this line: content = decodeURIComponent(content);
I hope this will help, not sure whether it works for you or not but you should try this
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 am running a feature file on Cucumber and every-time I get the same error message. No matter what feature file tags I run.
Missing Examples section for Scenario Outline at
features/support/internetonly.feature:10
(Cucumber::Core::Gherkin::ParseError)
Please help.
Thanks.
Error message speaks for itself: you have scenario outline without examples table. Either include examples table, either replace Scenario Outline: with just Scenario:.
When installing my application, users must start SQL Plus and run an SQL script. This script contains creates many tables and many PL/SQL functions and triggers etc.
At the moment some of the functions are in the wrong order in the script and so users currently see a few "trigger created with compilation errors" type messages. I believe this is because the functions/triggers rely on other functions which means they cannot compile correctly.
What I would like to do is to find out which ones are failing and what the specific compilation error was instead of the rather vague warning I get at the moment. This way I can rearrange the functions in my install script and get no more warnings!
UPDATE
I would also like the specific errors to be logged into a file. At the moment I'm using the SPOOL command to log things, so it would be great if the errors could be 'spooled' too.
You can append show errors; after creation of procedures/triggers in order to see detailed error message.
You can add show err or select * from all_errors where name='<object_name>' order by sequence after each compilation command.
I have a new fairly fresh install of Magento 1.7.0.2. I installed two custom payment method modules that are working fine. But now whenever I try to disable or enable any Payment Method or Shipping Method it gives me an error like this:
An error occurred while saving this configuration: Warning:
preg_match() expects parameter 2 to be string, array given in
/app/code/core/Mage/Adminhtml/Model/System/Config/Backend/Encrypted.php
on line 57
Do you have any idea why?
EDIT 2:
I found the problem. It was caused by a patch I applied to fix to a previous BUG. :P
EDIT:
So I disabled all custom modules and I was still getting the same error. I logged what was happening and it seems that some core modules are sending an array to be saved.
Like PayPal Express Checkout for instance. One of the config options is the Time of Day in the SFTP credentials for Settlement Report Settings. It's composed by three different drop-downs and it's sending an array to be saved!
In the Shipping Methods, UPS has a config options called Allowed Methods, and it's also sending an array!
I still don't know why it wasn't happening before and now it is. They shouldn't be encrypting everything. Any clues?
I had the same issue, its a known bug, try this around line no. 135 on code/core/mage/Adminhtml/model/config/data.php
// add this code
$backendClass=false;
if (isset($fieldConfig->backend_model)) {
$backendClass = $fieldConfig->backend_model;
} // before this
if (!$backendClass) {
$backendClass = 'core/config_data';
}
This actually is a reported bug in Magento that seems to affect encrypted config settings (passwords, API keys, etc.).
http://www.magentocommerce.com/bug-tracking/issue?issue=14217
Try disabling the first of the modules, log out of the admin panel, clear /var/cache and see if the problem still exists. If it does, do the same with the second module.
The problem should be gone. Now that you know which module causes the problems you can either decide to try another module instead or debug to see whats going wrong.
Put a breakpoint on line 57 in /app/code/core/Mage/Adminhtml/Model/System/Config/Backend/Encrypted.php to see what goes wrong. It seems that the second parameter is not a string (might be null for example due to wrong configuration or something) when its given to the preg_match function. Maybe this helps you to identify the problem.
Regards
Disabling modules through the back office isn't a good idea as it only disables the block output, if you would like to disable a module you should go to app/etc/modulesand there you should find Module_Name.xmlfile - in this file just put false in active node.