I need to use client-app-support and client-endpoint tags inside an endpoints file but I keep getting this error message: "Experimental feature, not available for external use".
Error:
As stated by the error, that feature is not available for external use.
If you think this a mistake, please file a support ticket through the IDE.
Related
i am using B2C provider for DNN and trying to install it as extension and it's throwing error https://i.stack.imgur.com/6faW1.png
i am trying to use multiple version as well but not installed properly and using source from https://github.com/intelequia/dnn.azureadb2cprovider/releases
Please help me out.
There was an issue in the DNN manifest file that has been solved on v1.4.7 (release https://github.com/intelequia/dnn.azureadb2cprovider/releases/tag/v1.4.7). Tracking the issue at https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
I wrote the answer below before seeing this: https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
Perhaps this is pertinent to your question. You might want to check with Ryan Moore (moorecreative" to see if he was able to resolve the issue.
First, please bear in mind that I am not familiar with this particular extension, but it seems as if it is "just another" authentication provide for DNN.
I'm also a little confused. The error message indicates that you've already installed th Intelequia AzureB2C provider. Is that true?
You also say "I am using" and then "trying to install it as an extension." If you are using it, that means that it is already installed as an extension, so a second attempt to install it should throw an error. But, I would think that the installer should see that problem earlier in the process.
Finally, you say "i am trying to use multiple version as well." A provider should be installed only once, and that is what the error message is telling you.
Once you have installed an authentication provider you typically enable it for a portal, and it becomes part of the authentication process.
You should read the documentation carefully, and make sure that you are trying to use the provider as the developer intended.
I want to use some JsonPath library in browser, but they all relying on eval()/Function() that get caught with unsafe-eval by CSP. And any other workarounds/3rd party libraries like static-eval/safe-eval also all get caught with the same console error. Does anyone know of any other potential workarounds to resolve this unsafe-eval issue besides allowing the unsafe-eval csp directive?
The best thing I found was an old fork of JSONPath-Plus that attempted to create a non-eval version of the library. Here's the Pull Request, however, this was never merged (fully) because of some merge issues and performance issues.
I imagine performance would be a problem for other non-eval implementations as well, and that's why we have non, at least to my knowledge.
After installing the Channable plugin for Shopware 6 I received the following error.
Plugin could not be activated due to error message "You have requested a non-existent service "sales_channel_definition.Shopware\Core\Content\Product\ProductDefinition"
I haven't been able to find a solution for this, and Google turns up little.
I can be wrong, but if you are talking about that plugin https://store.shopware.com/en/res6026584109026f/channable-connector.html.
Looks like it is not available for Shopware 6 yet.
Seems like you have a plugin or app with a services.xml file that might cause you trouble. Try deactivating your plugins and enable them one by one.. when you have found the plugin, then look into the services.xml file in order to find the problem.
I'm very new to DevOps tools and I'm starting to learn Puppet. I found this example at this link nice to start with for my purpose : configuring an Appache server with Puppet : http://blog.akquinet.de/2011/11/23/managing-an-apache-server-with-puppet/
But when running the code presented in the article I have the following error
Error: Evaluation Error: Error while evaluating a Resource Statement, Invalid resource type apache::vhost::proxy_http at /root/kmlunch.pp:17:1 on node learning.puppetlabs.vm
Maybe it's an obvious error, but I don't know how to fix it. Can you please help?
Thanks
Simple: you are pulling a newer apache module then the one for which your document was written. In the meantime the resource apache::vhost::proxy_http has disappear. If I'm not mistaken, the proxy part was integrated in the vhost define.
Solution: use an other tutorial (a newer one).
Our Cognos 8 application has an error affecting many users:
http://img543.imageshack.us/img543/6849/aoeu.png
CM-REQ-4158
The search path ... is invalid.
We know how to fix this problem (it's a browser configuration issue) but the error message is not helpful. Also, users will get this issue if they upgrade IE.
SO
Is it possible for us to modify this error message so it is more useful?
I believe the only way you'll be able to hone in on those messages is to use the Language Development Kit (LDK).. I'm sure you can edit them by hand, but I don't think it's worth it.