I have a solution and want to create a custom Area for that solution. I have created the Area but I want to have that area in all instances that I will install my solution but I don't want to override the sitemap that is in instance. I want to add only my custom area. I
Export the solution then go into the customizations.xml file and find the sitemap XML, remove all of the other areas from the solution except for your custom area. The result should be a SiteMap node with a single Area node. During import, your custom area will be added to the sitemap and existing areas will be left alone.
Optionally you could create a new solution with just the sitemap to make this manual editing process easier.
Related
Purpose: To add a Group with SubArea (opening a WebResource), which could be added in a managed solution. Sitemap state before installation and after uninstallation should be same.
I understand how merging in Dynamics works and that is not an issue for me
A generic sitemap inside customizations.xml would look like this
<SiteMap>
<SiteMap IntroducedVersion="7.0.0.0">
<Area Id="MA" ResourceId="Area_Marketing"
DescriptionResourceId="Marketing_Description"
Icon="/_imgs/marketing_24x24.gif"
ShowGroups="true" IntroducedVersion="7.0.0.0">
<Group Id="Test Group" Title="Test Group" IsProfile="false">
<SubArea Icon="$webresource:te_/assets/images/logo.png"
Id="te_survey"
Url="WebResources/te_/index.html"
Title="Test WebResource"
AvailableOffline="true"
PassParams="false"/>
</Group>
</Area>
</SiteMap>
</SiteMap>
However, when I used this I do not see any entry in SiteMap.
I found a post that address my concern directly. It asks to use solutionaction attribute in SubArea/Group elements which let CRM merge sitemap durin installation and uninstallation for a managed solution.
Sadly this does not work in Dynamics365. I lost my whole sitemap when I tried using it.
I think this is a relatively popular scenario.
PS:
I am on Dynamics365 (v8.2), so I cannot hack into the code behind, nor would I prefer it.
I tried How do I remove Dynamics CRM sitemap customizations?
, but it does not work in Dynamics365
Site Maps are typically modified in a development environment through the built-in Sitemap Designer or through external tools such as the XrmToolBox SiteMap Editor plugin. They're then exported as a managed solution which will contain only the differences to the site map. Here are steps to perform the changes you're wanting to make using the built-in Site Map Designer:
Create a new solution in the development instance
Add the site map to the solution
click on Components > Add Existing > Site Map
click on Site Map, then OK
Double click the site map component to edit it in the Sitemap Designer
Drag the Area component to the exiting menu to create a new area
Drag a Group component to the newly added area to add the group to the area
Drag a Subarea component to the newly added group to create the menu item for launching the web resource
Edit the properties of the subarea to reference the web resource
set the Type to Web Resource
set the URL to your HTML web resource
Save and publish the site map
Export the solution as a managed solution
Import the managed solution into the target instance to apply the site map changes
Delete the managed solution in the target instance to uninstall the solution and revert the site map changes
I have been using ckeditor 4 in my CMS and using the template feature to allow the user to add a collection of template styles they've agreed open in to the editor so they are able to create uniquely styled pages. I have it so they can see the different colours templates within the editor, which allows them to see what section there typing content into.
The problem i'm finding is that after its saved and i go back into the editor to add another template, it only adds it within a existing template and i am unable to click outside of it. The only way i have to get round it is to copy and paste a section from the source.
Is their a way to allow me to click or move the cursor outside the template so i can add another one underneath it and not in it?
Regards
Add to your editor the Magic Line plugin. It adds a "floating bar" that allows to place the cursor after elements like tables, divs, ...
Please I need some guidelines (or link of tutorials) in creating Joomla (3 - 3.5) website with the purchased template design. I wonder how professionals with experience are solving my doubts in practice.
Do you recommend the installation of the purchased blank template with a single installation and configuration of modules and components or installation of template with demo examples (Quickstart)? I know the differences but I was wondering how you are doing.
Till now I've almost always used the Quickstart installation.
I wonder if you clone the main menu (and other navigation and modules) and than you rename a copy for your needs and you change the content or you delete all navigation items except Home and than you are re-creating items according to your needs.
I'm not sure if I can copy the main menu or I copy only his necessary items and than delete overage of template.
It happens to me sometimes if I click on some of category it leads me to the main menu from original item, not to the desired custom copy, even though the path is set (the default items). Therefore, I am not sure which is better... copy main menu and items or to delete all navigation and content of the Quickstart installation and form my own navigation, content and modules.
In short, how to sort out all unnecessary items, and those that I am using should I copy and modify, modify existing, or delete all and make my own needed items.
I believe you will know my concerns.
Thank you and regards,
John
I have created several websites in Joomla with blank template and also with quickstart package.
Advantages with Blank Template
You will get the core theme without any unnecessary content and
basic modules and plugins. You dont have to delete any
contents/articles later.
You will be having authority to place modules at your desired positions. To check the modules position at the frontend simply do this http://example.com/?tp=1.
Disadvantage of Blank Template
There are some module style settings embedded in quickstart package that you wont be able to set yourself without going through full documentation. So sometimes your menu seems distorted.
Disadvantage of Quickstart Package
Deleteing unnecessary articles, removing unnecessary modules is a big headache.
Database size unnecessarily increases.
Steps I follow
I create a quickstart package in localhost and create a blank site with blank template in live site. Whatever settings I need I copy from the local website so that I am saved from removing unnecessary contents from live site. Also sometimes deleting some contents give rise to some other issues. Its better t go with a Blank template.
I’m fairly new to Magento themes and have been looking around for best practices for building them. I have an understanding of creating a skeleton structure for my theme and copying template files from the base theme. What I’m not sure of is, if for example I wanted to customise the product view, is it best practice to remove blocks from the view.phtml file or should I remove them in the layout file? I want a fairly simple product page with wishlist, compare, tags etc removed.
Many thanks in advance for your advice.
You need to remove from both from xml you will find handle catalog_product_view you need to remove code as well as you need to remove from view.phtml file in folder of your new theme. At the end your code will be cleared and will take less time to execute.
I want to customize our installer which is based on NSIS. My question is could we create custom windows? Where I mean not customizing Modern UI or other built-in surface, but building a totally new look with custom Window header, buttons and other elements like list where all element have other state, and all of the states are represented with an animated item before the text.
So I want to develop my look from ground to the peak. This can be done somehow?
You can do this using a resource hacker of your choice, e.g. PE Explorer, XNResourceEditor, Resource Hacker FX or good old ResHacker. You'll have to make sure to use the same IDs for the controls, so you probably best start by editing on of the existing UIs.
Like idleberg said you have to edit one of the .exe resource files (in the Contrib folder) with a resource editor. To apply the new UI you have to use the ChangeUI instruction. You can change all pages or just a single page...