Blog post publication date and profile time zone setting. This is on Telligent 9.2.

As this is job service related, it uses the server's time. Work was done for version 10 to more reliably standardize on UTC internally everywhere with conversions to/from user time, so this should actually work as you're expecting.

Michael Monteleone we have a scenario that we deem as a bug.  I don't believe it is addressed in 10.0.  Here is the scenario: our server is set to Hawaii time.  We have a user who's computer time is set to Hong Kong (18 hours ahead of Hawaii).  When he creates a blog post, the "Publication Date" under the "Options" tab is set to the user's current computer date/time.  When he creates the post, it does not show up in the blog post list widget.  When an admin were to look at the list of blog posts in the Control Panel, it is set to "Scheduled".  We believe that it is NOT the correct behavior because the user's intention is to create the post now.  But because he is in a timezone that is ahead of the server time, the post will not be displayed until 18 hours later.

Michael Monteleone we have a scenario that we deem as a bug.  I don't believe it is addressed in 10.0.  Here is the scenario: our server is set to Hawaii time.  We have a user who's computer time is set to Hong Kong (18 hours ahead of Hawaii).  When he creates a blog post, the "Publication Date" under the "Options" tab is set to the user's current computer date/time.  When he creates the post, it does not show up in the blog post list widget.  When an admin were to look at the list of blog posts in the Control Panel, it is set to "Scheduled".  We believe that it is NOT the correct behavior because the user's intention is to create the post now.  But because he is in a timezone that is ahead of the server time, the post will not be displayed until 18 hours later.

And so I am clear, you tested this in 10?

To be clear I ask because in 10, everything is based off of Universal Time, not server time

Yes, it was tested in 10.

So I just tested this, User A profile in Hawaii writes a post and publishes, User B in hong Kong TZ for profile views and the post is visible.

Note that computer time, especially in web scenario does not come in to play

You will need to test the scenario backwards:

Have User A (with computer timezone in Hong Kong) writes a blog post and publishes.  Nobody regardless of what timezone can view the blog post.

This was tested in 10.0.0.4689.  But you can test this in your latest version to see if this is a problem.

Out of Curiosity, what is your communities timezone set to vs what the actual web server is set to at the OS level?

Actual web server is set to Central Time Zone.  Community timezone (in Control Panel) is also set to Central Time Zone (UTC-6).

Ok thanks, I thought I had it repro'd for a moment, but even running in reverse it seems to be working so I will keep looking

This is a screenshot of me posting a blog post.  It says it will be posted tomorrow.

I have found something, it appears this was a known issue that was fixed in 10.1, which could explain alot on my side.   I will be reviewing the bug in question some more but it looked pretty close to what you described.