icanlocalize

https://wpml.org/documentation/getting-started-guide/language-setup/#admin_language

The message is pretty self-explanatory. It says that WPML cannot create the necessary DB tables.

Your MySQL user might not have enough privileges to create tables. You need to contact your hosting provider, explain to them that you need to be able to create tables and get them to upgrade your user privileges. There’s no work-around for creating these language tables.

What was the permlink structure before?

The language footer would probably display better in these themes.

You can also change the widget to show an always-open list, which would prevent this problem.

We’ll look into this. It’s probably something that WPML is doing wrong.

I saw this post in our forum, and couldn’t understand it there as well.

If you could refer to some example that shows what you’re trying to achieve, it would probably help people reply.

Maybe put up this site somewhere (in one language) and use that to explain.

I don’t know what you mean by ‘static page’ and what additional functionality you’re referring to.

WP has pages, posts and will have custom types, but I’ve never heard of a static page.

Hi Gary,

If you think about adding multilingual support for WPML, have a look at the String translation feature.

You can register jobs as strings and then display them with the icl_t filter. It’s very similar to how gettext works, only meant for dynamic texts.

Your users will be able to translate those texts using WPML’s string translation page, so you don’t need to change anything in the GUI.

We can help you if you need.

You should really try to post about that in our forum. It’s very difficult to keep track of support requests in other places.

It’s not compatible with BP 1.2 right now.

We’re planning to do this in the near future, once we finish other pressing stuff with WPML (e.g., support for WP 3.0).

Can you open a thread about that in our support forum, including where we can see it, the theme, WP version, PHP version, MySQL version and other stuff to help reproduce the problem?

https://forum.wpml.org

Thanks for reporting. It also appears in our support forum here:
https://forum.wpml.org/topic.php?id=734

We’ll include a fix for this in WPML 1.5.1, out this week.

Finally, an update.

WPML 1.5.0 can run from any directory, not just the standard wp-contents.

There are several issues in WP core itself that make this compatibility not 100%, but generally, it’s working now.

The error is pretty self-explanatory. Your PHP setup is limited to 32Mb, so there’s not enough memory for WP and all the plugins you’re using.

If you increase it, everything should work normally.

We’re running a translation service and can help with that (on us). Where can I get the .pot file for the plugin?

The problem, as I see it is that there uploads are just files and are not associated with any object in the database.

If they had DB entries, registering them, it would have been possible to access the files in different ways. The permalink would have been calculated in real time, based on the permalink structure.

As it is now, the only thing that identifies files is their path on the hard drive, so there’s not much to do about it.