I am getting a new error when running the ./tools/run-periodic-tasks script from the command line to initiate the action streams plugin (or scheduled post for that matter). When I execute the command in terminal the following is the result (repeated a few times):
Use of uninitialized value in unpack at lib/MT/Util.pm line 103.
Argument "" isn't numeric in subtraction (-) at lib/MT/Util.pm line 104.
Argument "" isn't numeric in integer ge (>=) at /System/Library/Perl/5.8.6/Time/Local.pm line 98.
Argument "" isn't numeric in integer addition (+) at /System/Library/Perl/5.8.6/Time/Local.pm line 67.
Argument "" isn't numeric in integer addition (+) at /System/Library/Perl/5.8.6/Time/Local.pm line 123.
Argument "" isn't numeric in integer multiplication (*) at /System/Library/Perl/5.8.6/Time/Local.pm line 123.
Argument "" isn't numeric in integer multiplication (*) at /System/Library/Perl/5.8.6/Time/Local.pm line 123.
Now I do notice that my action streams are updated in MTOS profile page but my blog is not rebuilt. I do have the blog plugin setting checked. If I run the script again immediately nothing happens. If I wait about 15 minutes I receive the error.
Hi, jerm!
These messages are warnings that appear if events are created without the proper timestamps. I've worked on improving the handling of these events, but the bug is not quite fixed yet. If you want, you can check in your database in the mt_profileevent table for rows that are missing created_on values; I think that's the problem.
However, as they are only warnings, I don't think they should be preventing the publishing of your blog. If you publish your blog's indexes manually from inside the MT application, do they publish successfully? Are there messages in the system Activity Log about it?
Hey Mark,
I looked in my db and all the rows have a profileeventcreatedon if that helps any.
When I publish my blog's indexes everything works fine with no errors then or in the Activity Log. This is how I am currently publishing all my action streams ... running the script then refreshing my indexes.
I currently have action streams for digg, twitter and a link to last.fm.
FWIW, Mark, we're seeing these warnings on movabletype.org as well.
I was getting the same problem and traced it to some of my feed items having an empty modified_on date. Specifically, my links from del.icio.us.
I changed line 497 of Plugin.pm to this:
my $time = $event->modified_on || $event->created_on; local $arg->{ts} = MT::Util::epoch2ts( $ctx->stash('blog'), MT::Util::ts2epoch(undef, $time) );That stopped the errors.
Many of these timestamp fixes are in the trunk version of the plugin, if you're able to check it out of the subversion repository. They'll be in the next packaged release of the plugin as well.