Sonja Glauch

Hello, did you comment line 424 in index.php? In my installation it's deactivated, even if I have no clue who did it and why. ;) fopen() is still used in function fetchDataFromURL, which is defined in include.inc.php. Regards

Hello, did you comment line 424 in index.php? In my installation it's deactivated (but I have no clue who did it and why ;) ). fopen() is still used in function fetchDataFromURL, which is defined in include.inc.php. Regards

Hello, did you comment line 424 in index.php? In my installation it's deactivated (but I have no clue who did it and why ;) ). P.S. fopen() is still used in function fetchDataFromURL, which is defined in include.inc.php. Regards

Hello, did you comment line 424 in index.php? In my installation it's deactivated (but I have no clue who did it and why ;) ). Regards

I'm afraid you will not get rid of this warning "Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead" easily. I pondered a good while about it and came to no solution. It originates in some of the transtab_-files in /includes/. These files contain arrays of replacements like '/((\$\^\{.+?\}\$|\\textsuperscript\{.+?\}|\{\\text(one|two|three)superior\})+)/ie' => "bibtexSuperScriptToRefbase('\1')" The /ie ist the culprit here. These arrays get processed...

You should ignore these warnings and notices. But I don't know where to adjust that in XAMP. Is there a php.ini somewhere? Perhaps this can help: https://stackoverflow.com/questions/10160859/turn-php-error-reporting-off-in-xampp

You should ignore these warnings and notices. But I don't know where to adjust that in XAMP. Is there a php.ini somewhere?

Ja, jetzt sehe ich auch, woran es lag. mysql_fetch_field (alt) und mysqli_fetch_field_direct (neu) liefern verschiedene Ergebniswerte. Ich finde im Sourcecode auch nur eine einzige Stelle, wo einmal einer der abgefragten Ergebniswerte ausgewertet wird. Es ist also vielleicht nicht so schlimm, die Zeilen auszukommentieren.