Textpattern Support Forum

Ruud

Yet another useful rvm plugin — thank you.

The plugin only changes the tables with the same table prefix as the textpattern install where the plugin was installed, so if you have 2 TXP installs in 1 database, you’ll have to install/run the plugin in both TXP installs.

Currently only tables that really belong to TXP are converted (textpattern, txp_page, txp_css etc), so if you have a plugin that creates a table called txp_example, then that table will not be converted automatically.

I’m thinking about also including extra tables with that same TXP table prefix that were added by other plugins, to avoid having to update those manually, but that’s a bit more risky, especially if you didn’t specify a prefix for your textpattern install and there are other, non-TXP related tables in your database.

Tables used by plugins should use the same prefix as TXP tables, so in that case I’d probably show all tables that are not normally part of a TXP install (the standard TXP tables should be converted anyway, so there’s no point in showing those) and let the user check them if he’s certain that they belong to the TXP install…. but how many plugins create separate tables that contain UTF-8 data? Is it worth adding this functionality?

Great!

I used to use this textsnippet to do the job.

A question:

A client’s site is running a TxP 4.0.5 + MLP on a MySQL 4.0.18, so it’s currently running on a latin1 db.
When MySQL gets updated (don’t know when will it happen), I would like to try this plug-in to update the DB.
But, ruud says that this only works over tables that belongs to TxP.

So, what about the MLP? does any table that belongs to MLP also need to be converted? I think translated articles are stored in the standard TxP table, but what about things like snippets?

Thanks!

maniqui wrote:

A client’s site is running a TxP 4.0.5 + MLP on a MySQL 4.0.18, so it’s currently running on a latin1 db.
When MySQL gets updated (don’t know when will it happen), I would like to try this plug-in to update the DB.
But, ruud says that this only works over tables that belongs to TxP.
So, what about the MLP? does any table that belongs to MLP also need to be converted?

Yes, the ‘l10n_’ tables would need to be converted too. If your installation is using a table prefix, then that will be taken care of by ruud’s idea of converting all tables which match the Txp table prefix. However, you could use your script method for those.

I think translated articles are stored in the standard TxP table, but what about things like snippets?

Snippets are all stored in the existing txp_lang table so they will be taken care of by ruud’s plugin anyway.

BTW: Latest MLP doesn’t allow installation attempts on MySQL pre-version 4.1.

Ruud

So there is some need for Txp plugins’ table conversions after all — and from my own work! (Dusts off hat in preparation for a meal.) But does that present enough demand to implement the UI for this?