SAPUI5 Annotation structure cannot read property 'IndexOf' undefined - annotations

I've created a local annotation file based on an OData service.
And even without adding any annotations to the new annotation file, when I open Annotation modeler it says
Annotation structure cannot read property 'IndexOf' undefined
And I have not defined any annotations from the service level.
And Even I add some annotaions using the Code view they also not display when I run the application
When I check the console it displays following error
2018-08-09 12:18:45.755000 TypeError: Cannot read property 'indexOf' of undefined
at Object.getAbsolutePath (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/plugins/pluginrepository/annotationmodeler/client/v1.33.1_1526463231420/config-preload.js:1:136)
at Object.<anonymous> (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/plugins/pluginrepository/annotationmodeler/client/v1.33.1_1526463231420/config-preload.js:9:17064)
at r (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:43:4628)
at r._settlePromiseFromHandler (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:42:23011)
at r._settlePromise (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:42:23814)
at r._settlePromise0 (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:42:24515)
at r._settlePromises (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:42:25845)
at r._drainQueue (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:41:12469)
at r._drainQueues (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:41:12530)
at drainQueues (https://webide-hf01c42be.dispatcher.us3.hana.ondemand.com/resources/~3502d451b8b72165ef3cf2fa0789ca9b3430f76e~/sap/watt/core/Core-preload.js:41:10559) -

Related

Can I use FLP without default model ?

My json model url is '/destinations/XXX/Collection?time=' + (+new Date) I don't know how to configure it in minifest of Component.js , so I delete the sap.app.dataSources and sap.ui.models."" (the defalut model? ) , and the flp app gave me this error:
Failed to load U5 component for navigation intent
TypeError: Cannot read property 'metadataLoaded' of undefined
sap.ushell.renderers.fiori2.Shell.controller
What should I do ?
i have a couple of links that should get you up and running (I am assuming you are developping on webIDE in SAP HCP (is that correct?)):
How to setup destinations, you need extra properties: WebIDEUsage = odata_gen and WebIDEEnabled = true.
You should then go into your manifest.json and choose Descriptor Editor and choose Data Sources and under OData Services choose the + to add your service.
More information on manifest.json you can find here: Documentation on Manifest

Call to a member function get_cart_subtotal() on a non-object in config-woocommerce/config.php on line 790

I'm trying to login into my WordPress Admin panel, and am getting the following error:
Call to a member function get_cart_subtotal() on a non-object in /home/spicom/public_html/adwinang.com/wp-content/themes/enfold/config-woocommerce/config.php on line 790
This is my code at line 790:
$cart_subtotal = $woocommerce->cart->get_cart_subtotal();
It sounds like you haven't called global $woocommerce;, before trying to access the $woocommerce object.
A better way would be to use WC():
$cart_subtotal = WC()->cart->get_cart_subtotal();
Alternatively, it's possible the WooCommerce hasn't even been installed and activated...make sure to do that, if it's a theme dependency.
I had a very similar message.
[25-Sep-2018 10:24:08 UTC] PHP Fatal error: Uncaught Error:
Call to a member function get_cart_subtotal() on null in
themes\storefront\inc\woocommerce\storefront-woocommerce-template-functions.php:80
It was due to me having the following in my wp-config.php file.
define( 'DOING_CRON', false );
I'd added this line while attempting to run something from the command line with W3 Total Cache activated. I didn't realise that it would completely ruin WooCommerce and didn't notice the side effect until attempting to view the site in my browser.

Meteor error in trying to use collections

I am currently pulling data from collections in the MongoDB but there are 2 in particular that will not work either giving me the following error:
Exception from sub Assets id i574gxNDc9RdHERNn TypeError: Cannot call method 'find' of undefined
Or:
TypeError: Cannot call method 'attachSchema' of undefined
Or:
Object # has no method 'attachSchema'
depending on how I configure it. Does anyone have an idea of what I am doing wrong. I am using the same code for the ones that work as well as the ones that are throwing errors.
The collection looks like this:
Assets = Collections.Assets = Meteor.Assets;
Querying in server/publish.js:
Meteor.publish("Assets", function (){
return Meteor.Assets.find({});
});
Changing it to:
new Mongo.Collection('Assets');
Gives error:
Exception from sub Assets id ZgzZyNYPmMr5gtFGn TypeError: Cannot call method 'find' of undefined
Running the following from the command line in the top (root) directory of the project might fix this (it helped me):
meteor add aldeed:collection2

Dynamic ZK Chart Type & Model: Unsupported model type Error

I'm creating a dashboard application which requires me to allow user to change the chart type to any other available chart type and reload the org.zkoss.chart.Charts .
Charts charts = (Charts) dashboardBuilderCanvas.getFellow(chartsId);
I can get the Charts, but when I want to change the type or the model from Column chart to Pie Chart:
charts.setType(Charts.PIE);
I get the following error:
Unsupported model type [org.zkoss.chart.model.DefaultCategoryModel#5665ad96] on that line.
I tried to do this:
PieModel model = new
DefaultPieModel();
charts.setModel(model);
charts.setType(Charts.PIE);
But I get the same error:
java.lang.IllegalArgumentException: Unsupported model type [org.zkoss.chart.model.DefaultCategoryModel#5e92429a]
at org.zkoss.chart.impl.PiePlotImpl.drawPlot(PiePlotImpl.java:33)
at org.zkoss.chart.Charts.doSmartDraw(Charts.java:2197)
at org.zkoss.chart.Charts.smartDrawChart(Charts.java:1702)
at org.zkoss.chart.Charts.setType(Charts.java:662)
How can I resolve this?
Thanks.
Call setType before setModel
PieModel model = new DefaultPieModel();
charts.setType(Charts.PIE);
charts.setModel(model);

sails.js : using dust in sails 0.10.5

I am trying to migrate a project from 0.9.9 to 0.10.5
We were using dust templating engine in our porject instead of the default ejs engine.
Contents of config/views.js file
module.exports.views = {
engine: 'dust',
layout: 'layout'
};
In my controller, I was able to render this view like this
res.view('layout', obj);
However, in sails 0.10.5, when I lift sails, first of all I get this warning
warn: Sails' built-in layout support only works with the `ejs` view engine.
warn: You're using `dust`.
warn: Ignoring `sails.config.views.layout`...
And then when I try to render the view as I was doing earlier, I get following error:
error: Sending 500 ("Server Error") response:
Error: ENOENT, open '/.dust'
{ [Error: ENOENT, open '/.dust'] errno: 34, code: 'ENOENT', path: '/.dust' }
Any idea what is the correct way of doing this in 0.10.5 ?
The layout property does not apply to dust (just ejs). Set layout to false to get the warning to go away. You want to use Dust's built-in support for partials and blocks anyways.
Using res.view('layout', obj); means that you expect a file called views/layout.dust to exist. Prior to 0.10, sails was including the layout property from config/views.js as part of the path.
So my best guess is that your res.view() call is actually being invoked with an empty string as the first parameter, and it wasn't breaking because you were trying to render something called layout. I'd check your invocation to make sure that you're calling res.view() with an instantiated variable.