I have used adapter, authentication, server everything of MFP. But now I am stuck in Direct Update. If I am pushing mfpdev app webupdate direct update default dialog is coming and I can update application.
But issue is coming while I am trying to make a custom dialog for getting the update. I never got the custom dialog. The codes I have used is:\
wl_directUpdateChallengeHandler.handleDirectUpdate = ((directUpdateData, directUpdateContext) => {
WL.SimpleDialog.show('Update Avalible', 'Press update button to download version 2.0', [{
text: 'update',
handler: () => {
directUpdateContext.start();
}
}]);
});
I cant find the wl_directUpdateChallengeHandler in worklight.d.ts file either. Seeming like in ionic2 we don't have a option for custom direct update dialog. Am I right?
The version I am using is Mobilefirst V8.0.0 and Ionic2
Please help me if anyone have any better understanding on this.
Related
Setup
I'm using GitHub Pages to host my website statically. To generate SEO data I'm using the native head() method supported by the Nuxt framework. Here is a sample of my setup.
export default {
head() {
return meta({
title: 'Page title here',
description: "Page description here",
image: this.image, // programmatic image
})
}
}
Issue
As expected with a single page application, the metadata is being rendered into the DOM as the page is loaded. The initial data in the HTML comes from the nuxt.config.js, information designated for my homepage. This is causing an issue that when any page gets scraped they all have the same metadata.
Goal
Is it possible to render each page's metadata in their respective HTML files when running nuxt generate? This way the appropriate metadata is available when Google, Facebook, Instagram, and other platforms scrape metadata.
With some help from #kissu, the issue was caused by the fact that in my nuxt.config.js I had the Server Side Rendering turned off with the following property being st ssr: false when it should have been ssr: true. There were subsequent issues with Node JS that needed to be resolved along the way.
You need to use ssr: true if you need some SEO, otherwise it will only stay as an SPA.
target can be either server (default) or static.
I'd like to add a button that opens a link in the tasklist navigation bar:
I read the documentation and it's clear that I have to add a plugin to the tasklist app but I can't figure out how to do it based on the given example.
Any hints, please? Thanks!
I found the Camunda docs very un-helpful. Consequently, I decided to find existing plugins to better understand what is needed. Luckily, I stumbled upon a sample project called tasklist-plugin-easy-search.
I cloned this project and used it as a base.
Within your newly cloned project , make sure that the class name in
/code-master/snippets/tasklist-plugin-easy-search/src/main/java/com/camunda/demo/plugin/tasklist/search/easy/EasySearchPlugin
is referenced in a file called org.camunda.bpm.tasklist.plugin.spi.TasklistPlugin that resides in the directory
META-INF/services.
There are a limited number of locations on the Tasklist webpage whereby you can place your plugin.
Please have a look here.
Once selected you can change the code in /code-master/snippets/tasklist-plugin-easy-search/src/main/resources/plugin-webapp/easy-search-plugin/app/plugin.js
var Configuration = ['ViewsProvider', function (ViewsProvider) {
ViewsProvider.registerDefaultView('tasklist.navbar.action', {
id: 'claim-interface-plugin',
label: 'Search',
url: 'plugin://claim-interface-plugin/static/app/claim-interface-plugin.html',
controller: Controller,
priority: 1000
});
}];
Finally, to integrate this plugin into you Camunda web app, you should create a Jar file. Next, shut down your Camunda web app if it is running.
Thereafter, go into your Camunda web app directory and place the Jar in
/server/apache-tomcat-8.0.24/webapps/camunda/WEB-INF/lib/.
Start up your Camunda web app.
In my applicaiton, I requried couple of things to be added.
No forward/Back Browser button should work for reach a hash.
Instead of brower back forward, there should be a back and forward button has to added in the applicaiton itself.
how to achive this both?
I am looking for a component to use globally for both 2 requriements.
Thanks in advance.
Disabling the native back/forward buttons of the browser in Ember.js is quite unusual but could possibly be achieved by using the NoneLocation class. To enable that open the config/environment.js file of your app and change the locationType property to none.
If you want to display back/forward buttons in your app you can use the History API and specifically window.history.back() and window.history.forward()
Since in mobile app there is no click and there is a touchEnd event how i can use it easly with ember.js ?
I know i can create a Ember.View with
events:
touchEnd: ->
console.log('my action')
I'm just searching for some more convenient way since creating a view for simple link in list is not the fastest way ;)
There is a touch gesture addon for ember called ember-touch. You can find it in https://github.com/emberjs-addons/ember-touch.
I hope it helps
I am writing an page inside Sitecore where users can create Sitecore items by entering some very basic information. One of the requirements is to the Sitecore RTE inside this form. The RTE should have all the command buttons available and working like linking to 'Media Library', 'Flash', 'Items', etc that come as defaults.
The control is working fine but I can't get any of the Sitecore commands to work. I get a -
Web.config registration missing! The Telerik dialogs require a
HttpHandler registration in the web.config file. Please, use the
control's Smart Tag to add the handler automatically, or see the help
for more information: Controls > RadEditor > Dialogs > Introduction.
I have checked all the Telerik settings and the handler is registered. I am not sure what else I can do to resolve this.
This is very crucial for the client. Also, if there are any alternatives you can suggest would be awesome.
Thanks
You can try the suggestions provided in the following help article: http://www.telerik.com/support/kb/aspnet-ajax/editor/error-web-config-registration-missing-the-telerik-dialogs-require-a-httphandler-registration-in-the-web-config-file.aspx