That is smarty code, not php code. You could try actually inserting PHP codes, though I have done a few tests of this myself and not had luck with wf-channel and embedded PHP (I think it treats the page contents as a string that gets passed all at once to the page renderer, rather than as code that gets executed.

PHP code would look like this, not the <? and ?> tags to start and end the PHP block:



The problem is that you seem to be referencing some template variables in your example code, and I'm not sure how you would expose that same info to PHP inside a page that has yet to be rendered by wf-channel.

If you didn't understand that last paragraph, then the short answer is, there may not be a way to do what you want, even if you can embed PHP code in wf-channel.

There might be another way to do what you want, through a custom block maybe or something like that.

Good luck,

--Julian

Formulize might be suitable for that. You can use it to make forms of any kind, and users can have the option of browsing their previous entries, or all entries by users who are in the same group(s) as them.

You can find it on dev.xoops.org here:

http://dev.xoops.org/modules/xfmod/project/?formulize

There is a forum discussion thread there that goes into some of the details about the different configuration options for forms, which might be important to you depending on what sort of behaviour/interaction you intend the users to have with the form. That thread is here:

http://dev.xoops.org/modules/xfmod/forum/forum.php?thread_id=1239&forum_id=745

The current release is a "release candidate" so not officially recommended for production systems. It should be quite stable (it's not a Beta), but it is not a final release either.

--Julian

According to the news story that was posted:

https://xoops.org/modules/news/article.php?storyid=1973

The XOOPS meeting will be February 26th, the Saturday. Myself, I'm arriving Friday and leaving Sunday.

--Julian

I'll be there.

Xoopermod is great.

Another way I have done what the initial post requires, where you just want to put a special block on a separate page of your site, is use WF-channel and simply make one blank page in it, turn off the link to us and refer a friend standard pages, and turn on the block I want for display in WF-channel only. This saves you having to make a blank module yourself just to display a block.

If you already have WF-Channel installed for other purposes on your site, or you want more than one section of your site handled this way, you can use our handy Perl script to clone WF-Channel. Details here:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=26041

Note: we have not tested the script with WF-channel 1.07. Details about compatibility (and a possible update to the script) will be posted shortly.

--Julian

Quote:

Oh, sorry. I thought the big change from Liase to Formulaire was the ability to create multiple forms, my mistake.

I would also suggest trying them both; there's really no better way to know what is best for you.

Quote:

Absolutely. It's like being a kid in a candy store.

--Julian

Quote:

Yes, Liase would be a good choice. If you want more than one form, Formulaire is worth considering (since Liase only gives you one form I believe).

If you want more complex form behaviours and reporting capabilities, then you should checkout Formulize, which is a module we have built on top of Formulaire. The biggest different for you may be that Liase/Formulaire only give you one form, people fill it in, and the data is e-mailed to you. People return to the form, it is blank, and they can fill it in again and send it to you, but that's all.

With Formulize, you could set things up so that when people go back to the form they would be able to see all the previous entries they have made (previous requests/bookings I suppose in your case).

Formulize would also let you setup reports on the entries users have made so you could easily see a list of all the bookings people have requested by age group, or location, or whatever other characteristics you're collecting in your booking form.

A release candidate version of Formulize has been released here:

http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1179

We believe it is a very stable release, with very few changes since the previous version which is in active use on a site with over 1000 registered users, but since this release has not been tested thoroughly we labeled it a release candidate.

It also has no docs and we feel strongly that an official release should have complete docs -- so we're getting around our own standards by making this an unoffical release.

There is a partial demo for Formulize at this site:

http://demo.freeformsolutions.ca

It's partial in the sense that you have no access to the form creation side (admin side) and you only get to play with two forms in the Form Menu. But they are two different kinds of forms (one is multiple entry which is probably closer to how you would want your bookings for setup, and one is single entry -- there are a few other options that control form behaviour too; if you want to try out the module for your site, we can answer more detailed configuration questions on the forums in the Formulize section of dev.xoops.org).

Good luck with your site,

--Julian

There is a partial demo here:

http://demo.freeformsolutions.ca

I say partial because it doesn't show you the form creation side. It shows two different forms, one is a form where you can make multiple entries and view the entries of other users in the same group as you. The other form is a single-entry form (conference registration is the example used -- you only register yourself for a conference once).

The first form, the multiple entries one, would be similar to what you want to do with the registry, so it might be a good example to check out. On the "View Entries" page you can select from a few different pre-defined reports that also give you an idea of how you could slice up the entries and present them back to users.

As I said, this is a partial demo, so keep in mind that it is possible to configure your form(s) so that each user would only see their own entry by default on the "View Entries" page (which is different from how the demo site has things setup), but each user could still have access to reports generated from the entire set of data from all users.

--Julian

It is possible to make something similar to this using Formulize, our form creation and reporting module, which you can download here:

http://dev.xoops.org/modules/xfmod/project/showfiles.php?group_id=1179

Formulize is not itself a vehicle registry module, but you can use it to create a form that contains all the information you wish to record about the bikes. You can then also create reports about the data that has been entered (such as all bikes newer than date X, bikes of such and such a make, all bikes newer than date X AND of such and such a make, etc).

Those reports can be made available to the users so they can use them to view the data in different ways.

Users can also have access to the report writing tools so they can search the data themselves, if you wish.

The version of Formulize that is currently available is a release candidate, but is believed to be very stable. Full documentation will accompany the final release. Full docs would help a lot in creating this kind of application with Formulize, but if you want to post questions in the Formulize Forum on dev.xoops.org, I will try to answer them.

--Julian

This would be a very handy feature; my company has looked at adding it too. We don't have an urgent need at the moment though. We have spec'd out a UI addition that would let you manage permissions on multiple groups at once, which would help deal with lots of non-hierarchical groups better. You can read that spec here (attached to this sourceforge posting):

http://sourceforge.net/tracker/?func=detail&aid=1017424&group_id=41586&atid=430843

As far as groups inheriting settings from other groups, the easiest way I have thought of for doing this would simply be to allow groups to have other groups as well as users as members. This would essentially eliminate the need to make people members of lots and lots of groups, you would only make people members of playersHalfLife, playersDOOM, etc, and then those groups themselves would be members of playersFPS, and so all the permissions attached to playersFPS would apply to the users who are members of playersHalfLife and playersDOOM without you having to manage complicated membership settings of multiple users in multiple groups.

In order to make that happen, you would have to modify a lot of the core libraries to do with checking permissions and group membership. It would be a complicated change, for sure.

No matter how you set about to change this, it would be complicated.

--Julian