Unable to Retreive Site definition - Endeca 11.1

Hi All,
I am getting below exception.
Can any one suggest on this?
14:40:02,550 SEVERE [atg.endeca.assembler.multisite.ExtendedSiteManager] (http-/0.0.0.0:8080-5) Unable to retrieve site definition for site id: /homeSite: com.ende
ca.store.exceptions.PathNotFoundException: No node found at path: [pages].

Hi,
If you are using the filestorefactory you should export the experience manager configurations to a directory and point the same directory in your assembler properties as well.
This is a reason for the page not found error.
It also throws the siteID definition is not available. So create a site named homeSite in the configuration files and do the configurations for the filestorefactory and continue with your work.
By default if you have installed all components in a single server or machine you can just do the promote content and you will be able to work.
Hope this solves you problem.
Thanks,
Karthik V

Similar Messages

How do I manually recreate the site definition (.ste) for an existing site?

My iMac hard drive recently failed and had to be replaced.
Though I had backed up my web site files, I don't have a backup of the site's Site Management (*.ste) file.
Thus, I'm unable to manage this site in Dreamweaver (reinstalled on the new hard drive).
In some forum threads, there are references to "manually recreating the site definition." How do I do this?
Thanks!

paintwlight wrote the following:
Does Putting the site to the remote server constitute an Export, whereby a .ste file would have been created during the Put process and, therefore, exist on the remote server?
No. Hit F1 and search for Export.
If so, I assume that if I copy the .ste file currently on the remote server and save it locally (into Library:Application Support:Adobe:Common:9:Sites:Site Prefs), all will be well and Dreamweaver will once again be able to manage the site.
DW can manage the site after you have defined the site as mentioned
earlier. It does not need the .ste files at all. Those are created by
the user via the Export feature and are not used by DW itself.
Gosh, I wish I would have known about the .ste file before my hard drive died. This seems like way too much responsibility to put on one teeny tiny little file -- especially one that's not kept with the rest of the web site files.
The .ste file contains only the paths to your site and the login
information - if you choose to include that information. It does not
contain any of the actual files. DW does not act as a backup or archival
program. You need to keep backups of your entire site (including source
files used to create the site, such as Photoshop/Fireworks layered
images, Flash .fla files, etc...) as well as backups of the .ste files.
HTH
Mark A. Boyd
Keep-On-Learnin'

Site definition Help needed....Thanks

I am working with Dreamweaver 8. Vista operating system. My problem is a simple one but I am really
stuck on it.
In the past I have learned that to set my site definitions
to always work OFF line and then transfer changes to my hosing company. For some reason this has changed to working
ON line in the ftp:\\ mode.
I am unable to find a way to get back to the SITE
DEFINITIONS PAGES to change back to “Edit locally and then upload to remote
testing server.” Need help, PLEASE
Joe

DW will just give a site a name when you first try to define
a site. That pop-up box which says those names should give you the
option to click in the text areas and change the name and path to
whatever you wish.
To answer your questions I will say the following:
1 - To do this would would serve no purpose I will explain
why with the answer to #2.
2. I wouldn't recommend putting only C:\ in the local root
folder box. That would potentially cause issues down the road
because then DW would have access to work in the WINDOWS directory
and this is not good. I would highly recommend keeping it in your
user account on Windows XP (this is anything inside the
C:\Documents and Settings\Username folder, which includes your My
Documents folder). Now to jump back to #2. Without defining a
proper directory you would not be able to use its functions for
PHP, ASP or any server-side script. You would also not be able to
insert Flash files onto your web pages nor would you be able to use
the new features such as Spry. This is because DW needs a folder to
work in so that it can create the associated files and folders
which accompany making those types of scripts and functions. You
don't necessarily need to connect it to a remote website if you do
not have one, but you do need to specify a local folder to work in
and I would highly recommend it. Thus defining the Name only gives
the site definition a way for you to reference the site, even if it
is for testing many sites. For instance I put my sites in a folder
called "Sites" and then inside that folder I have many subfolders
which are defined sites in Dreamweaver. Each folder has a name
which corresponds to it that DW sees.

