I've said it before and I'll say it again - that Gary Lapointe is a freaking
genius.
This simple command could have saved me two days of grief and the whole
operation lasted about 2 minutes.
stsadm -o gl-convertsubsitetositecollection
-sourceurl https://lei-sppdev-01/ict/
-targeturl https://lei
Hi All,
I have an internet facing site (MOSS), with an asp treeview which uses
GlobalNavSiteMapProvider as its site map provider.
The treeview is visible when a user logs in, but not to a anonymous
user. (anonymous user is enabled on the site)
Is it possible to display the treeview to
Hi Karl,
Spent a long time working with VS2008 workflows under MOSS last year, and
remember experiencing something similar. I'll try and find my notes on this
stuff later on to confirm - but I seem to remember that this link provided
"an approach" to this issue:
http://geeks.netindonesia.ne
Hi Stefan,
Thanks. This would probably explain why I'm having so much difficulty. So if
this was straight WSS site with no customisations I would have no problem
importing it to the site collection root?
Per Ajay's suggestion, if I disable the Publishing feature first would I then
be able to
Hi Folks,
We're experiencing an issue with a custom workflow designed in VS2008
see below for details:
Summary of Issue:
Workflow running on a Form Library in SharePoint. The workflow creates
Tasks on the default Task list in the Site. No fields have been edited
from default settings on t
I saw your post.. I am thinking couldn't you have deactivated the feature
and then exported to save all the trouble you went through..
On Wed, Jun 17, 2009 at 5:30 PM, Jeremy Thake wrote:
> If you struggle with that, I’ve actually got a post to remove the
> dependencies from the file ;-)
>
>
>
Hi Paul,
what you are trying to achieve is unsupported.
See here for details:
http://blogs.technet.com/stefan_gossner/archive/2009/05/27/limitations-of-stsadm-o-export-import-related-to-publishing-sites.aspx
Cheers,
Stefan Goßner
Escalation Engineer | CSS SharePoint Products and Technologies | M
If you do want to tidy up the Internal Names you can always create a new list
with the correct columns and migrate the list items across using PowerShell etc.
You could use a tool like SPSource to reverse engineer the List Template schema
, modify the Internal Names using Find and Replace (be ca
