I have imported a site into my local Kentico CMS Desk. The export had Media Library and physical files in it. But when I log into my local CMS Desk I do not get the option of Media Library in CMS Desk - Tools option.
I am logged in as Global Administrator both during export and import and I have permission on the Media Library module to Create, Modify and Destroy in CMS Desk.
The UI Personalization for this user displays the checkbox for Media Library - Add new library.
Sounds like it is the fact that you are missing UI Personalization values of the module. You should not just have Add new library. If you don't have other customizations you do a fresh install of 6.0.42 and export the whole tools module and import the whole module into your site. This will overwrite your settings to have a full clean set.
Related
I am customizing share point modern site. when iam uploading css file in styles library its showing deneid message but i am site owner andenter image description here i have full control right also.
Have you checked you permission in the style library? And also ensure custom script has been enabled in the current tenant.
I have one Notes Template ntf in which the Openntf Domino API plugins do not appear in 'Plug-in Dependencies' library, eg. org.openntf.domino.xsp etc. They are installed on both the server and the local machine, as we use XPiNC. They appear in any a new application created from the template and they appear in other templates and other nsfs. The plugin xml references them but they are still not in there.
<import optional="true" plugin="org.openntf.domino.xsp"/>
The Notes template is on a server. How do I get them in there or solve the problem, I have tried various import methods to no avail, this area is not a strong point for me.
Thanks for any help.
You cannot use an NTF with XPinc. The status bar will show a message about it not running. You can have an NSF with a TEMPLATE NAME that will refresh other database that inherit from that template. If you need the NTF for database creation purposes, develop in an NSF that has a TEMPLATE NAME from which the NTF inherits. (EG: MyAppDev). THe NTF then has a TEMPLATE NAME from whihc other databases inherit (EG: MyApp)
If you're getting an error that you cannot import a class in Domino Designer, there are two places to look.
The library needs "ticking" on the Xsp Properties. This tells the application that it needs that particular plugin at runtime. If it's missing on the server, you'll get an error.
The library needs installing for every Domino Designer that's going to be used to work on the application. Upgrading Notes to a new version will invariably disable previously installed plugins, so you need to go to File > Application > Application Management.... Custom plugins are in the second category, and if they have a red circle crossed through, it's disabled and needs re-enabling.
I have a new install of Orchard 1.8 and need to sync all images in the /media/default/ directory to the Media Library catalog of items (‘Media’ link in Dashboard). Currently the Media Library lists only the FOLDERS but not the items (images, docs, etc.) within them – only when the import is done online does it include the image and offer a preview.
I saw a similar post being asked for version 1.7 and Bertrand’s answer was ‘Enable the Update feature and migrate your media to the media library from there’ – yet I have no clue on how to accomplish this.
Can anyone list the steps needed to do a one-time sync of all items into the Media Library ?
From the admin menu click Modules, then find the "Upgrade" feature and click enable. This adds a new menu item called "Upgrade to 1.8", select this and then select the Media tab. Then click Migrate under Migrating Media Files.
Basically exactly as Bertrand said ;) He also has a blog post with more details:
http://weblogs.asp.net/bleroy/dude-where-are-my-images
I attended the MWLUG conference in Pittsburgh. One of the things I saw was an entry in the Eclipse menu, to let you import a custom control from OpenNTF. How can I add this to my menu or does it come as a part of updates for Notes?
It's an OpenNTF Project - Import and Export from Domino Designer http://www.openntf.org/internal/home.nsf/project.xsp?action=openDocument&name=Import%20and%20Export%20for%20Designer
It can be used to package databases for export to OpenNTF. It can be used to import not only custom controls but any design element. It's based on an XML file in the project. The file defines which design elements should be imported (there may be XPages for e.g. testing that aren't required when using the functionality).
If you're pushing anything up to OpenNTF, include the XML file of what design elements developers need to pull down from your NSF for their app to work completely.
If you want to see it in action, you should be able to use it to import the Mobile Value Picker project I put on OpenNTF. You'll see it doesn't pull in the XPages available in the sample app to demonstrate the functionality. http://www.openntf.org/internal/home.nsf/project.xsp?action=openDocument&name=Mobile%20Value%20Picker
I know this is not specifically a programming question, but programmers will often have to do this work.
How do I create a website with Liferay portal - the docs are pretty light on this fundamental issue and are all for version 4.4. I am using version 5.2 and the docs don't seem to be relevant.
Do you know what the basic steps are. So far I have logged in as the bruno user and can see the 7cogs website and edit it. But I now need to create my own website (for my company) and be able to develop portlets to add to the parts of the page.
Further I notice that the docs talk about doing work in Eclipse. If our website is all static HTML, (the reason we want liferay is mainly so that we can edit content items using its content management tools), then will there be any need for Java dev, or will it all be drag n drop and clicking to get setup. Any guidance will be much appreciated.
Liferay can be used as a simple CMS, without much Java knowledge : creating, editing and positioning of web content fragments are drag'n'drop and use of the included rich text editor.
But to start using Liferay for your company, there are two main steps : a technical configuration (database, etc.), and a look'n'feel customization.
The technical part
First of all, you should get rid of the 7cogs website : this is called a hook in the Liferay wording. To do that, if you are using Tomcat for the application server, just delete the 7cogs directory as stated here.
You can now create the configuration file for your installation : it's a simple text properties file, named portal-ext.properties and placed in the webapps/ROOT/WEB-INF/classes folder of your tomcat installation.
This file handles most of the configuration of the Liferay portal, for example :
the name of your company
if you want to display a terms of use page on first login
if you want anybody to be able to create an account on your portal
the database where the data will be stored
To do this, the properties in the portal-ext.properties override default properties found in a embedded portal.properties file located in the jar file portal-impl.jar, in the webapps/ROOT/WEB-INF/lib directory. Just unzip the jar file in a temporary folder to access the portal.properties file.
A sample portal-ext.properties file :
company.default.web.id=yourcompany.com
terms.of.use.required=false
company.security.strangers=false
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=root
jdbc.default.password=root
Once done, you can startup your application server. As the default admin (named test, something you can change in the portal-ext.properties file), you can access to the centralized web "control center", located in the "dock" (the strange menu labelled "welcome Test" in the upper right part of any page once logged in).
I would advise you to read the administration guide, useful for most administrative tasks.
The "branding" part
Liferay uses "Themes" to automatically decorate the portal pages (logo, navigation, portlet borders...) using images, CSS, Javascript (JQuery) and the templating language Velocity. The themes are bundled in a .war file, like a standard web application, and deployed on the fly either via the control center or by dropping the file in the deploy directory of the server.
Liferay can use several themes at the same time, one for each community (a group of pages, users and content) for example.
Creating your own theme can be done afterwards, using the "Plugins SDK".
The Wiki, forums and blogs can be very useful.