That error message actually answers your question. But you also have the option of turning off the error message throught the deprecated_function plugin options.
As you know, the forum rules require these conversations to be in English so that all can follow. We'll let it stand this time since you are obviously frustrated, but be warned that these non-English postings may be removed as non compliant.
Unfortunately, "lingua franca" no longer applies. The language of modern commerce is English, like it or not. Our documentation is in English, and while we have no objection to someone translating it to other languages we do not have the time (nor the skills) to do so ourselves.
I am also sorry that you are confused by the changes we have made (and don't understand them.) Of course, there are ample examples of how things are done now versus previous implementations. Just look at the plugins which we distribute.
It is also pretty late in the development process for a plugin developer to be looking at the 1.4 release. Best is to keep up with the changes by following the repositor and change log. Then suprises do not occur.
Also, I really think that our changes are not that severe at all. Its mainly detail changes that could be generally solved by changing just a few lines in a theme or plugin.
Sorry, but of course we don't know your plugins so we don't even know if they actually need any severe changes at all.
Comments
How change/modify my plugins to use new/good functions ?!
Unfortunately, "lingua franca" no longer applies. The language of modern commerce is English, like it or not. Our documentation is in English, and while we have no objection to someone translating it to other languages we do not have the time (nor the skills) to do so ourselves.
I am also sorry that you are confused by the changes we have made (and don't understand them.) Of course, there are ample examples of how things are done now versus previous implementations. Just look at the plugins which we distribute.
It is also pretty late in the development process for a plugin developer to be looking at the 1.4 release. Best is to keep up with the changes by following the repositor and change log. Then suprises do not occur.
Sorry, but of course we don't know your plugins so we don't even know if they actually need any severe changes at all.
A typical example of the function registered would look something like:
`
function flvplayerJS() {
?>
/flvplayer/swfobject.js">
<?php
}
`