How to use build_file callback

[nakedsushi]

According to this page, there's a build_file callback:
https://github.com/movabletype/movabletype/blob/f02afa4e1ed554ebc3c265d3856fb09e1666eb00/lib/MT/Callback.pod

When writing an MT plugin that is triggered by that callback, how should the callback be used? For example, this in my config.yaml doesn't seem to work:

callbacks:
 build_file: $MyPlugin::MyPlugin::method_to_call_after_build_file

Is this a bug? When I create an entry and publish it, it doesn't seem to call my plugin. Same for updated and editing an existing entry.

[ghost]

@nakedsushi
Your code looks good to me. I checked that build_file callback had been called in the following plugin on MT r.4208.

https://gist.github.com/miniuchi/4b0a2703a088b33c515be2f6fdc8189e

Please check the followings.

• ’$MyPlugin::MyPlugin::method_to_call_after_build_file’ has wrong name (package name, subroutine name, etc.)
• You are using ‘Dynamic Publishing’
• There is no archive mapping for entry. (this may occur when you are using ‘Mont-Blanc’ theme)

[ghost]

I checked that build_file callback had been called when creating an entry via Data API.

[nakedsushi]

Oh interesting, I didn't know that it only gets called when the entry page is set to "Dynamic Publishing." We have it configured to static publishing, so that may be why build_page never gets called. Thanks!

[nakedsushi]

If we have our configuration set up to statically publish, with archive mapping turned ON, is there a way to use that callback? Or my bigger question is, is there a callback I can use to trigger a plugin's method after an entry's archive mapping is created in the file system?

[ghost]

@nakedsushi

Please check the followings.

Sorry, this is a check list of wrong conditions. You can use build_file callback when using “Static Publishing”.

Oh interesting, I didn't know that it only gets called when the entry page is set to "Dynamic Publishing." We have it configured to static publishing, so that may be why build_page never gets called. Thanks!

Are you using build_page callback, not build_file callback?