This module is too cute. I the 2.2 version of Recette installed in XOOPS 2.4.7.3 (I also have News 1.44 which will stay!). I was about to publish a recipe, ok. But could not add anything to the ingrediants list. In fact, that tab in the module brought up a screen with two blank drop down boxes (and no way to add information into them) and a 'confirm' checkbox. Hit 'submit' and you get an error (of course).

On the printed page, you have a top section the the recipe which places the serving and cooktime information. Below that is "Ingrediants" - which is blank. I guess if I don't fix the indgrediants list, I could just take it away from the .html doc. But it looks very nice like that.

Also, in in admin section for this module, on of the tabs says "_MI_RECETTE-LNK". Anyone know what that is suppossed to be (it's to the right of 'Manage Pictograms')?

Thanks in advance!

Thank you! News 1.44 is a great improvement over 1.1; worlds apart. I'm happy with my current version of XOOPS though. I downloaded 2.0.14 and did not like it at all. Most modules I installed gave errors. One day though...perhaps after I get the site off and running.

Hello,

I'm using News 1.1 in XOOPS 2.0.7.3. I'm curious as to how you change the displayed name of the poster from the login name to the real name. The database variable is 'name' as oppossed to 'uname'. Normally, I just go right into the html file in the templates_c directory - or the .php file in the module's main directory (so in this case the directory for News) and make changes there. I went into the index.php file for the module and found where it was assigning 'poster' to be 'uname', changed it to 'name' and promptly got a white page when trying to access the site (News displays as the home page). I already have articles written.

This is probably an easy fix. I only need to know the correct file to edit. If not I have to make a change, reload, then revert a lot. Obviously I'm not an expert at PHP/mySQL - I know what the commands mean, but the XOOPS system is pretty massive...

Thanks in advance!

I also had this problem with several modules. I found that changing the permissions to the module directory help in most (but not all) cases.