Lost site definition in CS5.5

My IMac crashed and now l the Site Definitions file is lost, I have tried to do a restore from my Time Machine but I am unable to find the Site Definitions Folder
I have even tried reinstalling Dreamweaver as per the instructions in the Adobe support site after reinstalling DW I am still unable to make a new site, I am getting an error message that tells me that the Sprite Assets folder is not inside the site
Should I move the Dream Weaver application from the Applications Folder to the Trash and reinstall DW? or what?
Some help will be appreciated

Whenever DW starts acting up, the first thing I do is clear the program cache:
Deleting a corrupted cache file
If that doesn't take care of it, I move on to restoring preferences:
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
If restoring preferences doesn't clear the issue, the "nuke it from orbit" option would be a fresh re-install using the Cleaner Tool:
http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html

Site definitions stored where? os x

I need to migrate my site definitions and settings.
Unfortunately I am unable to export import from Dreamweaver due to
a problem with my old computer.
(An iMac G4 with a dead screen. So I am only able to access
the data on the HD by booting it up as an external firewire drive
to my new Mac.)
I am unable to run the old version of Dreamweaver in order to
perform the standard export / import process.
So the question is:
where does Dreamweaver store the site configuration data so I
can drag and drop from the old comp to the new,
thank u

It depends on what version of DW you are running. In DW8,
they're here:
/Users/[username]/Library/Application
Support/Macromedia/Common/8/Sites/Site Prefs
HTH,
Randy
> I need to migrate my site definitions and settings.
Unfortunately I am unable
> to export import from Dreamweaver due to a problem with
my old computer.
> (An iMac G4 with a dead screen. So I am only able to
access the data on the HD
> by booting it up as an external firewire drive to my new
Mac.)
> I am unable to run the old version of Dreamweaver in
order to perform the
> standard export / import process.
>
> So the question is: where does Dreamweaver
store the site configuration
> data so I can drag and drop from the old comp to the
new,

Show a WebPart view in a visual studio site definition

Hi Guys ,
i developed a Site definition in VS. In this Definition i have a list instance based on Promoted link template (type 170).Now i want to show in the Deafault.aspx a view of the promoted link but when i put the snipet
<WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly" ID="full" Title="loc:full">
<WebPartPages:XsltListViewWebPart runat="server"
ListUrl="Lists/List1"
IsIncluded="True"
JsLink="clientTemplate.js"
NoDefaultStyle="TRUE"
PageType="PAGE_NORMALVIEW"
Default="False"
ViewContentTypeId="0x">
</WebPartPages:XsltListViewWebPart>
</WebPartPages:WebPartZone>
the server respond me : ..Type 'Microsoft.SharePoint.WebPartPages.WebPartZone' does not have a public
property named 'XsltListViewWebPart'. I added
<%
@RegisterTagprefix="WebPartPages"Namespace="Microsoft.SharePoint.WebPartPages"Assembly="Microsoft.SharePoint,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
but it doesn´t work..
Any suggestion?

Hi gohberto,
Before <WebPartPages:XsltListViewWebPart> tag,you can add <zoneTemplate>
Here is a code snippet for your reference:
<WebPartPages:WebPartZone runat="server" FrameType="None" ID="Main" Title="loc:Main">
<ZoneTemplate>
<WebPartPages:XsltListViewWebPart runat="server" ListUrl="Lists/My List" [abbreviated...]>
<XmlDefinition>
<View Name="Some View" Type="HTML" Hidden="TRUE" TabularView="FALSE" DisplayName="" Url="View.aspx" Level="255" BaseViewID="1" ContentTypeID="0x" ImageUrl="/_layouts/images/generic.png">
<Query>
<OrderBy>
<FieldRef Ascending="FALSE" Name="ID"/>
</OrderBy>
</Query>
<ViewFields>
<FieldRef Name="ID"/>
</ViewFields>
<RowLimit Paged="TRUE">1</RowLimit>
<Aggregations Value="Off"/>
<Toolbar Type="Standard"/>
</View>
</XmlDefinition>
<DataFields>
</DataFields>
</WebPartPages:XsltListViewWebPart>
</ZoneTemplate>
</WebPartPages:WebPartZone>
Here is a similar thread for your reference:
https://social.msdn.microsoft.com/Forums/sharepoint/en-US/7740935e-d4d7-46f8-9dac-09b9c46855c6/type-microsoftsharepointwebpartpageswebpartzone-does-not-have-a-public-property-named-webpart?forum=sharepointcustomizationlegacy
Best Reagrds
Zhengyu Guo
TechNet Community Support

