This error:
[06-Jun-2007 17:44:59] PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /hq/site/foo/www/includes/class_dm_threadpost.php(656) : eval()'d code on line 1
Dissappear when I disabled postdata_start hook.
But, what happend if this be disabled? Or I need to enable this agayn?

Second error still here...

i tested it on my testboard with a post related warning and a non post related warning no errors at all (both of them didn't showed up) the postdata_start hook at wrong code PHP code in it true but you need to manually edit the plugin at that hook and no you need that hook or some data will be missing.I'll see later to package the fix as a plugin that you can import.This is not your fault but mine i forgot to mention you need to manually update that hook otherwise vBulletin will not update it

here it is imprt this through admincp => product system => download/ upload plugins

The second error will be fixed?

I am still getting errors on 4.4.7 after applying the fix and the updated files.

Parse error: syntax error, unexpected T_OBJECT_OPERATOR in C:\<path>\includes\class_dm_threadpost.php(656) : eval()'d code on line 1

and

Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in C:\<path>\includes\class_dm_threadpost.php(829) : eval()'d code on line 64

I've disabled all other hacks except this and I am still getting these errors, even on the default skin. Had to disable, since I don't have the old version lying around.

hmmmz,

I do drink much but it doesn't contain any alcohol. :rolleyes:

should be
i forgot a "$" $this is a PHP variable refering to the "current" object.The newly attached error_fix.xml contains the change and this time it's gonna work or you can shoot me :D

Wow! Great! This work!
But i still get
[07-Jun-2007 09:57:54] PHP Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /hq/site/foo/www/includes/class_dm_threadpost.php(829) : eval()'d code on line 64

And also: How can I do another language template?

You are free to Translate the phrases into any language you wish to use.. that's why the phrases system excist

as for the error message you still see that is coming from the postdata_postsave hook and that one is used by the automatic warnings feature which can be turned off in the system settings

The package availible for download has been updated to include the fix for the PHP error message and the original error_fix.xml is removed to avoid confusion

No, I mean, how can I create a language .xml file only for Language?
Can you say, what exactly I should to do?

• admincp => languages & phrases => {YOUR LANUGAGE} => translate phrases
• admincp => language.php?do=files => product advanced Warning System
• for each language you have installed vBulletin will display a corrosponding "translation box"
• please note you must be able to translate "from english"
• you will need the phrasetype id's used (you can see that in the product XML)

automatic warnings can be turned of by going to admincp => advanced warning system => manage system settings => use automatic warnings from posts and use automatic warnings from private messages set that to no

in case you get confused by the XML coding.You can also find the phrases you'll need to translate by quering your database like this

[sql]
SELECT * FROM vb3_phrase WHERE product = 'aws' ORDER BY fieldname DESC
[/sql]

if you use another table prefix (or none at all) you will need to replace that in the above example