website.powertools.http=http://powertools.local:9001/mystorefront
website.powertools.https=https://powertools.local:9002/mystorefront
website.mystore.http=http://localhost:9002
website.mystore.https=https://localhost:900
those are from localproperties.
so now, when i go to
https://localhost:9002
storefront comes. when i click something, it goes to
https://localhost:9002/powertools/en/USD/Open-Catalogue/Tools/Measuring-%26-Layout-Tools/c/1358
i want to remove this powertools and make it mystore.
What should i do?
I did not configure powertools, it is coming from b2b.
I also did not configure mystore.
I just want powertools to become mystore.
also on project properties, i did
mystorefront.webroot=
storefrontContextRoot=
this to make localhost navigate to mystore.
i also used that impex and i can see in in wcms / websites
$siteUid=mystore
# CMS Site
INSERT_UPDATE CMSSite ; uid[unique=true] ; urlPatterns ;
; $siteUid ; (?i)^https?://[^/]+(/[^?]*)?\?(.*\&)?(site=$siteUid)(|\&.*)$,(?i)^https?://$siteUid\.[^/]+(|/.*|\?.*)$,(?i)^https?://[^/].*$ ;
An accelerator module is able to display more than one CMS Site. A CMS Site is the configuration item for your online shop frontend. It is stored in the database. The accelerator module is just the source code that takes care of displaying a CMS Site. What products/pages are displayed and what languages, designs and so on are supported is configured in the CMS Site. Also, a CMS Site holds URL Patterns, which are regular expressions. If the request URL matches one of the URL Patterns, it is considered to belong to the corresponding CMS Site.
Did you configure a CMS Site for mystore? Creating a CMS Site requires the creation a lot of related types and has a lot of pitfalls. I would recommend you to follow the commmerce trail on the hybris help pages to create your own accelerator module/CMS Site config.
Related
I have newly created a b2b accelerator website and included catalog, catalog version, category and products, personalization etc. when I am trying to live edit staged version adding home page into it then it is redirecting me to login prompt and if I login then the page not found message showing. I am new at hybris. I don't know what could be reason of prompting login while attempting to live edit. Even using smartedit editing also has the same manner.
I would be very grateful if anybody can help me regrading this issue. I didn't find any tutorial how to customize b2b accelerator website making configuration.
When you see a generic hybris "page not found message" the url you called will most probably not be registered in your storefront. When you open your cms site in hmc/backoffice there is an attribute called "URL pattern". This attribute holds a list of strings, which are regular expressions. Every request you fire against the storefront has to match at least one of those regular expressions. That way, you can have more than one site on one hybris server.
E.g. there are the sites electronics, apparel, powertools, all available on the same machine but using different urls: http://electronics.local:9001/, http://apparel.local:9001/ and so on.
we have already created a custom cms. now we have to provide multi site option to this.
i have initial idea that i have to create a default project which contain codebase that will be used to serve pages created from cms
for a single site it is currently supported , and even when we create manually another site then also it is working fine..
my question is what i m doing is really multisite ? ( we have one cms , but for every site we are creating separate application in IIS)
if yes,
how would i able to create default application with certain folders,files in IIS programmatically or with some batch commands ..?
if no ,
can any one guide me on how to create multi site in cms by providing some tutorials on how multi site works in cms ?
I don't fully follow your question, however, from what I do understand, you have a single code base, and you want to host multiple websites from the single code base, e.g. www.domain1.com, www.domain2.com, etc.
Well, if that is the case, you can very easily configure one IIS website to accept multiple hostnames to the same code base by setting up site bindings (see: http://www.orcsweb.com/blog/mark-newnam/how-to-set-up-site-bindings-in-internet-information-services-iis/).
As for your custom built CMS system, it will need to determine what the hostname is in order to display the correct website.
There are two types of pages in sharepoint. Application and site pages. In site pages if we want to customize them, are we not able to use the server side code? If so why? I saw an article related to this in MSDN.
Generally what is meant by customized here. Adding a webpart through the code is customization? Please explain me any one.
Without a web.config modification (not recommended), Site Pages do not support server side code (either inline or in a code behind file). This is primarily for security and performance reasons. Unlike Application Pages, Site Pages can be added or modified in SharePoint Designer and, in a limited fashion, through the browser.
Normally, there are many more users with these privileges than those users that have access to the web server. I'll leave it to your imagination to consider some of the insecure or inefficient server side code some of these users could create.
In addition to custom web parts, see Where's the code-behind for sharepoint aspx pages? for server side code options within Site Pages.
When you're doing application page, you're storing the aspx with the 12 / 14 hive (SharePoint installation directory) and you're free to use any code behind class / component that you want to use. The original aspx file will stay in the physical folder of the Web Frond End
On the other side, when you're creating site pages, you're adding a new entry within the content database and not on the file system. Even if you have a site page template, you need to add safe entries to your web.config to trust the assemblies.
For the site pages, it is suggested to work with WebParts. They will allow you do do any business / core logic with the actual page, list, web, site.
When they talk about customization, they talk about modification done to the site pages that will alter the original definition. A site page provisioned through a web definition will stay "uncustomized" (ghosted) in the file system until it is being edited.
During site creation using SharePoint, SharePoint offers some templates. If we need to create a site other than a template offered, how should we proceed?
You have 2 options:
Site Templates
Site Definitions
Many people use those terms interchangeably, but there are big differences between the two.
Site Templates
Site templates are easy to create. Basically, you create a site using a ite definition (e.g. the blank site) and start customizing it. You can add lists and libraries and setup the site however you want it. Then, go to Site Actions > Site Settings > Save site as template. You can save your site as a .STP file. The .STP file basically records everything that you added or changed on your site after site creation.
Once saved, your site template will show up in your site template gallery. You can go to the site template gallery and save the .STP file offline. Your new site template will be available in the subsite creation page in the "custom" tab. The template will only be availalbe in this site collection, unless you add the .STP file to the site template gallery of another site.
You can deploy site templates globally. So, if you want everyone to see a STP in their subsite creation page, you can run the following stsadm command:
stsadm -o addtemplate -filename BoardDirectors.stp -title "Board of Directors"
You can retract site templates whenever you want without affecting the sites that used them for creation. This makes them easy to version, as long as you don't want to push updates to existing sites.
One big problem with site templates is that you cannot staple features to them.
Site Definitions
Site definitions are collections of XML files deployed to the 12 hive. They are harder to develop; you basically have to use Visual Studio. The XML files have to be packaged into a SharePoint WSP and deployed using STSADM.
Creating a site definition gives you the most control over your site. Another benefit is that sites using the site definition will always reference the site definition's files, so updates will be recognized by sites using that site definition. For example, if you find a bug, you can fix it in one spot and all sites using that site definition will be fixed.
Note that withdrawing a site definition will break sites that use it.
Recently, many SharePoint experts have recommended staying away from creation new site definitions because of the overhead. Instead, if custom functionality is needed, they recommend coding custom features and just activating those features on sites.
Think about which option you need. In our organization, we chose not to create any new site definitions, and use site templates sparingly. Custom functionality is driven primarily by the use of features.
You are talking about custom "site definitions" and custom "site templates". Google those terms and you'll find tons of information.
You can design your own custom templates. Install VSeWSS extension for Visual Studio and it has a project type called "Blank Site" template. You can use it as a base starting point and customize the solution generated to your needs. All the information required to do so is available in the help document that comes with VSeWSS.
I need to provision a custom aspx page which does some work and then redirects to another page. Using a _layouts page, AKA an application page won't work since I only want this page accessible to one site collection.
I looked at using pattern #4 from blog post Application Development on MOSS 2007 and WSS V3. It feels pretty hacky, and it asks you to drop the DLL. Drop it into the bin of the site collection, and upload the file through SP Designer.
I'd rather have this page be a feature that gets included in my site definition or stapled to an existing site definition. I imagine I could use a feature receiver to deploy the files to the pages SP list. One of the comments on the blog post says as much:
Pardon my ignorance on this maybe I am
missing the point completely but
wouldnt it be easier to deploy your
custom pages by programmatically
adding them to the pages splist?
I basically, had a simple .aspx page
with a user control. I deployed it via
this method.
How can a custom page be provisioned without using a _layouts page?
I guess another option is to keep using a _layouts page, but make sure the referrer is correct.
Besides application pages, you also have the possibility to create site pages.
Site pages are in nature related to application pages, but they reside in a site not in _LAYOUTS.
The welcome page (default.aspx) is an example of such a page.
In the same way as with application pages, it is possible to do codebehind in these pages (check out AC's article on this subject, Using ASP.NET 2.0 Code Behind Files in SharePoint v3 Sites)
You can read this article regarding the subtle differences between application pages and site pages: SharePoint Application and Site Pages - Part 1 of 2
You deploy this custom page using a feature, where you specify the file as ghostable (look at the example in ACs article).