we are going to downgrade WPMU incl. its plugins. The simplest way seems to be back to the “old” xampp installation and reload the WPMU database with the latest data.
The following components would be downgraded:
WPMU 2.9.2 to 2.8.4.a
WPML 184.108.40.206 to 1.4.0
Simple Tags 220.127.116.11 to 1.6.6
The database design was already anlysed and the following changes recognised (left the old one, right the new one):
1) the wp_XX_options table has two changes:
a) column “option_name”: VARCHAR(64) to VARCHAR(64) NOT NULL
b) PRIMARY KEY (option_id, blog_id, option_name), INDEX option_name (option_name) to
PRIMARY KEY (option_id), UNIQUE INDEX option_name (option_name)
2) There is new table in the newer version:
TABLE wp_XX_icl_string_positions (
id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT,
string_id BIGINT(20) NOT NULL,
kind TINYINT(4) DEFAULT NULL,
position_in_page VARCHAR(255) NOT NULL,
PRIMARY KEY (id),
INDEX string_id (string_id)
3) and a further:
TABLE wp_XX_commentmeta (
meta_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT,
comment_id BIGINT(20) UNSIGNED NOT NULL DEFAULT 0,
meta_key VARCHAR(255) DEFAULT NULL,
meta_value LONGTEXT DEFAULT NULL,
PRIMARY KEY (meta_id),
INDEX comment_id (comment_id),
INDEX meta_key (meta_key)
At first few there is no problem either on the database side nor on the application side:
1) The new constraints are more strong, therefore no problem during loading data (after loading rebuild index ?)
2-3) There is no references from the “old” tables to the “new” tables, therefore the new tables could be ignored simply.
Could you please confirm us, that
A) There is no other changes in the database (concerning Simple Tags)
B) The reload the old structurte with the new data (without 2 and 3 of course) will be had no effect on the application ?
Thanks in advance for your effort !
- The topic ‘Simple Tags’ is closed to new replies.