I have a question, recently I have upgrade a project of Spartacus from version 4 to 5 and something that I saw is that Modal Service seams to be deleted from version 5, but I do not find any new service that could be used instead and also I do not find any specific upgrade documentation talking about this. Can someone let me know what is going on ? If we will not use Modal Service in any new version or if there is an alternative for it.
Thanks
Use Modal Service when upgrading to spartacus 5
Related
I am new to version controlling and managing. I am in a situation where my current application is published and users are using it.
We have a new version, which we want to submit for review but for that we need to upload new version of backend to cloud and it wont work for older version and if we wont upload newe version then it wont work for reviewer.
How to resolve this issue ? Or Better implementation suggestions. Thank you
FrontEnd:- ReactNative
Backend:- Node and Express
Query Language for API: GraphQL
Cloud: Microsoft Azure.
Dont know how to resolve this
ok. for this. you have solution. you have to create a new api with v2 and run it. same put a static value on backend and Front-End for example
APP_VERSION = 1.
Now Create an API where it we'll get version from backend. if version number or different the show a message to user that please update the application.
for example. if we have uploaded new version to backend
APP_VERSION = 1.1
and user have app with
APP_VERIOSN 1.1
then show a message that please update to latest version
I'm developing an app with IBM MobileFirst Platform and I find an issue with Worklight.js file. Worklight.js is extending Function prototype defining several methods like bind, curry, wrap and so on.
My app is built with aurelia framework an after upgrading the framework to the last version I'm facing a funky issue related to bind extension.
If I comment the bind extension in worklight.js everything seems to work like a charm (don't know why worklight implements its bind version).
Worklight.js file seems to be added to the wlapp package at build time. Is there a way I can override this file so I do not have to modify .wlapp file each time app is built?
Thanks
The direct answer to the specific question you've asked is, no, there is no way provided to override worklight.js. This is the core JavaScript code needed for the MobileFirst Platform client-side to function, and as such the user isn't given any means to modify it - it's injected into your app (i.e., into the WLAPP file) during the build process.
I'm not aware of any specific issues with Aurelia, but have certainly seen cases in the past where an app that uses two different frameworks (e.g., MobileFirst Platform / Worklight, and something else) "fight" with each other because they both want to implement extensions that are not compatible with each other - in which case, one framework or the other usually needs to change to accommodate the other.
If you are a customer with paid support, I'd suggest opening a PMR so we can get our developers to take a look at the issue.
I have the same problem with Angular. Worklight bind makes Angular controller fail to instantiate. The solution is to recover the bind function after worklight is loaded.
var bind = Function.prototype.bind;
window.wlCommonInit = function() {
Function.prototype.bind = bind;
};
Recently I added a mobile version of the site using MVC4 .mobile views. I structured the site in a very similar way to the desktop version by starting from _Layout.mobile.cshtml which pointed to the correct scripts and css designed specifically for the mobile site.
After publishing the site I checked that everything worked correctly which it did just as how it was designed. But shortly I was told that the site was broken. When checking the mobile site I noticed that the _Layout.mobile.cshtml was loaded but instead of the Index.mobile.cshtml which is sent from the Home controller, what was returned instead was the standard Index.cshtml designed for desktop. The desktop Index file was also rendered using the mobile css which caused the whole mobile site to look very messed up. On a side note, no changes occurred to the desktop version of the site.
Republishing fixed the issue, but I also noticed that sometimes it reverts back to displaying the correct views without republishing even after it broke.
I began to research the issue and what I stumbled across discussions about Display Modes not working such as this:
ASP.NET MVC 4 Mobile Display Modes Stop Working
With a NuGet solution that read as deprecated: http://www.nuget.org/packages/Microsoft.AspNet.Mvc.FixedDisplayModes
I assumed that since this discussion was from a year ago talking about early releases it should be fixed by more recent MVC4 updates. My current version was 4.0.20710.0 so I updated to 4.0.30506 using NuGet before doing anything else.
This did not solve the issue but not only that, upon inspecting I noticed the reference System.Web.MVC was still pointing towards the 4.0.20710.0 version dll file.
I am worried about adding an unnecessary fix that is labeled deprecated and was hoping that the MVC update would resolve this issue. Any suggestions?
the package in your link is the package for the pre-release Asp.Net MVC 5. Indeed, they did solve the issue you are having in the Asp.Net MVC 5 package, but it is still pre-release with Visual Studio 2013. In the additional links on the page, there is a link for the non-beta, non-RC release that still applies to Asp.Net MVC 4 (FixedDisplayModes)
first of all this is my first question and I want to follow rules, but if I made a mistake, I am apologize :) My problem is that I want scale-out my website, which using SignalR and I wanted to download SignalR.Redis from NuGet. But it says that there is nothing like this but I found some tutorials witch talking about support for Redis in form of mentioned package on NuGet. I looking on internet for the reason of missing package, but I didn´t find any information about that. Or am I doing something wrong? Can you help me, please?
SignalR Redis is not currently available. The beta for 1.1 will be coming out soon which will have the Redis scaleout package.
I have jsf webapp. I have successfully deployed it to Cloudbees using steps from http://blogs.jetbrains.com/idea/2012/12/deploy-web-apps-to-cloudbees-from-intellij-idea-12/.
The problem is that the app won't work until I change the ClickStack to web application profile. The default one is Tomcat. My change is always lost each time I deploy/update the app from IntelliJ Idea. Deploying the app from PaaS console works without problem.
Is there any setting to make the Idea plugin remember the used stack?
It appears to be a bug, reported in YouTrack, star/vote the issue to receive notifications.
Found a work around. Include a jsf implementation to the app.
Support for ClickStacks had been added to IDEA CB integration, staring from next IDEA 13 EAP, it will be possible to choose between "Basic Java Webapp (Tomcat)" and "Java EE 6 Web Profile (JBoss)" options.