kabafit

I found this one in on of the previous debug.log’s that might be helpful:

[01-Oct-2014 10:13:32 UTC] WordPress-Datenbank-Fehler You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘( ml_blogid , ml_elementid )’ at line 1 für Abfrage ALTER TABLE wp_multilingual_linked ADD PRIMARY KEY (ml_id), INDEX ( ml_blogid , ml_elementid ) von require_once(‘wp-admin/network/admin.php’), require_once(‘wp-admin/admin.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), call_user_func_array, mlp_init, Multilingual_Press->__construct, Multilingual_Press->install_update_check, Multilingual_Press->update_plugin_data, Multilingual_Press->install_plugin, Mlp_Db_Installer->install, dbDelta

I followed the usual update procedure in the plugin section. Installation and activation went well. On the webpage appeared the widget box (language switcher) but without any link, flag or text (depending on the settings). Settings in the network administration are correct as well as all the widget settings on each site. In the debug.log no error message in regard to this plugin appeared.

I switched back to the old 2.0.3 and everything works like a charm again.

Eventually fixed it by a rollback to an old version (tx to mercurial) and database backup, now still using the old plugin version 2.0.3. Please let me know if you have fixed everything in the new update. TX for help.

TX for your support so far but there are still problems. No previous linkage between every article and page works anymore and to be honest I am a bit cross as the plugin worked so far really perfect and I enjoyed it and now it is a total mess. Now it takes a lot of time to fix it finally ??

Ok I understand. I replaced the old Mlp_Load_Controller.php with the new one you supported and could activate the Plugin in the normal way. But back on the main page (it is a two language page de/en) the icon and link to the english site disappeared. On the english site is everything fine. In the debug.log I found the following information:

[30-Sep-2014 10:45:04 UTC] PHP Notice: Undefined index: http_name in …/wp-content/plugins/multilingual-press-2.1.0/inc/core/language-api/Mlp_Language_Api.php on line 260

I guess that causes the new problem?

Yes, hosted by Strato. Here the debug.log content:

[30-Sep-2014 06:54:08 UTC] PHP Notice: get_current_theme is deprecated since version 3.4! Use wp_get_theme() instead. in …/wp-includes/functions.php on line 3201
[30-Sep-2014 06:54:10 UTC] PHP Notice: Use of undefined constant GLOB_BRACE – assumed ‘GLOB_BRACE’ in …/wp-content/plugins/multilingual-press-2.1.0/inc/autoload/Mlp_Load_Controller.php on line 83
[30-Sep-2014 06:54:10 UTC] PHP Fatal error: Class ‘Inpsyde_Property_List’ not found in …/wp-content/plugins/multilingual-press-2.1.0/multilingual-press.php on line 33

TX for support.

TX for reply, I replaced the old directory again with the new content of version 2.1.0 but after the activation of the Plugin the white page appears again like in the first attempt. As conclusion, it seems that it doesn’t matter in what way I install the Plugin Update, after the activation the page does not work at all.

have now installed the version 2.1.0 from github via FTP:

https://github.com/inpsyde/multilingual-press/releases/tag/2.1.0

After Aktivation of the Plugin it says:

Das Plugin kann nicht aktiviert werden, da es einen fatalen Fehler erzeugt.
Fatal error: Cannot redeclare mlp_init() (previously declared in …/wp-content/plugins/multilingual-press/multilingual-press.php:24) in …/wp-content/plugins/multilingual-press-2.1.0/multilingual-press.php on line 25

With the new version of FileZilla 3.1.6 everything works fine again.

I faced the same problem while updating from WordPress 2.6.3 to 2.6.5 using FileZilla 3.1.5.1. There is a Bug in that FileZilla Version not uploading subfolders. When I used another FTP programm everything worked fine. Here a link to a german forum discussing the same issue.

But why not using the latest Nightly Builds of FileZilla.