Backing up and restoring site definitions

Losing your site definitions in Dreamweaver can be a disaster, but it does happen sometimes. The best way to prepare for such an eventuality is to back up your site definitions on a regular basis.
Creating a backup
You can back up all your site definitions in a single operation by selecting Site > Manage Sites. In the dialog box that opens, Shift-click to select all site names, and then click Export.
In Dreamweaver CS6, the Manage Sites dialog box looks like this:
In earlier versions of Dreamweaver, it looks like this:
Dreamweaver asks if you want to include passwords and login details (this is the default option). Whichever option you choose will be applied to all sites, so click Cancel if you want to treat some sites separately, and export your sites in two sets by using Ctrl/Cmd-click to select them.
When you click OK, Dreamweaver asks where you want to export the definitions. Navigate to a suitable location, leave the File name field unchanged, and click Save. Although only one site name is listed in the File name field, Dreamweaver exports all the site definitions as .ste files in a single operation.
NOTE: This process backs up only the details of your sites, such as the location of the root folder, FTP details, and so on. It does not back up the actual files in your site, such as .html (or .php, .asp, .cfm) files, images, and style sheets. It's a good idea to use your normal file backup routine on your actual files from time to time, as well as exporting the site definitions.
Restoring site definitions
In the event of losing your site definitions in Dreamweaver or moving to a new computer, open the Manage Sites dialog box, and use the Import button to navigate to your backup .ste files.
What if I don't have a backup?
Often, if you don't have a backup of .ste files, you need to go through the whole process of re-entering the details for each site manually.
However, you might be able to restore them by using a restore point on Windows or Time Machine in Mac OS X.
On Windows, the site definitions for Dreamweaver CS6 are stored in the Windows Registry at HKEY_CURRENT_USER\Software\Adobe\Common\12.0\Sites.
In Mac OS X, they are at Macintosh HD:<username>:Library:Application Support:Adobe:Common:12.0:Sites:Site Prefs.
In recent versions of Mac OS X, the Library folder is hidden. In the Mac Finder, select Go > Go to Folder, type ~/Library in the search field, and click Go.
Dreamweaver CS5.5 site definitions are in the same location, except use 11.5 instead of 12.0. The numbers for CS4 and CS3 are 10 and 9 (without a decimal fraction) respectively. For earlier versions of Dreamweaver, substitute Macromedia for Adobe, and adjust the number accordingly.
If you don't have a backup of the actual files on your site, download the files from your remote server.

Hello,
We are running iPlanet 5.2 Messaging Server and need
to migrate to another (duplicate) 5.2 Messaging
Server. We have all the software installed and the
LDAP user accounts created. Now we just need to move
the existing mail from one server to the other.
I found the Backing Up and Restoring the Message
Store section in the Admin Guide says to back up and
restore your data, Messaging Server provides the
imsbackup and imsrestore utilities.
However I am wondering about the Queue?
Under <instance>/imta/queue
What is the difference between the Message Store
and the Queue? The Message Store is where messages get delivered to, so you can read them.'
The queue is where messages are temporarily stored, pending delivery to wherever they go.
You can use tar, cpio, or what have you for the queue. Stop the server first. . .
You then just restore the files to the new server. No need to restart or anything like that. Just dump the files in, and run
imsimta cache -sync
to tell the MTA to re-read the queue.
Can I just backup and restore the
Queue using tar or cpio?
Thanks in advance for any advice.
Regards,
Tim

