On Tue, May 26, 2015 at 5:17 PM, Nadeesha Meegoda <[email protected]> wrote:
> Hi Udara, > > When it's changed to a different type, gadgets will not be shown as the > landing page. > > My scenario is when the "gadget" is the landing page and it's later on > added to the disabled assets list, what should happen? Is it correct to > display the disabled gadgets as the landing page where all the published > gadgets are shown and life cycle exposed? or does the configuring person > need to take the responsibility in handling these conflicts while > configuring the app.js? I thought it would throw an exception at least. > IMO both arguments are correct and we can clearly document this scenario and avoid this configuration issue. I think it's not possible to browse an asset/listing page using the URL( https://localhost:9443/publisher/asts/ebook/list) If that asset type is under the disabled list. > > Thanks > > On Tue, May 26, 2015 at 5:02 PM, Udara Rathnayake <[email protected]> wrote: > >> Hi, >> >> What happen if you change the landing page to a different type? Are you >> still see the gadgets tab within the menu? >> >> I think what we have tried here is to remove the "asset type name" from >> the top menu and there is no valid reason to have Gadget within the >> disabled asset list as well as within the landing page. >> >> Regards, >> UdaraR >> >> On Tue, May 26, 2015 at 4:49 PM, Nadeesha Meegoda <[email protected]> >> wrote: >> >>> Hi, >>> >>> I followed the following steps for setting up an asset type for the >>> landing page and disabling the asset type. >>> >>> 1. Set "Gadget" as the landing page of ES Back-Office via >>> repository\deployment\server\jaggeryapps\publisher\extensions\app\publisher-common\app.js >>> >>> 2.Add "Gadget" to the Disabled Assets via the same. >>> >>> 3. Login to the store Back Office -> Gadgets are still shown as the >>> landing page though it's disabled. >>> >>> >>> It would be great if anyone can let me know whether we need to handle >>> this in a proper manner or is this the expected behavior in such a case? >>> >>> >>> Thanks & Regards, >>> Nadeesha >>> -- >>> *Nadeesha Meegoda* >>> Software Engineer - QA >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> email : [email protected] >>> mobile: +94783639540 >>> <%2B94%2077%202273555> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > *Nadeesha Meegoda* > Software Engineer - QA > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > email : [email protected] > mobile: +94783639540 > <%2B94%2077%202273555> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
