I tried renaming the one file to OO22_301.sfs and OO22_300.sfs; nothing happened. The openoffice-2.2.0.sfs shouldn't need renaming according to a post i saw by Barry, but it didn't work, either.
If you want the normal auto-mounting, you definitely need to rename them. Which name you need depends on whether you have Pizzapup 3.0 or 3.0.1. Check /etc/puppyversion.
Newer Puppies have an sfs loader program, so maybe they're different now, but the versions of Puppy I used for the last two Pizzapups (Puppy 2.12 and Puppy 2.14) don't. I don't know if it could be transplanted into Pizzapup.
If you have them named right, they
should be detected and mounted. How well they merge with the rest of the system is another story. I haven't used either, but just guessing, I'd say the OO22_215.sfs version will work best, at least with Pizzapup 3.0.1. That's because the module is for 2.15, which is really just a prettied up version of 2.14. The web_215.sfs module works partly for that reason (and partly because I made it, so I made sure it was compatible...)
I don't know which version the other module is made for. If it's too new or old, it might have dependency issues. And there also might be problems if it uses LZMA compression, which afaik Pizzapup is incompatible with.
Now, when you say nothing happens, what do you mean? We didn't have the fancy auto-icon thing back in Puppy 2.14, so Pizzapup doesn't either. So you'll need to actually look through the filesystem to see if it loaded correctly (or try starting it from the commandline). If it did work, you
should be able to run
fixmenus from the commandline to add it to the IceWM menu (IceWM won't need to be restarted, 'cuz it's cool).
Even though the desktop icons won't be added automatically, the images they'd use will still be included, unless they were stock icons from Puppy 2.15. Probably either in /usr/share/pixmaps or wherever the OpenOffice folder gets created.
Since the module itself is configured for the auto-icon system, you could probably port the system itself from 2.15 into Pizzapup. I don't know how it worked though. I think it scanned a directory to see if there are any files, and if so it would process them then edit /root/Choices/ROX-Filer/PuppyPin to add them.
Of course, muggins' method will work too, but it's more post-install oriented, rather than built-in capability. It's good for testing that Pizzapup can actually load the modules though, and then you can explore them to see where they install things easier.