It would be nice if the module could work on any formatted text field, not just book pages (i.e. node bodies).

This would be easier to import/export across sites than books and would mean that people have to deal with books less (people generally dislike books, though that's getting better).

Comments

greggles’s picture

Status: Active » Needs work

I just committed s5_textfield.module which works on node bodies and which I hope will eventually work on any text field in a node.

I also need to refactor it so that the functions that this and s5_book.module have in common are put into a third module that both depend on.

greggles’s picture

Component: Code » Code - s5_textfield

I just looked at refactoring and in fact the theme function is all that they have in common. So, maybe we don't want to bother with that.

I think the last thing now is coming up with a way to enable this for parts of the node other than the body. I've got two ideas:

First, provide a form where admins check off the formatted textfields which should be used for presentations. Then any node with that field will get a link added to the s5 export of that field.

Second, push the responsibility further to site admins to use something like custom links module to add which would link to node/NID/s5/field_name_to_use and then have this module respond to the field_name_to_use in the url.

The second is easier to code, the first is easier to admin. Thoughts? I feel like the second way isn't enough harder to make the first worthwhile.

greggles’s picture

Status: Needs work » Fixed

Well, now it's done. I'm sure there are some bugs related to this somewhere, but it works reasonably well, so yay for that!

greggles’s picture

Assigned: Unassigned » greggles
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.