Hi Joe.

some users reported a condition that prevents Plog Posts to be published.

Their site has two language/cultures, one in Italian the other in English.

web(user).config contains the following settings:

    <add key="AllowMultipleSites" value="true" />
    <add key="UseRelatedSiteMode" value="true" />
    <add key="RelatedSiteID" value="1"/>
    <add key="RelatedSiteModeHideRoleManagerInChildSites" value="true"/>
    <add key="UseFoldersInsteadOfHostnamesForMultipleSites" value="true" />
    <add key="UseCultureOverride" value="true" />
    <add key="site1culture" value="it-IT" />
    <add key="site2culture" value="en-US" />

The site has been operative for two years and is regularly updated to the latest mojoPortal version.

Site1 blog works fine but users have only recently started to populate the Blog in Site2 (this is why they reported the issue now).

When they enter a new post in their news page (blog feature instance) they cannot publish it because any posts entered in the Blog are held as Unpublished Drafts.
Please note that "Is Published?" flag is checked and "Start Date" is correctly entered and lower than "Now".

I suspected that the cause could be related to datetime format of site2 (en-US mm/dd/yyyy instead of it-IT dd/mm/yyyy) that may considers 10/06 as October 6th instead of the expected June 10th, but database contains the correct information and the Unpublished Blog Posts List correctly shows "To Be Published Friday, June 10, 2011 12:15:00 PM"

Any Clue ?

P.S: In the past, site settings where initially set to activate content workflow but at the moment that feature is disabled. I dont'know if this has anything related to the issue.

mojoPortal Version 2.3.6.6 MSSQL
Operating System Microsoft Windows NT 6.0.6002 Service Pack 2
ASP.NET Info v2.0.50727 Running in Full Trust
Server Time Zone ora legale Europa occidentale
Server Local Time (GMT 2) 6/10/2011 2:00:11 PM
Greenwich Mean Time (GMT/UTC) 6/10/2011 12:00:11 PM

Hi Joe,

the time setting on the server is ok but, thanks to your tip, I had a second check on all time settings.

The issue was caused by "Time Zone" site setting of site2.

It was still set on the default (GMT - 5) US Eastern Time.

I completely forgot that this parameter is site related.

Regards.

Diego