Thanks for the feedback. BTW PubKit is now published in the
Extras, so maybe future questions should be handled in its
support thread.
Re tags, you should be able to use any of the options type of TVs (radio, checkbox, single or multiple listbox). If you look at the sample blog, for instance, you’ll find checkbox implemented. The optionsbuilder class reads the TV type from its definition and generates a relevant SELECT tag for any of the above. If a radio button TV is working, just changing its type to
checkbox in the TV definition creates a checkbox set in the form. (You can then only have a single
&postid parameter, as I just found when testing that statement on the News section).
I know the template scheme is crude, but taking the example too far risks spending a lot of time to create a "blog in a box" that people might expect to use with a minor tweak here or there. An interesting challenge in its own right, but I’m more into creating tools for developers to customize to their own requirements at a slightly deeper level, so the example site is just a vehicle to deliver a reasonably consistent set of working materials.
Similarly, the restriction to unfriendly paths refers only to the example - I was spending too much time fiddling with getting the full paths right in all the subsidiary elements, then updating the installer SQL files for the resources involved (by hand, in Notepad++, what am I, some kind of masochist?). So the restriction in the example is an arbitrary one - I do use friendly URL paths with PubKit where it suits the site, as you can see in the News section of
Pog Academy of the PubKit demo site. You just need to be careful to keep all the FORM tags’ action attributes up to date.
KP
☆ A M B ☆
KP
