A database error has occurred: Contact name or email is missing for context(s) with path(s) [jiafm,test]. Please set those before upgrading

Describe the issue or problem
A database error has occurred: Contact name or email is missing for context(s) with path(s) [jiafm,test]. Please set those before upgrading.
Steps I took leading up to the issue
For example:
anyone please let me know where this setting is need to be filled

What application are you using?
OJS 3.3.0-4

Additional information
A database error has occurred: Contact name or email is missing for context(s) with path(s) [jiafm,test]. Please set those before upgrading.

this error is come whern trying to upgrage from

3.3.0-14 to 3.4.0-0

Hi @acspublisher,

You need to fill these fields before upgrading (if you don’t have access to the OJS 3.3 installation anymore, this can be manually through the database):

3-4-contactfields

Hi @acspublisher,

You can set journal’s contact name and email under journal settings → contact tab. Those are mandatory fiends and should be filled before the upgrade.

Thanks a lot upgrade but get below error HTTP ERROR 500

[14-Jun-2023 11:31:19 UTC] PHP Fatal error: Uncaught Error: Call to a member function getOption() on null in /home2/jiafmbfr/public_html/cache/t_compile/b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php:37
Stack trace:
#0 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_6489a4f74c3660_70767376(Object(Smarty_Internal_Template))
#1 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(Smarty_Internal_Template))
#2 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render(Object(Smarty_Internal_Template))
#3 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 1)
#4 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(134): Smarty_Internal_TemplateBase->_execute(Object(Smarty_Internal_Template), NULL, ‘b9da708b775ca19…’, NULL, 1)
#5 /home2/jiafmbfr/public_html/lib/pkp/classes/template/PKPTemplateManager.php(1325): Smarty_Internal_TemplateBase->display(‘frontend/pages/…’, NULL, ‘b9da708b775ca19…’, NULL)
#6 /home2/jiafmbfr/public_html/pages/index/IndexHandler.php(80): PKP\template\PKPTemplateManager->display(‘frontend/pages/…’)
#7 [internal function]: APP\pages\index\IndexHandler->index(Array, Object(APP\core\Request))
#8 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPRouter.php(334): call_user_func(Array, Array, Object(APP\core\Request))
#9 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPPageRouter.php(277): PKP\core\PKPRouter->_authorizeInitializeAndCallRequest(Array, Object(APP\core\Request), Array, false)
#10 /home2/jiafmbfr/public_html/lib/pkp/classes/core/Dispatcher.php(165): PKP\core\PKPPageRouter->route(Object(APP\core\Request))
#11 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPApplication.php(373): PKP\core\Dispatcher->dispatch(Object(APP\core\Request))
#12 /home2/jiafmbfr/public_html/index.php(21): PKP\core\PKPApplication->execute()
#13 {main}
thrown in /home2/jiafmbfr/public_html/cache/t_compile/b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php on line 37

Thanks a ton pls help me onto this also

Thanks a lot upgrade but get below error HTTP ERROR 500

[14-Jun-2023 11:31:19 UTC] PHP Fatal error: Uncaught Error: Call to a member function getOption() on null in /home2/jiafmbfr/public_html/cache/t_compile/b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php:37
Stack trace:
#0 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_resource_base.php(123): content_6489a4f74c3660_70767376(Object(Smarty_Internal_Template))
#1 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php(114): Smarty_Template_Resource_Base->getRenderedTemplateCode(Object(Smarty_Internal_Template))
#2 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php(217): Smarty_Template_Compiled->render(Object(Smarty_Internal_Template))
#3 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(238): Smarty_Internal_Template->render(false, 1)
#4 /home2/jiafmbfr/public_html/lib/pkp/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(134): Smarty_Internal_TemplateBase->_execute(Object(Smarty_Internal_Template), NULL, ‘b9da708b775ca19…’, NULL, 1)
#5 /home2/jiafmbfr/public_html/lib/pkp/classes/template/PKPTemplateManager.php(1325): Smarty_Internal_TemplateBase->display(‘frontend/pages/…’, NULL, ‘b9da708b775ca19…’, NULL)
#6 /home2/jiafmbfr/public_html/pages/index/IndexHandler.php(80): PKP\template\PKPTemplateManager->display(‘frontend/pages/…’)
#7 [internal function]: APP\pages\index\IndexHandler->index(Array, Object(APP\core\Request))
#8 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPRouter.php(334): call_user_func(Array, Array, Object(APP\core\Request))
#9 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPPageRouter.php(277): PKP\core\PKPRouter->_authorizeInitializeAndCallRequest(Array, Object(APP\core\Request), Array, false)
#10 /home2/jiafmbfr/public_html/lib/pkp/classes/core/Dispatcher.php(165): PKP\core\PKPPageRouter->route(Object(APP\core\Request))
#11 /home2/jiafmbfr/public_html/lib/pkp/classes/core/PKPApplication.php(373): PKP\core\Dispatcher->dispatch(Object(APP\core\Request))
#12 /home2/jiafmbfr/public_html/index.php(21): PKP\core\PKPApplication->execute()
#13 {main}
thrown in /home2/jiafmbfr/public_html/cache/t_compile/b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php on line 37

Was the upgrade successful?

yes the upgrade was sucessful without any error

The error goes from a cached template. Can you clear the catch from the administration area and see if the issue persists?

Unable to open anything… How can i clear the catches any suggestion

You can delete the file manually by the path specified:

/home2/jiafmbfr/public_html/cache/t_compile/b9da708b775ca192cb9735589afa7e98b537357a^e64e579388e5615e11e939b12134d6ae8679eba6_0.app.frontendpagesindexJournal.tpl.php

It will be regenerated on the next request.

Also, the error message specified is only for index journal page. Do you have other errors as well?
What do you see in the error log when trying to access administration page? (.../index.php/index/admin)

after that this error appear please help me onto this

A database error has occurred: SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘at.assoc_type’ in ‘where clause’ (SQL: select distinct at.type_id from announcement_types as at left join journals as c on at.assoc_id = c.journal_id where c.journal_id is null or at.assoc_type <> 256)

Was the previous error resolved after cache regeneration?

What are the reproduction steps for this error?
Are you conducting a new upgrade or is this something else?

Will remove all upgradtion and up old version, remove and delete cache and when trying to upgrade again this error will come

Yes the previous error is resolved

Upgrading again wont work, this is why the error appears.
You would have to start with the previous state of the database with the journal details updated and the do another upgrade.
But why would you need to start the upgrade process again?

After sucessful upgrarde cache error will come so i remove upgradation and install previous version and though administration remove cahce after this error come and not only me most user this error will come when i search on PKP forum

Yes, this error comes because the upgrade process already changed the database tables to the schema used in 3.4.0 version

After the upgrade process has been started once on the database you can not start it again without restoring the database to the old version with a dump/backup.