|
Home > Archive > Microsoft Content Management Server > December 2004 > Extending Wb Author options
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]
| Author |
Extending Wb Author options
|
|
|
| I am looking at possbily converting a custom CMS app to CMS 2002. One
scenario that has come up is about how to extend the Web Author. I have read
several articles showing some fundamental things to do, however they do not
really address custom support for maintaing DB data.
For example, a manager wants to create a newsletter every month. Now users
will be able to see the current issue but will need to be able to view
archived issues. Now I realize at this point this info will be kept in a
separate database outside of CMS. The problem is where to plug in the ability
to create and manage the newsletters. Now the answer I have receive is to
extend the Web Author. I am familar with the console and its user controls.
What I would like to see is a new action appear only on a designated
template. Does it makes sense to create a copy of the existing console and
then extend it only for this template or to simply create a new user control
with the new action that exhibits the same behavior as the console during the
different edit modes?
Then the last question is when the action is clicked how do I show the
maintenace screen for the newsletter? Is it a popup or can I insert it into
the edit view page?
This has to be a typical scenario for a lot of people since this is common
to alot of existing .NET apps.
Thanks.
Bill
| |
| Stefan [MSFT] 2004-12-26, 5:47 pm |
| Hi Bill,
usually archived content can be kept in a separate channel if it should be
available through the web site - and not in a separate database. The content
can be created and managed manually with WebAuthor or in an automated manner
with Web Services or console applications.
To have a different console on a dedicated template, just create a copy of
the defaultconsole.ascx (and code behind), modify the copy and add this copy
to the template.
The dialogs to show need to be written in your ASP.NET application.
The following white paper shows details about how to integrate your own
dialogs:
http://msdn.microsoft.com/library/d....asp?frame=true
Cheers,
Stefan.
"BillW" <BillW@discussions.microsoft.com> wrote in message
news:294B703A-2026-497B-A8A2-01BDC8AF7D6F@microsoft.com...
> I am looking at possbily converting a custom CMS app to CMS 2002. One
> scenario that has come up is about how to extend the Web Author. I have
read
> several articles showing some fundamental things to do, however they do
not
> really address custom support for maintaing DB data.
>
> For example, a manager wants to create a newsletter every month. Now users
> will be able to see the current issue but will need to be able to view
> archived issues. Now I realize at this point this info will be kept in a
> separate database outside of CMS. The problem is where to plug in the
ability
> to create and manage the newsletters. Now the answer I have receive is to
> extend the Web Author. I am familar with the console and its user
controls.
>
> What I would like to see is a new action appear only on a designated
> template. Does it makes sense to create a copy of the existing console and
> then extend it only for this template or to simply create a new user
control
> with the new action that exhibits the same behavior as the console during
the
> different edit modes?
>
> Then the last question is when the action is clicked how do I show the
> maintenace screen for the newsletter? Is it a popup or can I insert it
into
> the edit view page?
>
> This has to be a typical scenario for a lot of people since this is common
> to alot of existing .NET apps.
>
> Thanks.
>
> Bill
>
| |
|
| Thanks for the input. But I think I needed to provide more info.
The manager has a list of newsletters, each with a detail page. So the user
would come to a page with the list and then select a link to view the
details. The twist is that the manager wants to be able to set a flag that
determines whether or not a particular newsletter is visible in the list.
This is how it is now in a separate app in a separate database. The manager
woud like a CMS page which he can edit some content but have the list be
dynamically generated. This is easy.
1) The problem is that the manager also wants to be able to access the
maintenace page for the newsletters from the edit screen. This is why I am
asking how to integrate the maintenance part into the CMS page. Does it make
sense to create a copy of the console and extend it OR to just create a
smaller custom user control that displays an action to edit the newsletters?
Either apporach sounds feasible but I was looking for best practice (if such
a thing exists).
2) How should the maintenance screen be displayed after selecting the
action? Should it be a popup or should it become visible on the edit screen
right below the console but above the normal edit screen?
I hope I am making this clear.
Thanks
Bill
"Stefan [MSFT]" wrote:
> Hi Bill,
>
> usually archived content can be kept in a separate channel if it should be
> available through the web site - and not in a separate database. The content
> can be created and managed manually with WebAuthor or in an automated manner
> with Web Services or console applications.
>
> To have a different console on a dedicated template, just create a copy of
> the defaultconsole.ascx (and code behind), modify the copy and add this copy
> to the template.
> The dialogs to show need to be written in your ASP.NET application.
> The following white paper shows details about how to integrate your own
> dialogs:
> http://msdn.microsoft.com/library/d....asp?frame=true
>
> Cheers,
> Stefan.
>
>
> "BillW" <BillW@discussions.microsoft.com> wrote in message
> news:294B703A-2026-497B-A8A2-01BDC8AF7D6F@microsoft.com...
> read
> not
> ability
> controls.
> control
> the
> into
>
>
>
| |
| Stefan [MSFT] 2004-12-26, 5:47 pm |
| Hi Bill,
MCMS has a property on each posting (hide when published) which could be
used for this feature to determine whether to include the posting or not -
MCMS does this automatically for you!. Or use the "important" flag or a
custom property if you would like to handle this manually
The maintenance part of the newsletter would be the web author console. This
is the smooth integration of the management part into the visible content.
In your situation I would suggest to create a customized console.
There is no real best practice as MCMS allows you to do this in muliple
different but all correct ways.
Also the question about whether to display the actions on screen or in a
popup depends on your business requirements. Whatever you prefer!
Cheers,
Stefan.
"BillW" <BillW@discussions.microsoft.com> wrote in message
news:392DECB3-6C10-4D59-867C-04E26224C86C@microsoft.com...
> Thanks for the input. But I think I needed to provide more info.
>
> The manager has a list of newsletters, each with a detail page. So the
user
> would come to a page with the list and then select a link to view the
> details. The twist is that the manager wants to be able to set a flag that
> determines whether or not a particular newsletter is visible in the list.
> This is how it is now in a separate app in a separate database. The
manager
> woud like a CMS page which he can edit some content but have the list be
> dynamically generated. This is easy.
>
> 1) The problem is that the manager also wants to be able to access the
> maintenace page for the newsletters from the edit screen. This is why I am
> asking how to integrate the maintenance part into the CMS page. Does it
make
> sense to create a copy of the console and extend it OR to just create a
> smaller custom user control that displays an action to edit the
newsletters?
> Either apporach sounds feasible but I was looking for best practice (if
such
> a thing exists).
>
> 2) How should the maintenance screen be displayed after selecting the
> action? Should it be a popup or should it become visible on the edit
screen[vbcol=seagreen]
> right below the console but above the normal edit screen?
>
> I hope I am making this clear.
>
> Thanks
>
> Bill
>
>
>
> "Stefan [MSFT]" wrote:
>
be[vbcol=seagreen]
content[vbcol=seagreen]
manner[vbcol=seagreen]
of[vbcol=seagreen]
copy[vbcol=seagreen]
http://msdn.microsoft.com/library/d....asp?frame=true[vbcol=seagreen]
have[vbcol=seagreen]
do[vbcol=seagreen]
users[vbcol=seagreen]
a[vbcol=seagreen]
to[vbcol=seagreen]
and[vbcol=seagreen]
during[vbcol=seagreen]
common[vbcol=seagreen]
| |
|
|
Great. I realize CMS allows you to do things in a lot of different ways,
just wanted to know if there were better ways. I am a believer of best
practices when possible.
It would be great to see some sort of best practices were available for CMS.
This is a critical issue when users are looking to migrate to CMS and then
have to decide migrate and/or integrate existing apps.
Thanks
Bill
"Stefan [MSFT]" wrote:
> Hi Bill,
>
> MCMS has a property on each posting (hide when published) which could be
> used for this feature to determine whether to include the posting or not -
> MCMS does this automatically for you!. Or use the "important" flag or a
> custom property if you would like to handle this manually
>
> The maintenance part of the newsletter would be the web author console. This
> is the smooth integration of the management part into the visible content.
> In your situation I would suggest to create a customized console.
>
> There is no real best practice as MCMS allows you to do this in muliple
> different but all correct ways.
>
> Also the question about whether to display the actions on screen or in a
> popup depends on your business requirements. Whatever you prefer!
>
> Cheers,
> Stefan.
>
>
> "BillW" <BillW@discussions.microsoft.com> wrote in message
> news:392DECB3-6C10-4D59-867C-04E26224C86C@microsoft.com...
> user
> manager
> make
> newsletters?
> such
> screen
> be
> content
> manner
> of
> copy
> http://msdn.microsoft.com/library/d....asp?frame=true
> have
> do
> users
> a
> to
> and
> during
> common
>
>
>
|
|
|
|
|