French Traduction finished.

Do you want it ?

I just moved my XOOPS installation from one box to another. Everything seems to be ok except when I try to update each module. I don't know which file the "Unable to write to main menu" error is refering to.

I get the following (errors are in red). Any help would be appreciated.
----------------------------
failed open fileModule data updated.
Updating templates...
Template system_imagemanager.html inserted to the database.
Template system_imagemanager2.html inserted to the database.
Template system_userinfo.html inserted to the database.
Template system_userform.html inserted to the database.
Template system_rss.html inserted to the database.
Template system_redirect.html inserted to the database.
Template system_comment.html inserted to the database.
Template system_comments_flat.html inserted to the database.
Template system_comments_thread.html inserted to the database.
Template system_comments_nest.html inserted to the database.
Template system_siteclosed.html inserted to the database.
Template system_dummy.html inserted to the database.
Template system_notification_list.html inserted to the database.
Template system_notification_select.html inserted to the database.

Unable to write to main menu.


Rebuilding blocks...
Block User Menu updated. Block ID: 1
Template system_block_user.html updated.
Block Login updated. Block ID: 2
Template system_block_login.html updated.
Block Search updated. Block ID: 3
Template system_block_search.html updated.
Block Waiting Contents updated. Block ID: 4
Template system_block_waiting.html updated.
Block Main Menu updated. Block ID: 5
Template system_block_mainmenu.html updated.
Block Site Info updated. Block ID: 6
Template system_block_siteinfo.html updated.
Block Who's Online updated. Block ID: 7
Template system_block_online.html updated.
Block Top Posters updated. Block ID: 8
Template system_block_topusers.html updated.
Block New Members updated. Block ID: 9
Template system_block_newusers.html updated.
Block Recent Comments updated. Block ID: 10
Template system_block_comments.html updated.
Block Notification Options updated. Block ID: 11
Template system_block_notification.html updated.
Block Themes updated. Block ID: 12
Template system_block_themes.html updated.

Module System updated successfully.

Thanks Brad !



Tested and it works perfectly.

@Gronice : do you mind if I make the french adaptation of your module ?

I get the same error.

EDIT> the problem is the two underscores, it should only be one: _getSubTasks. I made this change, and it works fine now.

Brad

OK, I'm sorry I didn't read carefully enough what you intended to do before I posted. You want everything to happen in that link (i.e. not go to some other page first). You solution should work, though I think it is a little insecure because it will be very easy for your visitors to figure out the URL and start spamming you (if you have a small trusted userbase this may not be a problem).

I would suggest instead, wrapping a tiny HTML form around the link, and make the link a *button* instead. This way the message will be set as a POST var. Then your change isn't needed, and security is improved.

Got it!

I added these lines after line 34 of pmlite.php:

// Begin Hack
$message = $HTTP_GET_VARS['message'];
$subject = $HTTP_GET_VARS['subject'];
// End Hack

Now it works!

I'm a bit confused, but thanks for all the help!

I saw that bit of code, and that's what got me to use what I did in the URL. I saw that it was looking for "message" in the URL, so I added that, but that didn't let the message show up in the message box.

Could it be that the message is there, but just not being added to the textbox and made visible?

catzwolf's suggestions would be the simplest.

A slightly more complicated approach, but one would give the option of sending EMAIL in addition or as alternative to PM, is to use the 'xoopsmultimailer'. If interested, check out kernel/notification.php for code to set up the mailer to send messages.

You could try using this code in your own, this will use the PM system directly without having to hack any other files:

$pm_handler = & xoops_gethandler( 'privmessage' );
$pm = & $pm_handler -> create();
$pm -> setVar( "subject", $HTTP_POST_VARS['subject'] );
$pm -> setVar( "msg_text", $HTTP_POST_VARS['message'] );
$pm -> setVar( "to_userid", $HTTP_POST_VARS['to_userid'] );
$pm -> setVar( "from_userid", $xoopsUser -> getVar( "uid" ) );

Hope this helps

You're absolutely correct! I enclosed the XOOPS_ROOT_PATH in quotes and it's running without a hitch now. Thanks for your help