Errors with run-periodic-tasks cron job

That's not an error, that's a warning.

Hi Mike,

While that is true, it does appear like the script is not executing properly, i.e., my understanding is that run-periodic-tasks will re-publish the main index and similar pages that I've set to be published via the publish queue.

However, those pages are not being republished.

Perhaps I'm missing something?

Phillip.

I'm using the "Action Streams," and I assumed those were equivalent to setting the "please republish me" flag, or what-have-you, that the run-periodic-tasks would check for. However, that could be a totally off-base assumption.

Maybe the better question is: How do I republish the main indexes regularly, regardless of whether they technically *need* to be republished?

Many thanks in advance,

Phillip.

I have seen many warnings that has to do with a few Action Streams, but never Flickr. These warnings seem to be attributed to the action stream in question, not Perl running on your setup.

If you are setting your Author Archives to be published with the publish queue I would suggest two things: maybe a less aggressive schedule, like every 15 min, and turning off Action Streams or just Flickr and seeing if the issue still persists.

But even if an action stream or two are not working properly, it should not stop the republishing of that archive.

Ken

Hi Ken,

Many thanks for the response. I guess I'm missing something. Basically, here's what I'm seeing:

* I post something to (let's say) Twitter
* I would expect that at some point the main index would need to get updated to display that Action (using the default Motion template set, where actions are shown "in context" or in the "timeline" of posts)

So, my question is: What can / should trigger the re-build of the main index?

Obviously, if I post a new MT entry, the main index gets republished. However, I'm far more often creating Actions than I am posting MT entries.

So, my sense was that I should frequently republish the main index using run-periodic tasks, as a way to show those Actions.

If I run run-periodic-tasks on the CLI, I don't get any errors, but the main index isn't updated either.

Thoughts?

Phillip.

And, actually, now that I look at bit closer, I see that I can run ./run-periodic-tasks --verbose

Which prints out:

TheSchwartz::work_once found no jobs

Which tells me that Actions don't create jobs. :-(

I'll go poke around in the Actions category of this forum, but -- heading back to my earlier question -- is there a way to force a frequent republish of the main index?

Phillip.

And I now see that Actions probably update on a schedule too... hrmmmm... more reading to do, clearly. :-(

Hi,

In your blog go to Tools > Plugins and go to the AS settings. Make sure it is set to enable rebuilding.

Here is an example of mine that is working. It is not in Motion, but it is using the latest build of AS 2.0. (currently MT 4.23)

http://bgviewsnetwork.com/dev/actions/

AS does run on its own schedule, I have never looked into what that is because it just has always worked for me.

Go to your profile > Action Streams. Many times you will see Actions in here that have not been published yet (but have been fetched). Do you see any there that are not published?

Go to Other Profiles, select them all, and click Update Now. That will take some time, depending on your server.

Go back to Action Streams and see if anything new showed up (if there was in fact anything new).

Hope that helps. Beyond that I really can't help you. I have not really dug into 4.25 yet, I have enough work getting our community site in 4.23 up and running. I have installed the beta 2 of Motion (http://bgviewsnetwork.com/motion/) and have messed with it, but I have yet to actually turn on run-periodic-tasks for it and test it out.

Ken

Hi Ken,

Many thanks for this. I had missed the "enable rebuilding" setting for the Action Streams module.

I'll wait to see what happens now. :-)

Phillip.