Remote and Testing Server Site Definitions

I am confused about what information I should put in my
remote site definition info and testing server FTC Host directory
text boxes. My host placed 3 directories: database, log, and www on
my server and Dreamweaver placed two directories, Connections and
_mmServerScripts in the same directory as the above 3. I have
placed all of my site files, including my home page and folders in
the www directory and my Access database in the database directory.
Dreamweaver placed the connection info in the Connections folder an
d _mmServerScripts in the same directory.
In order to construct my local site to match the remote site,
I created a www folder on my local site and placed all of my HTML
files and supporting folders in it.
From various Adobe Tech Notes I have read, I was led to
believe my FTP host directory
Should be www/. However, when I do this and create a new web
page on my local site and upload it to my remote site, Dreamweaver
creates a new www directory inside of the one my host created on
the remote site and uploads the file to it instead of placing it in
the www directory my host created. Also, when I use F12 to test my
page in my browser I get a 404 page not found because Dreamweaver
placed a www in the page URL that shouldn’t be there and
after I remove it I’m able to see my page in my browser. My
URL prefix on my testing server site definition is:
http://I.P.number.html.
What am I not doing right?
Should I use www/ as my FTP host directory or leave it blank?
Also, what should my URL prefix be?
Thanks for your help.

What you need to do is set up so that in the remote server
you point to the
www level on the server, and don't replicate this locally.
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"Jim_Moore" <[email protected]> wrote in
message
news:[email protected]...
>I am confused about what information I should put in my
remote site
>definition
> info and testing server FTC Host directory text boxes.
My host placed 3
> directories: database, log, and www on my server and
Dreamweaver placed
> two
> directories, Connections and _mmServerScripts in the
same directory as the
> above 3. I have placed all of my site files, including
my home page and
> folders
> in the www directory and my Access database in the
database directory.
> Dreamweaver placed the connection info in the
Connections folder an d
> _mmServerScripts in the same directory.
>
> In order to construct my local site to match the remote
site, I created a
> www
> folder on my local site and placed all of my HTML files
and supporting
> folders
> in it.
>
> From various Adobe Tech Notes I have read, I was led to
believe my FTP
> host
> directory
> Should be www/. However, when I do this and create a new
web page on my
> local
> site and upload it to my remote site, Dreamweaver
creates a new www
> directory
> inside of the one my host created on the remote site and
uploads the file
> to it
> instead of placing it in the www directory my host
created. Also, when I
> use
> F12 to test my page in my browser I get a 404 page not
found because
> Dreamweaver placed a www in the page URL that shouldn?t
be there and after
> I
> remove it I?m able to see my page in my browser. My URL
prefix on my
> testing
> server site definition is:
http://I.P.number.html.
>
> What am I not doing right?
> Should I use www/ as my FTP host directory or leave it
blank?
> Also, what should my URL prefix be?
>
> Thanks for your help.
>
>

Create a Site Definition file with Visual Web part in Visual Studio

