How can we remove default HomePage Theme with Custom Theme in DNN 8? I haven't got any blog providing me clear idea about it.
You can change the styling of a page by changing the "Skin" or "Theme" in the Page Settings on the page.
Update:
To create a skin I highly recommend you follow my tutorials:
http://www.christoc.com/Tutorials/All-Tutorials/aid/8
In order to use the DNN Theme Project template (new with the 4.0 release of Christoc’s development templates, January 2015), you will need to follow the steps laid out in this tutorial exactly. If you choose to not follow each of the steps, you may run into trouble and will have to figure out things on your own. As always, support for our tutorials is provided in the form of paid DNN Support and Consulting. You can also visit www.dnnchat.com and possibly get some free support there, but no guarantees are made that support will be provided there.
Prerequisites
The latest release of the Project templates requires Visual Studio 2013+, it will not work on VS2010 or VS2012.
As with the Module Development templates, the Theme development template requires you to have your DNN Development environment configured in a specific way. You should have your development environment running at the URL http://dnndev.me/ good news for you, it is very easy to do, all you need to do is follow this tutorial.
Once you have your environment setup, you need to install the Project templates. This is another easy step, simply follow this tutorial.
Now that you have the Templates installed, you can get to doing the real work, working with the Theme project template itself.
How to use the DNN Theme Project Template
Run Visual Studio 2013 as an Administrator (right click on the shortcut to do so)
File –> New Project
Choose the Visual C# option from the Languages section of the new project dialog
Select the DotNetNuke Folder
Choose the DotNetNuke C# Compiled Theme template for your project template
For the new project creation screen using the following settings
Name: ThemeName (something unique here, example MyFirstTheme)
Location: c:\websites\dnndev.me\portals_default\skins\ (this assumes you setup your development environment as instructed) DO NOT PUT THE SKIN IN /PORTALS/#/SKINS/
Solution: Create new solution
Create directory for solution : Unchecked (this will cause path problems if checked, the templates assume the SLN is in the same folder as the project file)
Add to source control: Unchecked
Click OK
Once your Theme has been created, you will want to perform the following steps.
After project creation steps
Delete the Documentation folder (it isn’t needed)
Switch from DEBUG to RELEASE mode
Build the project. This will create an INSTALL and SOURCE zip file in the /install folder within the project’s folder on the file system (/portals/_default/skins/themename/install/)
Login to your DNNDEV.me site with a HOST/Super User account
Navigate to the Host/Extensions page
Upload the newly created INSTALL zip file (created in step 3) using the Install Extension Wizard on the Host/Extensions page.
Navigate to a Page and apply the skin to your page.
A few items of Note:
The Theme template and package MUST be in the /portals/_default/skins/ folder, not in one of the individual portal’s (/portals/0/skins/) folders.
The Containers are inside of the Containers folder, inside of the project. This is not where DNN expects them to be, they need to be in /portals/_default/containers/ThemeName/. The Project templates will put them into that location in your development environment when you BUILD the project in RELEASE mode. During Installation in another environment, when installing the INSTALL package for the theme will do the same thing.
Related
I would like to use Eclipse in an intro programming class. Is there some way I can make some kind of preferences file or some such that I can distribute with it that would set defaults for:
which buttons are in the toolbar
which menus are enabled in the application
which context-menus are enabled
what kinds of completions are available
I'd like it to start with only completing words from the current document
that is no Java API completions or code generation or whatever
This can be done using Eclipse Preferences File. All you need to do is import preferences into your workspace.
You can also export the workspace folder itself & publish Eclipse together with a default workspace folder, which will contain all the preferences.
Then create a shortcut to start eclipse with -data <path to your workspace> parameter
I'd try the following:
Install Eclipse
Put the configuration files and workspace under version control and commit.
Configure Eclipse as required.
Check all the changes in the version control to understand what configuration files are relevant to my changes.
Continue as Zilvinas is suggesting.
Look into Eclipse Oomph. It essentially automates all the tasks that you need to do to set up a fresh dev environment.
Also of interest are Yatta profiles which do a similar thing based off Oomph.
They're pretty easy to set up and publish. Get your local eclipse working, record to a profile, publish the profile, get your students to consume said profile. We've used these in a professional environment to more easily on-board new devs!
We've updated to Visual Studio 2017 and switched to Team Services (VSTS) as our source control. I've migrated a few old projects and am using the Microsoft Installer Project extension to provide compatibility for the original setup projects.
However, there seems to be a potential issue with source control when working with the setup projects. Attempting to make any change results in the error:
The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out.
Modifying files of other projects within the solution work correctly and trigger checkout from the repository.
I have not been able to determine a way to properly check out the setup project and work with it under the new source control. I'm unsure if it's a bug with the extension or if it simply lacks support for VSTS.
Has anyone successfully been able to work with setup projects (.vdproj) in conjunction with VSTS? If not, is there a workaround?
Edit:
Image of context menu:
You can apply the following workaround, since it seems to be a bug in the installer extension:
Choose 'Open file in File explorer' in your context menu
Open the project file in your favorite texteditor
Make a dummy change (adding a space character in an empty spot is enough)
Visual studio will prompt to reload the project and has explicity checked out the project file.
see also here
I submit a feedback here: The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out
The workaround is that you can check out the project manually. (Right click the installer project > Check out for edit)
I am trying to run an Xpage locally (in Chrome if it makes any difference) from a local NSF and am receiving the error:
Build path contains duplicate entry: 'org.eclipse.jdt.launching.JRE_CONTAINER'
I have copied all the ExtLib Features and Plugins to the correct directories as required.
Anonymous is set to Author.
I cannot find any information on how to resolve this. There was an open ticket on OpenNTF 6 years ago but no resolution.
[Update]
As Jesse Gallagher pointed out on Twitter, you can access the .classpath file without going through the ODP setup via the Navigator perspective. I would still recommend setting up source control since it gives you:
local change history in DDE (even if you don't use the ODP in git/hg)
the ability to track any changing file during development, aka- a rogue change to your .classpath file (I recommend installing Cameron Gregor's Swiper plugin)
is fairly easy to set up
as a developer, version control is the best way to cover your butt
[/Update]
I believe you quite literally have a duplicate entry in your NSF's build class path. This has to do with the Eclipse version Domino Designer is based on is being confused by its defined class path. I recommend the following:
if you don't have it set up already, set up source control for your NSF
open the (hidden) file .classpath, which can be found in the root of your On Disk Project (ODP) folder with a trusty text editor (Notepad++, etc.)
search for org.eclipse.jdt.launching.JRE_CONTAINER
if you find more than one, you will need to deconflict your class path (aka- remove one; it may be best to make a backup of the file)
if you don't have "Build Automatically" checked (in your Project menu), you may need to open Package Explorer and right-click your ODP, then perform a "Sync with NSF"
You should be able to de-conflict your build path via the Project > Build Path screen, but this is an easy way to search the whole thing in one shot.
Here's an example the .classpath file from a working app.
An example of a situation where others (using gradle, in this case) ran into a duplicate issue with org.eclipse.jdt.launching.JRE_CONTAINER.
Setting up source control with an NSF, right-click NSF, Team Development, Set Up Source Control:
Note: If you need a little more info on how to set up source control or want to know more about where to park the ODP (aka- if you haven't done this before), I recommend checking out David Leedy's Notes in 9 episode 131: Using SourceTree for Better XPages Source Control. Even if you don't use SourceTree, it's worth it to understand that the ODP should not be placed in your Notes Data directory, etc.
I'm working on a joomla project and for debugging/type hinting/auto-complete have my whole joomla install as a project. Is there a way I can hide the folders I don't need in file or project view?
Ideally I would have a project that scans all of the folders but simply displays this:
administrator
components
com_myproject
(display all files under this)
components
com_myproject
(display all files under this)
You can hide any directories you'd like in Netbeans 6.9.1. Right click on the project, select properties, and select the "Ignored Folders" category. In this section you can add all the directories you don't want to see.
No, you cannot do it with NetBeans like this.
However, you can do it little differently... this is going to be component development.
Basically for every custom component you will need to have a separate project.
Create project with folder structure like Joomla
|
|-administrator
|-componnets
|-my_component
|
|-componnets
|-my_component
After this step, right click the project and go into properties. In the properties go to PHP Include Path, map path to Joomla directory, this is what is going to give you autocomplete feature for Joomla code.
Also, to improve auto-complete for Joomla, go to Tools->Properteis->Editor->Code Copletion
Select PHP from language drop down.
Check Also Non-Static methods after ::, this will give your auto-complete for methods like JFactory::getDBO(), etc...
Obviously it makes it hard to test right now, because component is not inside of Joomla... and copying it manually makes it a hassle. Go to project properties (right click project->properties) and enabled "copy files from Sources Folder to another location" and math the path. NetBeans will no allow you to setup copy into existing directory, workaround is simple.
Setup copy support into temp direcotry /tmp
In NetBeans windows, go to Files of your component project
Expand the nbproject node
Open project.properties
Manually modify the copy path
If you want something more advanced and runt test's, you can use Ant and create build.xml files. Read more about it on Sun's blog about NetBeans PHP and Ant.
Heres a video that will help u to do the same using netbeans IDE. Keeping yout component file into a seperate directory and do the development making full use of IDE features using the Apache ANt build procedures.
The Ant build file.
http://docs.joomla.org/Building_Joomla_Extensions_with_Apache_Ant
The video to help you setup netbeans for component development.
http://www.vimeo.com/13167176
We have an RCP application and we are looking for a better way to do installation/updates. Currently to install, they just unzip a zip file. The zip file also contains scripts in it that are not java code. We were running into some bugs when updating if they don't first delete the old folder that was previous unzipped. The issue with deleting the folder is that the user loses the plugin preferences that were set. The installation would also need to register a COM server. The update would have to update the plugins and also replace the current script folder. What are some of the best options that could be used for installing and updating rcp apps? Thanks!
An option is to use the eclipse update mechanism. In this case the user would simply update like in the eclipse ide using help->software update. I have not used it myself yet ,but I have visited a tutorial from kai tödter, just google "eclipse rcp adanced kai tödter" und you will find some stuff, e.g. slides where he explains the updated mechanism as well as an example project "MP3 Manager" where you can find an example