OJS当前最新版本为3.5,很多使用OJS3.4.X的同学,在升级时都遇到了或多或少的问题,丁老师几乎每天都收到有关升级失败的咨询。以下是丁老师整理的常见OJS3.4升级3.5的失败问题及处理方法(持续更新中):
Error 1: MariaDB SQL Syntax Incompatibility
ERROR: Upgrade failed: DB: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB
server version for the right syntax to use near '''' at line 1 (Connection: mysql, SQL: alter table `email_templates_default_data` modify `locale`
varchar(28) not null default ''en'')Error 2: Column Rename Conflicts
ERROR: Upgrade failed: DB: SQLSTATE[42S21]: Column already exists: 1060
Duplicate column name 'redirect_context_id'
(Connection: mysql, SQL: alter table `site` rename column `redirect` to `redirect_context_id`)Error 3: Missing Column Dependencies
ERROR: Upgrade failed: DB: SQLSTATE[42S22]: Column not found: 1054
Unknown column 'context' in 'notification_subscription_settings'
(Connection: mysql, SQL: alter table `notification_subscription_settings` rename column `context` to `context_id`)Error 4: Schema Inconsistency
ERROR: Upgrade failed: DB: SQLSTATE[42S22]: Column not found: 1054
Unknown column 'redirect' in 'site'
(Connection: mysql, SQL: alter table `site` modify `redirect` bigint null)Error 5: Schema Inconsistency
ojs upgrade A database error has occurred: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘’‘’ at line 1 (Connection: mysql, SQL: alter table email_templates_default_data modify locale varchar(28) not null default ‘‘en’’)上述问题是,默认值引用不正确,在MariaDB/Mysql上出现的语法错误,导致在创建或修改表列时,Illuminate Database工具集无法正确转义基于字符串的列默认值,从而引起OJS3.5升级失败。是属于官方程序的一个bug。
解决方法:当提供字符串字面量时,转义应该由Laravel处理。
/**
* Format a value so that it can be used in "default" clauses.
*
* @param mixed $value
* @return string
*/
protected function getDefaultValue($value)
{
if ($value instanceof Expression) {
return $this->getValue($value);
}
if ($value instanceof BackedEnum) {
return "'{$value->value}'";
}
return is_bool($value)
? "'".(int) $value."'"
: "'".(string) $value."'";
}Error 6: Table‘journals’already exists
SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘journals’ already exists (Connection: mysql, SQL: create table journals (journal_id bigint not null auto_increment primary key, path varchar(32) not null, seq float(53) not null default ‘0’ comment ‘Used to order lists of journals’, primary_locale varchar(28) not null, enabled smallint not null default ‘1’ comment ‘Controls whether or not the journal is considered "live" and will appear on the website. (Note that disabled journals may still be accessible, but only if the user knows the URL.)’, current_issue_id bigint null) default character set utf8 collate ‘utf8_general_ci’)Error 7: Table‘invitations’already exists
2025-07-02 15:50:28 [pre-install]
2025-07-02 15:50:28 [load: upgrade.xml]
2025-07-02 15:50:28 [version: 3.5.0.0]
2025-07-02 15:50:28 [code: Installer Installer::checkPhpVersion]
2025-07-02 15:50:28 [code: Installer Installer::installDefaultNavigationMenus]
[02-Jul-2025 15:50:28 UTC] WARNING: The NavigationMenu (ContextId: 1, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
[02-Jul-2025 15:50:28 UTC] WARNING: The NavigationMenu (ContextId: 1, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
[02-Jul-2025 15:50:28 UTC] WARNING: The NavigationMenu (ContextId: , Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
2025-07-02 15:50:28 [code: Installer Installer::migrateStaticPagesToNavigationMenuItems]
2025-07-02 15:50:28 [migration: PKP\migration\upgrade\v3_4_0\I10249_FixProfileImageDataLoss]
2025-07-02 15:50:28 [migration: PKP\migration\upgrade\v3_4_0\I9627_AddUsageStatsTemporaryTablesIndexes]
2025-07-02 15:50:29 [migration: PKP\migration\upgrade\v3_4_0\I9535_FixEmptyFileStage]
2025-07-02 15:50:29 [migration: PKP\migration\upgrade\v3_4_0\I9830_FixEmptyUserLocales]
2025-07-02 15:50:29 [migration: PKP\migration\upgrade\v3_4_0\I8592_SiteNotificationSubscriptions]
2025-07-02 15:50:29 [migration: APP\migration\upgrade\v3_4_0\I9813_QuickSubmitSubmissionProgressType]
2025-07-02 15:50:29 [migration: APP\migration\upgrade\v3_5_0\I11241_MissingDecisionConstantsUpdate]
2025-07-02 15:50:29 [migration: PKP\migration\upgrade\v3_5_0\PreflightCheckMigration]
2025-07-02 15:50:29 [migration: APP\migration\upgrade\v3_5_0\I8333_AddMissingForeignKeys]
2025-07-02 15:50:33 [migration: APP\migration\upgrade\v3_5_0\I9892_FloatToDecimalColumnTypeUpdate]
2025-07-02 15:50:33 [migration: PKP\migration\upgrade\v3_5_0\I9895_AddAppKeyToConfigFile]
2025-07-02 15:50:33 [migration: PKP\migration\upgrade\v3_5_0\I9678_RemoveScheduledTasksTable]
2025-07-02 15:50:33 [migration: PKP\migration\upgrade\v3_5_0\InstallEmailTemplates]
2025-07-02 15:50:33 [migration: PKP\migration\upgrade\v3_5_0\I9197_MigrateAccessKeys]
2025-07-02 15:50:33 [revert migration: PKP\migration\upgrade\v3_5_0\InstallEmailTemplates]
2025-07-02 15:50:33 [revert migration: PKP\migration\upgrade\v3_5_0\I9678_RemoveScheduledTasksTable]
2025-07-02 15:50:33 [revert migration: PKP\migration\upgrade\v3_5_0\I9895_AddAppKeyToConfigFile]
2025-07-02 15:50:33 [revert migration: APP\migration\upgrade\v3_5_0\I9892_FloatToDecimalColumnTypeUpdate]
2025-07-02 15:50:33 [revert migration: APP\migration\upgrade\v3_5_0\I8333_AddMissingForeignKeys]
2025-07-02 15:50:33 [downgrade for "APP\migration\upgrade\v3_5_0\I8333_AddMissingForeignKeys" unsupported: Downgrade not supported]
ERROR: Upgrade failed: DB: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'invitations' already exists (Connection: mysql, SQL: create table `invitations` (`invitation_id` bigint not null auto_increment primary key, `key_hash` varchar(255) null, `type` varchar(255) not null, `user_id` bigint null, `inviter_id` bigint null, `expiry_date` datetime null, `payload` json null, `status` enum('INITIALIZED', 'PENDING', 'ACCEPTED', 'DECLINED', 'CANCELLED') not null, `email` varchar(255) null comment 'When present, the email address of the invitation recipient; when null, user_id must be set and the email can be fetched from the users table.', `context_id` bigint null, `created_at` timestamp null, `updated_at` timestamp null) default character set utf8mb4 collate 'utf8mb4_unicode_ci')解决方法:
1.备份旧数据库;
2.删除提示已存在的表“如journals、invitations表”;
3.升级;
4.从旧数据库,恢复导入旧表的数据至新表。
总结:
OJS软件版本分支较多,每个版本的迭代,都是很大规模的更新。因为涉及数据关联、插件兼容性等问题,一些OJS版本在升级时可能会遇到一些意想不到的问题,而这些问题往往很难找到正确的处理方法。
丁老师从事专业的OJS期刊软件安装搭建、二次开发、版本升级服务,对OJS系统有着深入的研究,可以解决各种OJS软件的疑难杂症及故障。同时,丁老师提供OJS版本升级服务,需要升级OJS版本的同学,可以联系丁老师咨询。
经常有想做期刊运营的客户咨询,使用OJS期刊管理系统,是不是很贵?都会产生什么费用啊?网上说的OJS很烧钱,是不是真的?针对这些相关问题,丁老师今天做一下解答。OJS是否收费?OJS系统是开源免费的,不收任何费用,并且无软件授权,支持商...
有使用Open Journal Systems(OJS)期刊系统的客户咨询,他们出版社使用的是OJS3.2版本的程序,很多最新的功能都没法用,而且已发布的文章,有很多Google学术都不再收录(不知道是不是因为版本太久的原因),并且系统...
OJS系统中,关于投稿-同行评审(审核、退稿、通过)-发布等流程中,任何操作都是会有邮件通知的,在评审进入每一个环节时,会自动的把相关的信息通过邮件发送给相关人员,如图:OJS自带邮件模板,包含了对应工作流的内容:期刊名称、期刊网址、工...
近期丁老师在对OJS期刊系统进行等保工作时,发现OJS一个安全漏洞,即任意文件上传漏洞,具体内容如下。漏洞描述任意文件上传漏洞(Unrestricted File Upload),是一种常见的Web安全漏洞,由于Web应用程序在实现文件...