I just got off the phone with MS and I am not a happy camper. The usual practice with large scale enterprise server software is to set up a live server and a test server. Development work on the test server is bundled over and installed on the live server when testing is complete. MS is telling me you can't do this with Sharepoint. IMO, I ought to be able to fully configure a sub area and move it over in one shot, including all the sub areas beneath it, over to the Live server. At the very least, I should be able to move a page over. They say I can't do it. Am I talking to someone with their head placed firmly between their cheeks or is this on the level? How are you doing testing?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
No test server?
- Thread starter vbajock
- Start date
dlongnecker
MIS
Hehe...
Yes and no... as with most Microsoft products. In regards to complete Areas, I haven't found a way to develop those and move those around because, they don't "exist"... rather are a series of database calls and .NET coding.
In regards to sites, you have some flexibility... though I use that term liberaly.
You can develop a site on one server, back it up in FP2003 into a "backup file", move that file to the production box and restore it... but it's glitchy. It won't add it into the Sites Directory, you'll need to do that yourself, but it'll allow you to develop on a separate box. I've had our MS guy down here and almost strangled him when he said that I couldn't simply move the sites around.
I have tried this... and it wasn't pretty... and I didn't even changes boxes!
I tried moving one site from, say \\portal\sites\mis\test1 to \\portal\sites\random\test1 and spent a good hour fixing all the odd links that SPS makes absolute (for some very sick reason).
The other issue I came up with is in regards to the indexing. I had to go through and totally kill the search index and reindex the entire portal because the site pointed to the old location giving a 404 error and, for a time, displayed both entires (severly confusing our users).
I'd say, out of the box and without some creativity, that SPS is designed to be modified live... programmers everywhere cringe.
On a side note and a word of caution... these are seen and treated as network shares... delete a file accidently? There is _typically_ no undo. For some reason, the database information doesn't seem to store undo information. I've trashed a site pretty bad and ended up just scavinging the information and recreating it.
If you do want to create sites outside the normal portal, what I suggest is keeping that site hidden and locked until you're ready to release it to the individual/public. That'll give you the opportunity to work, but keep wandering eyes out of it.
Sadly, this is truly a case where business practices must mold to how Microsoft does business--not vice versa. (;_
-David
---
David R. Longnecker
Web Developer
CCNA, MCSA, Network+, A+
Management Information Services
Wichita Public Schools, USD 259
Yes and no... as with most Microsoft products. In regards to complete Areas, I haven't found a way to develop those and move those around because, they don't "exist"... rather are a series of database calls and .NET coding.
In regards to sites, you have some flexibility... though I use that term liberaly.
You can develop a site on one server, back it up in FP2003 into a "backup file", move that file to the production box and restore it... but it's glitchy. It won't add it into the Sites Directory, you'll need to do that yourself, but it'll allow you to develop on a separate box. I've had our MS guy down here and almost strangled him when he said that I couldn't simply move the sites around.
I have tried this... and it wasn't pretty... and I didn't even changes boxes!
I tried moving one site from, say \\portal\sites\mis\test1 to \\portal\sites\random\test1 and spent a good hour fixing all the odd links that SPS makes absolute (for some very sick reason).
The other issue I came up with is in regards to the indexing. I had to go through and totally kill the search index and reindex the entire portal because the site pointed to the old location giving a 404 error and, for a time, displayed both entires (severly confusing our users).
I'd say, out of the box and without some creativity, that SPS is designed to be modified live... programmers everywhere cringe.
On a side note and a word of caution... these are seen and treated as network shares... delete a file accidently? There is _typically_ no undo. For some reason, the database information doesn't seem to store undo information. I've trashed a site pretty bad and ended up just scavinging the information and recreating it.
If you do want to create sites outside the normal portal, what I suggest is keeping that site hidden and locked until you're ready to release it to the individual/public. That'll give you the opportunity to work, but keep wandering eyes out of it.
Sadly, this is truly a case where business practices must mold to how Microsoft does business--not vice versa. (;_
-David
---
David R. Longnecker
Web Developer
CCNA, MCSA, Network+, A+
Management Information Services
Wichita Public Schools, USD 259
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question