On Thursday, June 27, 2013 1:29:43 AM UTC-4, Stuart Rackham wrote: > > > The 'updating published post' message means that the post already exists > (it has an ID), the update is performed by the editPost() method in the > wordpresslib library. blogpost does not set the creation date, that's > set by WordPress when the post is created and is fetched by the > getPost() method in the wordpresslib library. > > I often update my blog posts and have never experienced the problem (e.g > http://srackham.wordpress.com/2011/08/30/fossil-backend-for-asciidoc/ > was updated times but still retained it's create URL). I can only guess > that at some point WordPress is changing your blog creation date, as to > why, I have no idea. >
Hi Stuart, I think at least I've found the reason why the time went back -- If you keep doing blogpost.py post --force ... then you will notice that each time that you do it, the creat_time in the .blogpost file will decrease by a certain amount. It happens *each time*. I think you are lucky that it hasn't hit you yet, but I believe if you keep doing 'blogpost.py post --force ', sooner or later the date will change. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/groups/opt_out.
