What browser are you using? I think this is a bug in the HTML that is only rearing it's head in a particular browser, maybe IE 7?

Here's the thing, the calendar '...' buttons are listed as "type=reset", and the behaviour you're describing is exactly what you'd expect a reset button to do in a form. But the onclick event should (and normally does) override the behaviour of the reset button. Instead, the button simply does whatever the javascript function returns, which should be the typical calendar that we know and love.

However, in your case, the javascript is failing. This could be because your site has a problem with accessing the javascript function that shows the calendar (did you put the <{$calendarjs}> smarty tag into your main page template when you installed the datebox patch?).

Or it could be that the browser you are using is deciding that the 'reset' status of the button should override whatever onclick events the button has.

Or both.

So the first thing to do is make sure the javascript function is available. So make sure that <{$calendarjs}> is in your main page template. Right before the <title> tag is recommended.

If you do that, check the page source after going to the form, to make sure the change is picked up. You should have a lot of javascript code near the top, including a line like this:

function showCalendar(id) {

If you don't have that even after making the change, make sure your templates are being read properly and you don't have any cached or compiled templates or other files getting in the way. Check the FAQ on this site for help making sure changes are reflected in your live site.

If you do have that javascript in the page now, and you click the button and you still get the reset behaviour and not the calendar behaviour, then you need to fix that HTML bug in the date select box, which should never have been written that way in the first place in my opinion, I'm sorry we didn't correct it when we made our datebox patch.

Anyway, go to class/xoopsform/formtextdateselect.php and change the text near the bottom that says type='reset' to type='button'.

If you do that, and then try to click the calendar button, I sure hope it works!

Make sense?

--Julian

Using the Pageworks module, which works together with Formulize, you can use PHP to make any kind of page you want drawing on data in a form. You can actually template the output of a Pageworks page if you call the XOOPS template object in your Pageworks page, but that's getting a little complicated, and isn't necessary.

Using Pageworks is not the same as having a fully templated system, we know. But it does give you some more flexibility if you want to present data, or forms, in very customized ways.

Please post in our area on dev.xoops.org if you run into any technical issues trying to implement your application with Formulize. You can access that area here:

http://www.freeformsolutions.ca/formulize

--Julian

Hello,

I don't think the problem you're having with the showCalendar javascript function is related to the notice about the displayCalendar PHP function.

Have you installed the datebox patch that we distribute with Formulize? It changes the behaviour of XOOPS dateboxes slightly.

What exactly happens when users click the button? All fields in the form go blank? Or just calendar fields? What version of Formulize are you using?

--Julian

Quote:

Also, keep in mind, XOOPS site on top of a tall stack of software. If PHP on your server is configured to log error messages, but not display them, then that too will affect how you are able to track down issues (check log files instead of seeing errors displayed on screen for instance).

Your problem is most likely some interaction effect of XOOPS with all the settings in the operating system and database version and PHP version and .ini settings and who knows what else on your new server.

When we moved from one server to another a long time ago, we had some problems because the root folder structure on the old server was something like /foo/bar/www/xoops and on the new server it was /bar/foo/www/xoops. Once we changed that in the mainfile.php for our XOOPS sites, everything worked just fine. That kind of issue has nothing to do with XOOPS per se, it is caused by not knowing enough about how your server is configured, and what implications that will have for your site.

--Julian

FYI: I have put a detailed reply here on dev.xoops.org:

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

--Julian

Quote:

Good point! Does it not respond to changes made to "the top page"? But I guess you want some blocks on that page setup differently to how the top page looks. Hmmm. Sounds like a core change may have to be made. Anyone more knowledgeable about the blocks system have anything to add?

--Julian

Quote:

Formulize plus Registration Codes is a completely different approach from hacking the core files. It uses custom versions of four core files, register.php, edituser.php, userinfo.php and the system template that corresponds to userinfo.php. Those custom files integrate with a form you create in Formulize, which replaces most of the standard user profile form, except for the basic required things like username, password, etc.

Quote:

No, sorry.

Quote:

You could make a page using the Pageworks module, and have whatever you want on it, and even integrate that with a hidden element of the registration form or something fancy. But no matter what, that's work, it's not a built in feature. You would have to alter the layout of the userinfo.php and the edituser.php pages in order to support a second page too.

Quote:

Not without a fair bit of hacking. Formulize+Registration Codes is built around a single page metaphor, all the registration info is on one page/form. Supporting multi-page registration forms would be a nice addition though, and shouldn't be too hard since there is now a way to display Formulize forms as multiple pages (via a new function available when using Pageworks).

So I'm sorry to say that it sounds like most of what you need is highly customized, with no "out-of-the-box" support for what you're really after. But if you do use Formulize, feel free to post on dev.xoops.org in the Formulize area if you have usage questions.

Good luck, happy holidays,

--Julian

Hello, I believe you cross posted this to dev.xoops.org, and there is a response there:

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

--Julian

Quote:

Hello,

You may be right about this. Certainly Formulize does not have support for file upload elements, so that's probably a big problem for you right there. It shouldn't be too hard to add them back in, but whenever we need to upload files to a site, we usually do that through wf-downloads, so there hasn't been a need to do this in Formulize for us.

And your other field is a count, which changes based on other events in the website? If so, that is also sort of difficult, but only in that you would have to write code in the right place to increment the counter when necessary, and you would have to do that no matter what implementation method you used.

Formulize does have a function called "writeElementValue" that you can use to overwrite the value of an element in an existing entry. So maybe that would work for you.

If you have any questions about using Formulize, please check out our area on dev.xoops.org, where you can also download the latest versions. It's conveniently accessible through this URL:

http://www.freeformsolutions.ca/formulize

--Julian

Hello,

Thanks for the plug Stefan. Our module, Formulize, could be used to do this. You would create a form for your widgets, with two textboxes as you describe. Then users can fill in the form multiple times if necessary (for multiple widgets). You would not need to manually do anything in the DB, since Formulize does that for you.

To display the counts, you could write a page in the companion "Pageworks" module, where you can use a function called
"getData" to gather information from your form. You can then display that data however you need to in the page.

To display the page as a block, you just create a PHP block in XOOPS with this code in it:

$page=1;
include XOOPS_ROOT_PATH . "/modules/pageworks/index.php";

And that's about it. Obviously there's more details in how you actually use the getData function and so on, but that's probably the only tricky bit of this process. The creation of the form and having users fill it in is all "out-of-the-box" functionality that Formulize provides.

If you have any questions about using Formulize, please check out our area on dev.xoops.org, where you can also download the latest versions. It's conveniently accessible through this URL:

http://www.freeformsolutions.ca/formulize

--Julian