Closed (fixed)
Project:
Token
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Jan 2011 at 01:26 UTC
Updated:
3 Jan 2014 at 02:41 UTC
Jump to comment: Most recent
Comments
Comment #1
Freso commentedThis sounds very much like a timezone conflict.
Are all your articles dated a day off? If not, at what time were those off published?
What timezone are you in? (What timezone is the server in?)
Comment #2
wnet commentedNot all my articles are dated a day off. Only when i write an article from 00:00 till 08:00 ... after 08:00 everything its ok.
Server timezone is America/Chicago (GMT-6.00), my timezone is Europe/Athens (GMT+2.00).
Comment #3
lordgilman commentedSome more information:
I can reproduce this by setting Authored on: to midnight of the day I want. Pathauto will create the path with the previous day's date. To contrast, if you set the exact same time in Scheduler the publish/unpublish happens at the proper time and day in the site's timezone. (Drupal is configured to UTC -6, the server is on UTC)
This has been around for at least a year
Drupal's display of dates on nodes and elsewhere on the site doesn't have a problem with this timezone
Scheduler isn't confused by my timezone setup
Comment #4
Freso commented@wnet: What is the site's timezone? (Hint: Look at admin/settings/date-time (that's Administration -> Site configuration -> Date and time) If you have set a per-user timezone, please provide that as well (even if it's just +0200).
Comment #5
Freso commented@lordgilman: We know Pathauto isn't very intelligent when it comes to timezones. However, what would be the proper thing to do? There are several scenarios in which taking different times make sense.
Two quick ones OTTOMH:
1) If we're hosting a multi-blog/community site, it would make sense to store the aliases in the posting user's timezone.
2) A company website would most likely want to keep its blog etc. in the site's timezone.
Note that the aliases are different from the display dates, as they will generally be stored just once, while the display dates are generated during the construction of the page, every time the site is loaded. Thus, the alias won't be able to adapt to the currently logged in user, but has to have some set timezone to work from during creation, which is what it'll have to stick with. As you can see from the above example, what that timezone ought to be, is not always crystal clear.
If you can come up with a clever solution to this conundrum, we'd love to hear it. :)
Comment #6
adrian drupal commentedI am sorry to disturb this thread.
I'm starting with Drupal, and Pathauto, is definitely an essential tool around here.
I'm learning there are developers who contribute to Drupal, and I'm learning they have many limitations: time, money, space, and more.
The day added to the URL, from my point of view, it should not take time away from the contributors.
Date added to a URL, it is not advisable at this time, perhaps it was, but now it is not, for many reasons. You can write in your browser;
seo url date
Also combine the search and you'll discover some SEO experts on the matter, explaining the reasons for change.
I add this comment;
/*
The only posts I have with dated URLs are from the time I did not follow SEO. Since then I do not see the point. Why complicate the URL with irrelevant data?
*/
And I'll add this link.
http://www.seobook.com/do-you-put-dates-your-urls
If we have limited resources, not spend, and do not waste the time of the contributors.
It's just my point of view.
Comment #7
dave reidToken issue since Pathauto doesn't provide any date tokens.
Comment #8
dave reidAll date tokens provided by Token module use the system default timezone, and never use the user's timezone. Otherwise you may end up with inconsistent URLs with different days, even though the content was posted by two different users at the same time. Aliases are hard-coded once they are set. You can't 'adapt' them to work for the user's timezone.