I tried to create a site definition file in Visual Studio 2013 and SharePoint 2013 by following the MSDN tutorial:
Walkthrough: Create a Basic Site Definition Project. Near the end, I added a virtual web part control to the site definition and registered MyWebPartControls in the site definition's default ASPX page as written in the MSDN tutorial:
Unfortunately, IntelliSense doesn't show any MyWebPartControls: tags, and VisualWebPart1 is highlighted with a warning “Element 'SMWebPart3' is not a known element. This can
occur if there is a compilation error in the Web site, or the web.config file is missing.”
Since it’s a warning, I went ahead to build and deploy the solution. However, when I used the site definition template to create a subsite, it returned a parser error:
Unknown server tag 'MyWebPartControls:TestSiteDef1.VisualWebPart1'
I spent half day researching and debugging, and finally solved the problem. The issue is on the registration line:
<%@ Register Tagprefix="MyWebPartControls" Namespace="TestSiteDef.VisualWebPart1" Assembly="$SharePoint.Project.AssemblyFullName$" %>
The $SharePoint.Project.AssemblyFullName$ is a replaceable parameter to provide values for SharePoint solution items whose actual values are not known at design time. Unfortunately, it does not find the right assembly name during the deployment. It should
be replaced by the Assembly’s Strong Name. Here is how I fixed the problem step by step:
In Solution Explorer, open the package node and double click Package.package
Click Manifest tab in the Package.package.
Copy the full assembly name in the package’s manifest. It may be similar like this:
Assembly="TestSiteDef,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=a300f1f2da8ae976"
Back to the site definition’s default.aspx page, replace the
Assembly="$SharePoint.Project.AssemblyFullName"
in the registration line with the copied text:
Assembly="TestSiteDef,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=a300f1f2da8ae976"
Change the Namespace from
Namespace="TestSiteDef.VisualWebPart1"
to
Namespace="TestSiteDef".
The line to register the web part in a site definition file will look like this:
<%@
Register
Tagprefix="MyWebPartControls"
Namespace="TestSiteDef "
Assembly="TestSiteDef, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=a300f1f2da8ae976"
%>
Clean, build and deploy the solution. It works like charm. (Note: the warning message on visual web part may still exist, but you can ignore it).

Assuming your .ascx.vb file is inheriting from the web part class, you can add the custom properties in the same manor (language syntax aside).
Be sure to use the attributes to correctly identify and scope the properties. (see:
http://www.sbrickey.com/Tech/Blog/Post/SharePoint_Attributes_for_Web_Part_properties)
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com

Unable to load Site Control File

Hello,
The background :
I am in the process of learning how to create a Management Pack for a distributed application in SCOM 2012 R2.For this, I picked our SCCM Site server to use as an example. So, in short, am writing a management pack for SCCM 2007 Discovery.
I know a management pack might already exist. I am trying to learn by using an architecture I'm familiar with so I need to create this from scratch.
In order to discover SCCM Site installed on a server, I decided to use the SMS WMI namespace. By reading the
SMS_ProviderLocation Instance, I am able to detect if the server has SCCM Site installed on it.
My next step was to find out where the SMS database is hosted. I found
ROOT\SMS\site_ABC\ namespace contains an instance of SMS_SCI_SiteDefinition where I can find the database name and server name which I can use to discover the other components of a distributed application.
The problem :
When I run the query Select * from SMS_SCI_SiteDefinition I get a generic error 0x80041001.
More Information reveals the following:
error description : " Unable to load site control file "
error code : " 2160198400 (0x80c20300) "
file name : " c:\qfe\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspsitecontrolextractor.cpp "
Now, I cannot find the QFE folder anywhere. The SCCM Site is working fine and the site_control_manager component has no errors. I can launch the SCCM console on that server without any errors and the site status messages do not contain any errors.
Can someone please help me out with "detecting" an installed instance of SCCM site server using WMI? Is the above error cause for worry for the SCCM part of my brain?
Thanks in advance for your guidance!

Thanks for your response Don!
The SMS_Site instance does not provide information of the database server and database name.
The funny thing is when I browse use wbemtest to connect to root\SMS\site_XXX and enumerate classes, i do not find
the SMS_SCI_SiteDefinition.
I find it when i enumerate recursively and can browse into the values. I'm not sure how could build a query against this now.
Can anybody with a test instance of SCCM 2007 check this and let me know please?
Everything you are looking for exist within WMI. You can use the documentation script as an example to get what you are looking for.
http://www.enhansoft.com/pages/downloads.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Issue in Custom Blog site definition based on SharePoint 2010 blog site definition after migrating the sites to SharePoint 2013 and site collection upgrade

I have created a custom blog site definition using SharePoint 2010 blog site definition with Configuration ID 31 in onet.xml (new value). This was working fine for SharePoint 2010.
We created new SharePoint 2013 farm and deployed the all Custom solutions in
14/15 folders. After migrating the sites to SharePoint 2013 using Content DB approach, site created previously using my custom definition are working fine.
But after running site collection upgrade these sites stop working. When I post a comment then comments not getting listed on post detail page. However comments are getting added to Comments List but
PostTitle column of Comment is not getting populated.
Also, when we create a new site in SharePoint 2013 using my custom blog template then that is also not getting provisioned. default.aspx and look-up between post and comment list are not working.
If any one has faced such issue then please share your findings and any solution to fix this.
Thanks in Advance :)

