Can anyone explain the use of the Morpheus portal and skin in Sakai? What I mean to ask is, how do I enable those things and what are the differences to the neo skin and neo portal code in Sakai?
Thanks in advance.
Morpheus (Mobile Optimized Responsive Portal for Higher Education Using Sass) is the new responsive design portal (the primary UI) which will be available in Sakai 11 (and is in a preview state for Sakai 10). The neo portal is the portal which was developed and released for Sakai 2.9. Before that the portal was known as the Charon portal.
If you want to test it you should really be using Sakai trunk (instead of 10.x). Either way, the following setting needs to be enabled in your sakai config file (typically sakai.properties). Make sure you check that they are not duplicated in the file.
portal.templates=morpheus
portal.neoprefix=
skin.default=morpheus-default
Also, if that doesn't work then check to make sure the morpheus dirs exist in the reference/library/src/webapp/skin directory. If they don't then you need to update to a newer version of the code.
Morpheus is the new responsive design portal (the primary UI) which will be available in Sakai 11 (and is in a preview state for Sakai 10). The neo portal is the portal which was developed and released for Sakai 2.9. Before that the portal was known as the Charon portal.
MORPHEUS=Mobile Optimized Responsive Portal for Higher Education Using Sass
Here were some slides
http://www.slideshare.net/alienresident/sakai-meet-morpheus-slides
And a presentation on this topic from Apereo 2014
https://www.youtube.com/watch?v=BQyGgwUPeqU
Related
In part to help explain or understand "what components build on which others" in Azure, or show others the time and evolution of thinking as products were released (console vs portal for example), is there a list of when products were released to the public?
I checked Wikipedia for this and found no historical data, (hoping it would be in table form by date/status/release/LTS)
I think the closest would be the RSS feed from https://azure.microsoft.com/en-us/updates/
It includes updates about features going to Preview and General Availability.
You could also try with the Wayback Machine on the Products available by region page.
Here is a version from 2018. The page changed into a search type page so you'll need to try see if archive.org has versions of the region specific pages.
Products available by region gives you a NOW-only view with the following key:
Generally Available
In Preview
In Preview (hover to view expected timeframe)
Future availability (hover to view expected timeframe)
I am facing problems with interface customizations in the latest OBIEE release.
Is it possible to "hide" the Mobile, VA and BiPublisher options - marked red in the appendix.
(Privileges in Administration and roles in EM are configured - users can not access Mobile, BiPub however the buttons are still visible - OBI 11 did not display them afterwards...)
I am looking for a "clean" design.
Any help is much appreciated
Unfortunately up to and including 12.2.1.2 (the current version) the "Visual Analyzer" menu point will keep being rendered even if they permission has been removed from the application role(s) of the user.
Mobile and BIP disappear completely on the other hand.
So the question to be asked is: how did you configure your application roles and policies? Did you reuse vanilla ones? Then it may just be the case that some rights still persist due to ootb inheritance between roles and hence some rights stay even though you think you removed them.
This isn't much of a programming question, but I figure some here would know the answer.
I'm trying to setup the Suitecloud IDE, but you have to enable Web Services. Does it cost anything to do so? Our consultant keeps telling us that we have to buy another account to do so, whereas the Netsuite Tech Support seemed to indicate that it is free.
I'm just wondering what the cost is.
No it is free.
Go to Setup > Enable Features > Suitecloud (tab) > Web Services (check box).
You have to give roles (or global permissions to users) permission to use Web Services.
You can get the IDE from the help section. Search SuiteCloud IDE and it will come up.
SuiteCloud (Customization, Scripting, and Web Services) > SuiteCloud IDE > SuiteCloud IDE Overview
As far as I know, your consultant is wrong or at least isn't being clear.
Enabling Web Services(SuiteTalk) doesn't change your licensing costs at all.
When you connect to NetSuite using web services, you do so using a user account. So in that way, each IDE user would need a license. In most situations however, if the developers already have access to the NetSuite UI, and are therefore consuming a license, it works fine to have them connect with the IDE using the same credentials and thus the same account. That's what we do anyway.
What's more, you could probably (technically; if not necessarily within the letter of the license agreement) share a single license across all the IDE users. You would lose all audit control over who made what changes and you could conceivably run into conflicts with multiple users trying to interact with the account at the same time.
Bottom line: SuiteTalk doesn't cost extra to turn on. Anyone with a normal Netsuite user login can use the IDE at no extra cost.
Does anyone here know what could cause a new feature to not show up in the SharePoint UI?
The solution it is part of has been correctly deployed to the GAC and shows up in the central administration list of deployed farm solutions, the feature appears in the FEATURES folder of the 14 hive, yet the feature itself does not appear in the features list for the site collection, either in the UI or in PowerShell using Get-SPFeature.
Yes, the feature is correctly scoped, and no, it is not hidden. :)
Any thoughts or pointers would be very welcome!
Answer supplied on sharepoint.stackexchange.com, with thanks to Simon Doy. https://sharepoint.stackexchange.com/questions/73871/sharepoint-2010-feature-not-appearing-in-ui
Somehow, something had gone wrong with the installation of the feature, and neither the UI nor commands like Get-SPFeature revealed its existence, although the Install-SPFeature -ScanForFeatures command emboldened below displayed the missing feature.
"Check that the feature has been installed. For example, if you are
performing Update-SPSolution and a new feature has been added between
solution deployments then the feature is not installed by default.
To check do the following:-
Run SharePoint 2010 Management Shell from one of the SharePoint
servers Type Install-SPFeature -ScanForFeatures This will show you any
features that are available in the SharePoint Root but have not been
installed. You can install any missing features using the command :-
Install-SPFeature -AllExistingFeatures
See the following TechNet
Article for more information.
http://technet.microsoft.com/en-us/library/ff607825(v=office.14).aspx"
Look in central admin to see what site collection the feature is deployed to. Make sure in that site collection the feature is turned on.
Also, check the deploy job status to see if it actually finished.
Is there a on install event receiver? If it errors out, the feature will not finish installing even after the DLL is copied.
Now our team is facing new project - creation of new company's intranet portal. Because of some reasons we are considering java open source portals and deciding between Liferay and GateIn.
One of very important requirements is following: portal representation for users must depend on country/language settings of customer computer, it means not only portlets localization but users in US subsidiaries of the company should see probably other structure than users in France.
Is it possible to implement the requirement in Liferay and GateIn?.
This can definitely be achieved through Liferay. Please have a look at the concepts of creating organisations.
Am not sure if this can be done in GateIn. However, there are many other things that you may need to keep in mind before choosing these Portals. I have tried to mention few of them here.
1. Check the stability of the Portal server that you will choose to run on a particular Container. GateIn initially was unstable.
2. You may have to override few files (for your customization) if required. GateIn uses GTMPL view technology for the same. Check how good are you in this. In this case, Liferay is easier (Liferay doesn't use any GTMPL UI framework)
3. Apart from developing a location based Portal, if you are also trying to achieve other things like fully Ajax based pages, a good UI framework (like JSF) etc then check if the Portal server you are choosing runs on a particular Container which supports Ajax, JSF (latest versions)
Above were few and list may grow. But, to conclude I would suggest to go for Liferay :)
This can be achieved with Gatein at different level :
Sites : you can declare multiple sites running on the same portal instance(sharing same User Base). In this case you can automatically redirect user to different country sites, based on the country/language of the user.
Sites Navigations : Gatein provides portal, group and user navigations. Navigation is created dynamically when a user connects to the portal. You can have only websites, navigation will created dynamically by user (based on group and user permissions).
Pages (Dynamics layout rendering): GateIn renders each page dynamically. A page is composed of multiple containers that contains portlets or gadgets.
By setting permissions on each container and by using User Group or Membership of the connected user, it's possible to have different page layout.
Of course, you can also mixed these 3 approaches to build your portal.
Liferay is very buggy, and community is very bad. Unless you pay the support.
GateIn promises much, but still lacks functionality.
You may consider JBoss Juzu and Apache Struts to develop generic portlets in order to void any portal vendor lock-in.
Struts provides features of internationalization, localization, timezones achieve my project.
I make use of struts2-portlet plugin to achieve a reporting portlet running on multiple portals. Here is my sample: code.google.com/p/jasperrocks/wiki/Features