Home › Toolset Professional Support › [Resolved] I get the faullt message below
Problem:
I ran a local site on WordPress Studio (SQLite) and hit a fatal error during Toolset’s upgrade when it tried to ALTER TABLE wp_toolset_relationships to add the autodelete_intermediary column (duplicate column error), preventing access to the admin side.
Solution:
This environment isn’t supported by Toolset; the fix was to use a standard WordPress stack with MySQL/MariaDB (e.g., MAMP/WAMP/Local WP/XAMPP) or migrate to a regular host, after which the issue no longer occurred.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
This topic contains 3 replies, has 1 voice.
Last updated by Kristian Adolfsson 3 weeks, 4 days ago.
Assisted by: Christopher Amirian.
This is a local site run on "WordPress Studio" program.
What can I do to solve it?
"MySQL query:
ALTER TABLE `wp_toolset_relationships` ADD `autodelete_intermediary` TINYINT(1) NOT NULL DEFAULT '1' AFTER `is_active`
Queries made or created this session were:
Executing: BEGIN IMMEDIATE | (no parameters)
Executing: SELECT 1 FROM sqlite_temp_schema WHERE type = 'table' AND name = ? | parameters: wp_toolset_relationships
Executing: SELECT COLUMN_NAME, LOWER(COLUMN_NAME) AS COLUMN_NAME_LOWERCASE FROM `_wp_sqlite_mysql_information_schema_columns` WHERE table_schema = ? AND table_name = ? | parameters: database_name_here, wp_toolset_relationships
Executing: SELECT 1 FROM sqlite_temp_schema WHERE type = 'table' AND name = ? | parameters: wp_toolset_relationships
Executing: SELECT MAX(ordinal_position) FROM `_wp_sqlite_mysql_information_schema_columns` WHERE table_schema = ? AND table_name = ? | parameters: database_name_here, wp_toolset_relationships
Executing: INSERT INTO `_wp_sqlite_mysql_information_schema_columns` (`table_schema`, `table_name`, `column_name`, `ordinal_position`, `column_default`, `is_nullable`, `data_type`, `character_maximum_length`, `character_octet_length`, `numeric_precision`, `numeric_scale`, `datetime_precision`, `character_set_name`, `collation_name`, `column_type`, `column_key`, `extra`, `privileges`, `column_comment`, `generation_expression`, `srs_id`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) | parameters: database_name_here, wp_toolset_relationships, autodelete_intermediary, 29, 1, NO, tinyint, , , 3, 0, , , , tinyint(1), , , select,insert,update,references, , ,
Executing: ROLLBACK | (no parameters)
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'autodelete_intermediary'
Backtrace:
#0 /wordpress/wp-content/mu-plugins/sqlite-database-integration/wp-includes/sqlite-ast/class-wp-sqlite-driver.php(5496): WP_SQLite_Driver->new_driver_exception('SQLSTATE[42S21]...', '42S21')
#1 /wordpress/wp-content/mu-plugins/sqlite-database-integration/wp-includes/sqlite-ast/class-wp-sqlite-driver.php(845): WP_SQLite_Driver->convert_information_schema_exception(Object(WP_SQLite_Information_Schema_Exception))
#2 /wordpress/wp-content/mu-plugins/sqlite-database-integration/wp-includes/sqlite/class-wp-sqlite-db.php(537): WP_SQLite_Driver->query('ALTER TABLE `wp...')
#3 /wordpress/wp-content/mu-plugins/sqlite-database-integration/wp-includes/sqlite/class-wp-sqlite-db.php(449): WP_SQLite_DB->_do_query('ALTER TABLE `wp...')
#4 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/upgrade/Command/AddRelationshipTableColumnAutodeleteIntermediaryPosts.php(79): WP_SQLite_DB->query('ALTER TABLE `wp...')
#5 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/upgrade/Command/AddRelationshipTableColumnAutodeleteIntermediaryPosts.php(38): OTGS\Toolset\Common\Upgrade\Command\AddRelationshipTableColumnAutodeleteIntermediaryPosts->update_relationships_table()
#6 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/upgrade/UpgradeController.php(161): OTGS\Toolset\Common\Upgrade\Command\AddRelationshipTableColumnAutodeleteIntermediaryPosts->run()
#7 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/upgrade/UpgradeController.php(134): OTGS\Toolset\Common\Upgrade\UpgradeController->process_command(Object(OTGS\Toolset\Common\Upgrade\CommandDefinition), Object(OTGS\Toolset\Common\Result\ResultSet))
#8 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/upgrade/UpgradeController.php(97): OTGS\Toolset\Common\Upgrade\UpgradeController->do_upgrade(0, 6)
#9 /wordpress/wp-includes/class-wp-hook.php(324): OTGS\Toolset\Common\Upgrade\UpgradeController->check_upgrade(Object(Toolset_Common_Bootstrap))
#10 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#11 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/bootstrap.php(107): do_action('toolset_common_...', Object(Toolset_Common_Bootstrap))
#13 /wordpress/wp-content/plugins/types/vendor/toolset/toolset-common/bootstrap.php(126): Toolset_Common_Bootstrap->__construct()
#14 /wordpress/wp-content/plugins/types/application/controllers/main.php(171): Toolset_Common_Bootstrap::get_instance()
#15 /wordpress/wp-includes/class-wp-hook.php(324): Types_Main->after_setup_theme('')
#16 /wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#17 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#18 /wordpress/wp-settings.php(705): do_action('after_setup_the...')
#19 /wordpress/wp-config.php(102): require_once('/wordpress/wp-s...')
#20 /wordpress/wp-load.php(50): require_once('/wordpress/wp-c...')
#21 /wordpress/wp-admin/admin.php(35): require_once('/wordpress/wp-l...')
#22 /wordpress/wp-admin/edit.php(10): require_once('/wordpress/wp-a...')
#23 {main}"
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi there
WordPress Studio is a non-standard development environment that uses SQLite instead of MySQL as its database layer, and it includes a compatibility layer that aims to mimic MySQL but not wholly successfully.
We haven't done any testing with WordPress Studio I'm afraid and it is not something we have declared support for.
If you migrate your site to a server that uses a traditional stack and it also displays a similar error than we would be able to investigate that, if you could share such details with us.
Hi Nigel
OK, what would you recommend instead?
Hi,
This is Christopher, and I will continue with this ticket.
You will need to create a standard WordPress installation.
There are many website hosting services that provide that out of the box.
For a local environment, you can use:
MAMP/WAMP
Local WP
ZAMP
...
So basically, Toolset is a plugin of the WordPress system and not the WordPress studio.
Thanks.
Ah, thanks, now I get the difference!