|
Home > Archive > Microsoft Content Management Server > May 2007 > SiteManager
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Is there any MS or 3rd party patch/software we can install to enhance the
existing SiteManager interface? It seems there could be so much more
functionality on the UI than what comes out of the box.
| |
| Shady Khorshed 2007-04-06, 7:16 pm |
| Hi Ara,
you can try this
http://www.codeproject.com/aspnet/MCMSManager.asp
Regards,
Shady Khorshed
"ara99" <ara99@discussions.microsoft.com> wrote in message
news:E14207AF-012A-4280-9D05-121737414E6B@microsoft.com...
> Is there any MS or 3rd party patch/software we can install to enhance the
> existing SiteManager interface? It seems there could be so much more
> functionality on the UI than what comes out of the box.
>
>
| |
| Stefan Goßner [MSFT] 2007-04-10, 7:16 am |
| Hi,
the answer is no.
Actually you should only use Site Manager for the actions really required.
Everything else should be done using Web author.
Cheers,
Stefan
"ara99" <ara99@discussions.microsoft.com> wrote in message
news:E14207AF-012A-4280-9D05-121737414E6B@microsoft.com...
> Is there any MS or 3rd party patch/software we can install to enhance the
> existing SiteManager interface? It seems there could be so much more
> functionality on the UI than what comes out of the box.
>
>
| |
|
| Hello,
I'm sorry but I don't understand "Everything else should be done using Web
author." Web author wouldn't allow us to rename resoure items, determine
where where a resouce is (if it was uploaded from an authors desktop)... on
and on. It just seems like SM could be so much more robust. 99% of the
fixes on this board appear to be for programmers, but having to access the
API seems a bit much where a GUI tool should be more than enough to
handlethings.
Thanks,
Ara
"Stefan Goßner [MSFT]" wrote:
> Hi,
>
> the answer is no.
> Actually you should only use Site Manager for the actions really required.
> Everything else should be done using Web author.
>
> Cheers,
> Stefan
>
>
> "ara99" <ara99@discussions.microsoft.com> wrote in message
> news:E14207AF-012A-4280-9D05-121737414E6B@microsoft.com...
>
>
>
| |
| Stefan Goßner [MSFT] 2007-05-02, 7:17 am |
| Hi Ara,
I ment everything that can be done with the API should not be done with site
manager.
It was planned to remove site manager completly with CMS 2002 - but due to
time constraints not all functions have been implemented in the API and Site
Manager had to be shipped.
Cheers,
Stefan
"ara99" <ara99@discussions.microsoft.com> wrote in message
news:F1B8EBB3-5547-44D4-B69B-094AACEA249B@microsoft.com...[vbcol=seagreen]
> Hello,
>
> I'm sorry but I don't understand "Everything else should be done using Web
> author." Web author wouldn't allow us to rename resoure items, determine
> where where a resouce is (if it was uploaded from an authors desktop)...
> on
> and on. It just seems like SM could be so much more robust. 99% of the
> fixes on this board appear to be for programmers, but having to access the
> API seems a bit much where a GUI tool should be more than enough to
> handlethings.
>
> Thanks,
> Ara
>
> "Stefan Goßner [MSFT]" wrote:
>
| |
|
| Thanks very much Stefan. Can you explain the logic behind moving away from a
GUI and only to API? An API means only coders can implement change, a robust
site manager means anyone can.
Our model is we have non-techie's managing the CMS via site manager and our
offshore dev team builds templates and functionality. However, we would
like to be less dependent on them for day to day management and maintenance.
Does this also mean that there is no site manager (gui) in Office 2007 CMS?
"Stefan Goßner [MSFT]" wrote:
> Hi Ara,
>
> I ment everything that can be done with the API should not be done with site
> manager.
> It was planned to remove site manager completly with CMS 2002 - but due to
> time constraints not all functions have been implemented in the API and Site
> Manager had to be shipped.
>
> Cheers,
> Stefan
>
> "ara99" <ara99@discussions.microsoft.com> wrote in message
> news:F1B8EBB3-5547-44D4-B69B-094AACEA249B@microsoft.com...
>
>
>
| |
| Stefan Goßner [MSFT] 2007-05-09, 1:20 pm |
| Hi,
the plan was to provide all the featues in webauthor using console actions.
So you would have a unified administration and content creation tool in a
browser which the need to install a legacy application on a client system.
MOSS does this: no separate UI installation.
Cheers,
Stefan
"ara99" <ara99@discussions.microsoft.com> wrote in message
news:BD40B7D1-FE44-4E39-B302-A614FEAF11F2@microsoft.com...[vbcol=seagreen]
> Thanks very much Stefan. Can you explain the logic behind moving away
> from a
> GUI and only to API? An API means only coders can implement change, a
> robust
> site manager means anyone can.
>
> Our model is we have non-techie's managing the CMS via site manager and
> our
> offshore dev team builds templates and functionality. However, we would
> like to be less dependent on them for day to day management and
> maintenance.
>
> Does this also mean that there is no site manager (gui) in Office 2007
> CMS?
>
> "Stefan Goßner [MSFT]" wrote:
>
| |
|
| Thanks again Stefan. What is MOSS? Can this work with MCMS 2002 to provide
a "unified administration and content creation tool"? Is this difficult to
get up and running - i.e., is there coding involved?
Ara
"Stefan Goßner [MSFT]" wrote:
> Hi,
>
> the plan was to provide all the featues in webauthor using console actions.
> So you would have a unified administration and content creation tool in a
> browser which the need to install a legacy application on a client system.
>
> MOSS does this: no separate UI installation.
>
> Cheers,
> Stefan
>
> "ara99" <ara99@discussions.microsoft.com> wrote in message
> news:BD40B7D1-FE44-4E39-B302-A614FEAF11F2@microsoft.com...
>
>
>
| |
| Stefan Goßner [MSFT] 2007-05-10, 1:23 pm |
| Hi Ara,
MOSS is Microsoft Office SharePoint Server. So Office 12 which you asked for
below.
Cheers,
Stefan
"ara99" <ara99@discussions.microsoft.com> wrote in message
news:05FDAF32-C4F4-49DC-A2A2-758B9041CA7B@microsoft.com...[vbcol=seagreen]
> Thanks again Stefan. What is MOSS? Can this work with MCMS 2002 to
> provide
> a "unified administration and content creation tool"? Is this difficult
> to
> get up and running - i.e., is there coding involved?
>
> Ara
>
> "Stefan Goßner [MSFT]" wrote:
>
|
|
|
|
|