Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 28 replies, has 3 voices.

Last updated by Luis 8 years, 10 months ago.

Author Posts
July 19, 2012 at 8:29 pm #68335

Kristof

I've just purchased a licence but when uploading the CMS core files; I get plenty of errors (debug mode is true). Please check it out at: hidden link
Mostly Use of undefined constant ICL_LANGUAGE_CODE - assumed 'ICL_LANGUAGE_CODE' in

July 19, 2012 at 9:38 pm #68338

Kristof

Update: i've activated the Core plugin, the website is fine now; but the admin gives a 500 server error.

July 20, 2012 at 10:24 am #68394

Anonymous

Dear Kristof,

You can still get the complete information of what’s wrong, by dumping the PHP error log to a file.

To do this, add the following two lines to your wp-config.php file:

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . 'https://cdn.wpml.org/error_log.txt');
You will need to create a file named error_log.txt in your WordPress root directory and give the web server full write access to it. You can do it with a command shell or using an FTP program.
And post here the content of the log file.

July 20, 2012 at 10:25 am #68395

Anonymous

Dear Kristof,

You can still get the complete information of what’s wrong, by dumping the PHP error log to a file.

To do this, add the following two lines to your wp-config.php file:

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . 'https://cdn.wpml.org/error_log.txt');
You will need to create a file named error_log.txt in your WordPress root directory and give the web server full write access to it. You can do it with a command shell or using an FTP program.
And post here the content of the log file.

July 20, 2012 at 4:22 pm #68433

Kristof

Hi,
Please find below the content of the error log, after I have logged into WP.

[20-Jul-2012 16:20:21] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 91 bytes) in /var/www/goudenlaars.com/goudenlaars.com/wwwroot/wp-includes/pomo/mo.php on line 219

July 21, 2012 at 9:10 am #68481

Kristof

These are todays error logs:

[21-Jul-2012 04:59:20] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /var/www/goudenlaars.com/goudenlaars.com/wwwroot/wp-content/plugins/tinymce-advanced/tinymce-advanced.php on line 84
[21-Jul-2012 08:16:58] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in /var/www/goudenlaars.com/goudenlaars.com/wwwroot/wp-content/plugins/sociable/includes/sociable_output.php on line 234
[21-Jul-2012 09:09:37] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 78 bytes) in /var/www/goudenlaars.com/goudenlaars.com/wwwroot/wp-includes/pomo/streams.php on line 62

July 21, 2012 at 9:26 am #68483

Kristof

Yet another update 🙂 i've increased the memory limit to 64M and the allowed memory size exhausted errors no longer appears and I can log on to WP. Now the WPML plugin tells me that it needs to upgrade the database, i confirm, but nothing happens.

July 21, 2012 at 10:49 am #68487

Kristof

Update: now when i click upgrade the database, i get a blank screen with "Invalid nonce"

July 23, 2012 at 5:05 am #68591

Anonymous

Did you have an older version of WPM running?
If yes, What version was it?

July 23, 2012 at 5:17 am #68593

Kristof

As said in the title, WPML 2.5.2, that's the latest no?

July 23, 2012 at 12:00 pm #68643

Anonymous

Yes, Iam sure you have the latest version of the plugin on the site, but did you have an older version before? Usually wpml prompts a database upgrade if there was an older versoin of wpml running before trying to upgrade to the new one.

July 23, 2012 at 12:16 pm #68647

Kristof

Hi Brooks, yes i've upgraded from an earlier version, I guess that's why he's asking for the upgrade. But that upgrade of the database is causing the problem.

July 23, 2012 at 12:48 pm #68656

Anonymous

What version did you upgrade from?

July 23, 2012 at 1:02 pm #68660

Kristof

Good question, I'll have to go trough the backups. It was a free version before it turned into a paid plugin.

July 23, 2012 at 1:47 pm #68672

Anonymous

Try this to upgrade from a free version
1) restore your old database.
2) Disable WPML in the Plugins page.
3) Download WPML 2.0.4.1 and install it. You can get it from here:
hidden link
4) Enable WPML from the plugins page and disable it again.
5) Delete the entire WPML directory from your plugins folder on the server.
6) Install the current version
7) Enable it.

The topic ‘[Closed] WPML CMS 2.5.2. breaks WP 3.4.1.’ is closed to new replies.