|
Home > Archive > Microsoft Content Management Server > December 2006 > Last Updated Date - Only for published Postings
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 |
Last Updated Date - Only for published Postings
|
|
| vjammy 2006-11-13, 8:43 am |
| Hi,
We are facing a problem that is difficult to explain, nonetheless, let me
try my best.
Issue:
We have a CMS setup, where we have a staging server and a production server.
Everyday, changes are made to the staging server.
There is a batch job that runs every day to migrate these content changes to
the production server.
The production server is in the Read Only Configuration.
On the production server, we have an application called the Email alerts.
Whenever there are updates to (selected) webpages, an email is sent out to
the registered members.
Initially we were using the last modified date to check whether the page was
updated. But this caused a problem.
On staging, When any author updated the page, the page status changed to
Saved. Even though the page was not published, the last updated date changed.
After the daily content migration, the last updated date of the page in the
production also changed, and it triggered the email alerts. But, we wanted to
send emails for published pages only.
Then we tried another approach.
The logic was as follows: Loop through all the revisions. Take the revision
date for the most recent revision.
If there was no revision, then show 'Jan 1 1900'.
In production all the pages were showing the last revision date as Jan 1
1900.(Een pages those had multiple revisions in staging). Figured out that
the production is not storing any revisions.
Question:
If there are no revisions in production, how can we get the last updated
date for the published pages only? If we can get the updated date for the
published page only, then our problem will be solved.
Please help.
Thanks
Vivek
| |
| Stefan Goßner [MSFT] 2006-11-13, 8:43 am |
| Hi,
site deployment will only deploy the latest revision.
But every update through site deployment will add a new revision to the
updated posting.
The LastModified date will always show the date of the import. And as only
published postings are deployed using site deployment you should not get any
notifications for non-approved content as the non approved content is not
deployed using incremental site deployment.
With other words: you should be able to use the LastModified date for your
scenario on the production machine as there is only published content on the
production machine.
Could you please explain where your scenario differs from the explanation
above?
Cheers,
Stefan
"vjammy" <vjammy@discussions.microsoft.com> wrote in message
news:0E54154A-A573-45BF-B488-08996293F8A7@microsoft.com...
> Hi,
>
> We are facing a problem that is difficult to explain, nonetheless, let me
> try my best.
>
> Issue:
> We have a CMS setup, where we have a staging server and a production
> server.
> Everyday, changes are made to the staging server.
> There is a batch job that runs every day to migrate these content changes
> to
> the production server.
> The production server is in the Read Only Configuration.
>
> On the production server, we have an application called the Email alerts.
> Whenever there are updates to (selected) webpages, an email is sent out to
> the registered members.
>
> Initially we were using the last modified date to check whether the page
> was
> updated. But this caused a problem.
> On staging, When any author updated the page, the page status changed to
> Saved. Even though the page was not published, the last updated date
> changed.
> After the daily content migration, the last updated date of the page in
> the
> production also changed, and it triggered the email alerts. But, we wanted
> to
> send emails for published pages only.
>
> Then we tried another approach.
> The logic was as follows: Loop through all the revisions. Take the
> revision
> date for the most recent revision.
> If there was no revision, then show 'Jan 1 1900'.
> In production all the pages were showing the last revision date as Jan 1
> 1900.(Een pages those had multiple revisions in staging). Figured out that
> the production is not storing any revisions.
>
> Question:
> If there are no revisions in production, how can we get the last updated
> date for the published pages only? If we can get the updated date for the
> published page only, then our problem will be solved.
>
> Please help.
>
> Thanks
> Vivek
>
>
| |
| vjammy 2006-11-13, 8:43 am |
| Hi Stefan,
Scenario.
Page X - Last published on 1 Nov.
If the user changes Page X in staging on 15 nov, and the content is migrated
to production, in production the last modified date of page X changes to 15
Nov as well.
This is the behaviour that we experience.
Thanks
Vivek
"Stefan Goßner [MSFT]" wrote:
> Hi,
>
> site deployment will only deploy the latest revision.
> But every update through site deployment will add a new revision to the
> updated posting.
> The LastModified date will always show the date of the import. And as only
> published postings are deployed using site deployment you should not get any
> notifications for non-approved content as the non approved content is not
> deployed using incremental site deployment.
>
> With other words: you should be able to use the LastModified date for your
> scenario on the production machine as there is only published content on the
> production machine.
>
> Could you please explain where your scenario differs from the explanation
> above?
>
> Cheers,
> Stefan
>
> "vjammy" <vjammy@discussions.microsoft.com> wrote in message
> news:0E54154A-A573-45BF-B488-08996293F8A7@microsoft.com...
>
>
>
| |
| Stefan Goßner [MSFT] 2006-11-14, 7:27 am |
| Hi Vivek,
site deployment always changes the last modified date to the deploy date.
Not to the date on the staging machine.
This is by design.
You could use a custom property rather than the last modified date for your
purpose.
Cheers,
Stefan
"vjammy" <vjammy@discussions.microsoft.com> wrote in message
news:E270FB83-CDBE-4926-997D-8502F3E65235@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
>
> Scenario.
> Page X - Last published on 1 Nov.
>
> If the user changes Page X in staging on 15 nov, and the content is
> migrated
> to production, in production the last modified date of page X changes to
> 15
> Nov as well.
>
> This is the behaviour that we experience.
>
> Thanks
> Vivek
> "Stefan Goßner [MSFT]" wrote:
>
| |
| vjammy 2006-12-13, 1:32 am |
| Stefan,
Sorry for the delayed response but Can you please help to explain, how we
can use a custom property in this instance?
Do we update the custom property, "Custom last modified date" everytime
someone publishes the page?
Thanks
Vivek
"Stefan Goßner [MSFT]" wrote:
> Hi Vivek,
>
> site deployment always changes the last modified date to the deploy date.
> Not to the date on the staging machine.
> This is by design.
> You could use a custom property rather than the last modified date for your
> purpose.
>
> Cheers,
> Stefan
>
>
> "vjammy" <vjammy@discussions.microsoft.com> wrote in message
> news:E270FB83-CDBE-4926-997D-8502F3E65235@microsoft.com...
>
>
>
| |
| vjammy 2006-12-13, 1:32 am |
| Hi Stefan,
Let me explain the scenario one more time.
Scenario.
Page X - Last published on 1 Nov in staging and production.
If the user changes Page X in staging on 15 nov, and the page status is
"Waiting for Editor Approval" (the page is not published in staging) , and
the content is migrated
to production (via the daily content migration batch job) , in production
the last modified date of page X changes to 15 Nov as well.
I tried to check the Revision date in production, but there is only one
revision in production, as the production is a Read Only kind of a setup. I
tried many ways of using the revision date, but it did not work.
This is the behaviour that we experience.
Thanks
Vivek
"vjammy" wrote:
[vbcol=seagreen]
> Hi Stefan,
>
> Scenario.
> Page X - Last published on 1 Nov.
>
> If the user changes Page X in staging on 15 nov, and the content is migrated
> to production, in production the last modified date of page X changes to 15
> Nov as well.
>
> This is the behaviour that we experience.
>
> Thanks
> Vivek
> "Stefan Goßner [MSFT]" wrote:
>
| |
| Stefan Goßner [MSFT] 2006-12-13, 7:20 am |
| Hi Vivek,
items waiting for approval should not be deployed.
Please check the export and import report - is this item included?
Cheers,
Stefan
"vjammy" <vjammy@discussions.microsoft.com> wrote in message
news:15824277-204F-4FC8-8200-2072B8C0CD53@microsoft.com...[vbcol=seagreen]
> Hi Stefan,
>
> Let me explain the scenario one more time.
>
> Scenario.
> Page X - Last published on 1 Nov in staging and production.
>
> If the user changes Page X in staging on 15 nov, and the page status is
> "Waiting for Editor Approval" (the page is not published in staging) , and
> the content is migrated
> to production (via the daily content migration batch job) , in production
> the last modified date of page X changes to 15 Nov as well.
>
> I tried to check the Revision date in production, but there is only one
> revision in production, as the production is a Read Only kind of a setup.
> I
> tried many ways of using the revision date, but it did not work.
>
> This is the behaviour that we experience.
>
> Thanks
> Vivek
>
>
> "vjammy" wrote:
>
|
|
|
|
|