Hi ,
According to your description, my understanding is that the blog based on custom blog site definition didn’t work correctly after migrating custom blog site definition to SharePoint 2013.
If you customized the Onet.xml file in a previous version's site definition, you should modify some sections in the file to work in the current version, like <BaseTypes> and <ListTemplate> etc. More information, please refer
to the link below:
http://msdn.microsoft.com/en-us/library/office/aa543837(v=office.14).aspx
For that the PostTitle column of Comment is not getting populated, please try to modify the view, then compare the result.
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Site Definitions not working in CC 2014

Since the update, my site definitions are no longer working. I try to set up a new site, navigate to the correct folder and get the warning: 'site is inside the site "x"' This may cause conflicts … ' etc. The site folder isn't inside another site at all. I've even tried trashing the 'x' site folder, and Dreamweaver just throws up the same warning with the next alphabetically listed folder. Then I tried removing all the site definitions and setting up a new one, but I get the same problem. Is anyone else suffering?

In order to preview .php pages locally, you need a local testing server (Wamp, Xampp, Mamp). Is yours properly defined in DW CC? See screenshots.
Nancy O.

Preview versus Real View Not the Same, Site Definition Errors - Dreamweaver CS4

I am having trouble working on sites where it seems that Dreamweaver wants me to specify different file locations for various "includes" depending on whether I want to view the site as a preview (F12) vs. on a local test server vs. on the real website server. Note I am using Dreamweaver CS4 (ver. 10) on Windows, my local test server is Apache running via an Xampp installation on Windows, and my production server is also Apache, running at Hostgator. I am building a fairly basic html site using SSI via SHTML files, rather than PHP or a more sophisticated method. Here is what seems to be happening:
1. In my index.shtml file I call, for example, a subheader file called "header-nosub-menu.inc.htm." I have my site definitions set to "relative to document root." Using the insert -> SSI command, Dreamweaver links to the file with the following: My first problem is that, as specified, the subheader.menu.inc.htm file is not found and the preview gives me an error. I get the same error if i try to display the file on my local test server (http://localhost/domainname). However, if I upload the file to my production server, it seems to work fine. If I change the include command to: #include virtual="./includes/subheader.menu.inc.htm," by manually inserting the "./" to change the directory reference, then the file seems to work in all three situations Which is the correct directory specification, and why is Dreamweaver not generating it automatically?
While I can make the manual changes in the directory specifications, I am concerned that if Dreamweaver is making an error in this instance, it may generate more serious problems that are harder to find later.
2. The second issue seems to involve the Site Definition file configuration.I get an error message when I set up my site definition in what seems to be the correct way, specifically, using the following specifications:
Local Root folder: "C:\htdocs\domainname-dev\"
http address: "http://www.domainname/"
testing server folder: "C:\htdocs\domainname-dev"
url prefix: "http://localhost/domainname-dev"
The error message is: "The site url prefix for the testing server does not match the site url prefix specified in the http address for the site."
However, when I change the testing server url prefix to one that does not yield an error message ("http://localhost") I then have problems with the preview (F12) display. Specifically, instead of a preview request generating the following url: "http://localhost/domainname-dev/TMPm393xnclqu.shtml" I find that it generates the following: "http://localhost/TMPm393xnclqu.shtml" The so called incorrect definition seems to be the correct one, but why is Dreamweaver not recognizing it as such? Am I making a error somewhere else in my configuration?
I would appreciate any assistance that anyone here can provide,
Thanks,
http://localhost/

except for the Apache virtual host configuration, which I do not see a need for
I wasn't suggesting that you use virtual hosts (although I have defined about 50 virtual hosts on my own development machine). I was trying to understand the url you listed:
http://www.domainname/
Without a virtual host definition, that would have no meaning and could not point to anything, unless you simply were leaving off the TLD in the example. (.com, .net, etc)
I often use the PHP $_SERVER superglobal to define paths and handle differences between the development environment and the remote server environment. Examples:
DOCUMENT_ROOT: D:/ZendServer/Apache2/htdocs/website/ranch (machine path)
REQUEST_URI: /topic/calendar (url parameters)
SCRIPT_NAME: index.php
HTTP_REFERER: (the url of the script preceding the current script)
HTTP_HOST: (this is the domain name. It is very useful for distinguishing between the local and remote environments)
COMPLETE EXAMPLE:
echo "<a class='noPrint' href='".$_SERVER['HTTP_REFERER']."'>RETURN TO PREVIOUS PAGE</a>";

Which port number to use in remote site definition? [was:Help!]

I recently upgraded from Dreamweaver 8 to Dreamweaver cs6. I'm having trouble accessing my website because I dont know which port to choose. I never had to choose a port in Dreamweaver 8. How does one decide which port to use? Do you just keep picking random numbers until you get one that works?

Generally, the port next to your FTP address in the site definition will be 21 by default.
If that isn't working, you'll need to contact your hosting company to see if they use something else.

To decide save site as a template, web template or site definition

hi,
I have to create a generic site template which has few tabs in the home page and on click of these links/tabs
in this site template it will navigate to the sub sites created under that[this generic site template shud contain 3 sub sites -
[1 blog, 1 search center sub site, meeting workspace as tabs in the site template’s top navigation] and
a) 2 Doc Libs
b) 2 splists by default present in this site template [ most prob. its a team site template]
What should be the correct approach for creating this site template:
I have thought of implementing using:
a) save site as a template and upload this wsp into the solution gallery. and based on this site template
i will create new subsites. one problem i will be facing is that, mine is a publishing site template not team site template.
b) create a web template having the above subsites and doc libs and splists
c) last option is to create a site definition [ complex ]
which one should i choose, assuming that, there would be future changes from customer side in the
site template.like, adding a new splist, sp doclic or a new custom web part.
in that case, adding a new addtion to the already existing site template will not affect/reflect the already running
sites' content.
only those new sites which is created based on the updated site template would be having the new additions
implemented.
help is highly appreciated.

Hi,
From your description, the most concern you might have is that customers will have the requirements to add other components into their sites and created with them afterwards.
Since SharePoint 2010, it is recommended to take use of something like “a la carte” pattern to manage SharePoint sites. If there are needs to add sites, lists or other components,
we can make them as solution(.wsp) and deploy to our sites. By doing this, we will be more flexible and easier to manage the features and structure of sites.
So you can just create a site template with simple structure and deploy the solutions you want after sites created.
Here are two links about
Plan for sites and solutions for your reference:
http://technet.microsoft.com/en-us/library/cc789336(v=office.14).aspx
http://technet.microsoft.com/en-us/library/ee476993(v=office.14).aspx
What’s more, you can take a look at the two links below about
Custom Web Templates and Custom Site Definitions:
http://msdn.microsoft.com/en-us/library/office/aa979683(v=office.14).aspx
http://sharepointchick.com/archive/0001/01/01/site-definitions-vs.-webtemplates.aspx
Thanks
Patrick Liang
TechNet Community Support

Unable to Retreive Site definition - Endeca 11.1

Similar Messages

Maybe you are looking for