I am using ace-editor with the angular-ui-ace directive in my angular project. I need to remove specific markers (such as 'missing !DOCTYPE) from my session. How do I do it?
See https://github.com/ajaxorg/ace/blob/v1.1.8/lib/ace/mode/html_worker.js#L40. you can set error type for errors you want to ignore to "none", or even add an api similar to https://github.com/ajaxorg/ace/blob/v1.1.8/lib/ace/mode/css_worker.js#L61 to customize disabled errors.
Related
Just upgraded to DNN EVOQ BASIC v. 09.01.01 (113) and 2sxc 9.32.1
After placing the Content module on a page, some of our templates do not have Edit options and some of them that have an Add Item option doesn't do anything after clicked.
When I click on Add Item, I get this error:
Uncaught SyntaxError: Unexpected token T in JSON at position 0
at JSON.parse (<anonymous>)
at Object.t.showDetailedHttpError (ToSic.Sxc.Instance.ts:73)
at fire (jquery.js?cdv=209:1037)
at Object.fireWith [as rejectWith] (jquery.js?cdv=209:1148)
at done (jquery.js?cdv=209:8076)
at XMLHttpRequest.callback (jquery.js?cdv=209:8598)
This sounds like a skin / container compatibility issue, the "content module" you mention, is this the core text / html module or something else?
As a test, change the page skin and or module container to one that comes with the core 9.1.1 install and retest
DC
I don't know for sure what's happening, but let me give you a bit of background. When an editor is on the page, 2sxc adds some configuration information as json in the html-attributes, which the UI the needs to know what you were clicking on etc.
To me it sound like something is breaking this - either because a server-side filter is changing the HTML (not likely, but possible), or another javascript is running which changes the DOM, resulting in removed or broken attributes.
To get this resolved, pls verify that you can find these jsons in the html-tags (they are very obvious) by looking at the html-source. If they are there and look ok, it's not the server that's breaking it.
Then check if they are still there in Chrome-Debugger (F12) which doesn't show you the source as the server sent it, but the source as the browser currently has it. I'm pretty sure it will be off somehow, because maybe a neat jQuery mangles the HTML.
Love from Switzerland,
iJungleboy
Is it possible to hide vanilla buttons (in my case crm save button), according to Javascript function or field change in Dynamics - Crm 2016 using workbench? If it's optional where can I had the connection to my display rule?
You need to add a ribbon display rule.
Control when ribbon elements are displayed
By defining display rules in rule definitions, you can use the same
display rule for many command definitions. When more than one display
rule is defined for a command definition, all of the display rules
must evaluate as true for the ribbon element to be displayed.
This is easier using Ribbon Workbench. This article is similiar but for enable rules. In later versions of CRM disabling a button usually hides it as well.
Download the XrmToolbox: https://www.xrmtoolbox.com/
Open the Ribbon Workbench 2016
Open your ribbon
Right-click on the button you want to edit, click Customize command
Go in Solution Elements > Commands > Your command
Add a display rule
Add Step, Value Rule
If you to use javascript for a complex rule, instead add an Enable Rule and a step, CustomRule.
I installed the last version of OpenContent Module, and I add some items using catalog template, but when I try to filter the content using Filter Settings, it doesn't work. Seems that for some reason the module doesn't find the results.
Someone knows how it works or what I doing wrong?
Filter Settings
for some reason only accepts lowercase values and no symbols like: &, #,... try to change the "Membership" for "membership".
I have created a Banana custom panel, and I want to change dynamically its "custom query" by a system of "select" tag.
In this page, I can see that I can find a variable "_d" that contains custom. I can change it by a static variable which I give a value before launch Banana.
Far in the tutorial, is a comment "Set the additional custom query", but, I am not sure of what I have to replace by my variable (or have I not to touch it?).
I decided to look at the filtering panel, because, in fact, it is what I want to do (filtering). But I don’t understand how does the module works (where does he stock its filters? and how does it apply them?).
I looked at the filterSrv.js, but I am not sure it do something on filtering/module.js (apart from giving function to filtering/module.js and filtering/module.html).
Do you know something about it?
To set the custom query, you have to set $scope.panel.queries.custom in module.js. This file src/app/partials/querySelect.html is responsible for the Queries tab in each panel's config, where you add custom queries through UI.
I've recently started working with an application written using Adobe Flex 3. We're using several deprecated functions and unfortunately we can't remove these dependencies.
The documentation says to set -show-deprecated-warnings=false into the Compiler Additional Options. This isn't accepted, but I've found that using -show-deprecation-warnings=false will be accepted by the dialog, but gives an error about declaring the option twice when I try to compile the project.
Ideally, I'd like a way to disable the warning on a case-by-case basis. Failing that, can anyone help me to disable the warnings either per-file, per-project or globally?
As an update for recent versions, I added a compiler option in FlashDevelop:
-show-deprecation-warnings=false
This worked for me.
This link suggests that it doesn't work properly anyway, and the only real answer is to turn off warnings altogether.
Adobe Jira 13569
You can turn off warnings by using a custom flex-config.xml file for each project / globally. Just point the compiler at the right file.
I've found a partial workaround: filter the warnings from the 'Problems' tab. This doesn't get rid of the next-to-the-source warning markers, but it's the Problems tab which I'd like to be clean.
Click the filters button on the Problems tab, change 'Description' to 'doesn't contain' with text 'deprecated' and hit OK.