Upgrading from 2.3 to 3.0 

Before you start 

Version 3.0 runs on TYPO3 13.4 from 13.4.35 on and on TYPO3 14.3 from 14.3.7 on, with PHP 8.2 or later.

academic_jobs 3.0 needs these packages. Upgrade them first or in the same deployment, in this order:

• fgtclb/environment-state-manager 2.x, new since 2.4, which academic_base 3.0 requires. Composer installs it on its own. A classic installation installs environment_state_manager 2.x before it activates academic_base 3.0.
• fgtclb/academic-base 3.0, the same release as this extension.

ext_emconf.php names the system extensions rte_ckeditor and fluid_styled_content by their extension keys since 2.4. A classic installation resolves its dependencies from that file, so both have to be active. See Important: Dependencies are named by their extension keys.

A site package that ships its own Configuration/AcademicJobs/Settings.yaml changes it in the same deployment as the update:

• Replace number with tel on contactPhone , or remove the field from the file so the shipped flags apply. The shipped file of 2.3 marked the field with number , and so does a copy of it. The flags reach the backend record editor of a job now, and a number there stores +49 30 123 as 49 when an editor saves the job. Move a TCA override of required or readOnly of a job field into the settings file, the settings win over it now. See Breaking: The job validation settings reach the backend and Important: The new job form stores the chosen values.
• The files of all packages are merged per field now. A field the copy left out to make it optional keeps the flags academic_jobs ships. Name it with an empty list instead, and drop the fields the site package does not change. See Breaking: The job validation settings are merged per field.
• Flags are read regardless of case, a flag outside the shared vocabulary is ignored, and readonly , disabled and frontendreadonly take effect. Check the flags of the file against Validation settings, see Important: The job validation flags follow the persons vocabulary.

A site without the site set also includes the page TSconfig of the components in the same deployment, or the content elements are not offered for new content, see Include the components.

The module paths on this page are those of TYPO3 13, where the upgrade runs.

Update TYPO3 first 

Update TYPO3 to 13.4.35 or later while the site still runs 2.3, which supports TYPO3 13.4. Version 3.0 no longer installs on TYPO3 12, and Composer and the Extension Manager refuse it next to an older patch release of TYPO3 13.

Stay on TYPO3 13 until the upgrade is complete. The content element wizard academicJobs_pluginContent of this extension reads the column tt_content.list_type , which TYPO3 14 removes, so it only runs on TYPO3 13. The same holds for the content element wizards of academic_persons, academic_persons_edit and academic_projects when the installation also has them. Move to TYPO3 14.3.7 or later once they have run.

See Breaking: Removed TYPO3 v12 support and Important: TYPO3 13.4.35 or 14.3.7 is required.

Update the package 

composer require -W \
    'fgtclb/academic-base':'~3.0.0' \
    'fgtclb/academic-jobs':'~3.0.0'

On a classic installation, install environment_state_manager 2.x from the TER in Admin Tools > Extensions first, then update academic_base and academic_jobs there, in this order. Run the commands of this page with typo3/sysext/core/bin/typo3 instead of vendor/bin/typo3 .

vendor/bin/typo3 cache:flush

Update the database 

vendor/bin/typo3 extension:setup

Or apply the changes in Admin Tools > Maintenance > Analyze Database Structure.

For this extension the comparison adds and changes:

• company_name , sector , required_degree and contractual_relationship of tx_academicjobs_domain_model_job become nullable. No data is converted, see Important: Four job columns are nullable now.
• l10n_source is added to the same table, where a translation records the record it was made from. Existing rows get 0 , see Important: The job table records its translation source.

It also applies the changes of the index definitions TYPO3 13.4.35 and 14.3.7 bring.

Run the upgrade wizards 

The wizards need the database changes of the previous section. Run them on TYPO3 13, in this order, in Admin Tools > Upgrade > Upgrade Wizard or on the command line.

1. academicJobs_contactRelation, Migrate job contact records from relation to fields directly in the job record. It copies the contact record of a job into the contact fields of the job. Up to 2.3 it left out every job that was hidden, scheduled or expired while it ran, which includes every job submitted through the frontend form and not yet approved. It now reads every job and leaves a job alone that has a contact of its own. An installation that already ran it has it recorded as done and marks it undone first. For a wizard that was never recorded as done, the command reports an error, which is harmless. Then run the wizard:

   vendor/bin/typo3 upgrade:mark:undone academicJobs_contactRelation
   vendor/bin/typo3 upgrade:run academicJobs_contactRelation

   Copied!

   Read Important: The job contact wizard migrates invisible jobs before running it: a job whose contact fields an editor emptied on purpose gets its old contact back.

2. academicJobs_repairNewJobFormValues, Repair the jobs stored by the old new job form of academic jobs. It moves the start date and the application deadline the old form stored with the time of day of the submission to whole days, and lists the jobs that kept an unchosen Employment Type or Job Type for an editor. It writes the database directly, in the time zone of the process that runs it, and a wrong zone moves the dates in a way that cannot be taken back. Check the time zone its description names first. If it is not the zone the form ran in, set $GLOBALS['TYPO3_CONF_VARS']['SYS']['phpTimeZone'] , or run the wizard from the upgrade module, which runs in the web server like the form did:

   vendor/bin/typo3 upgrade:list
   vendor/bin/typo3 upgrade:run academicJobs_repairNewJobFormValues
   vendor/bin/typo3 cache:flush

   Copied!

   Keep the list of jobs it prints, it is shown once. Correct those jobs in the backend. See Important: A wizard repairs the jobs of the old new job form.

3. academicJobs_pluginContent, Migrate plugin list element from academic_jobs to normal content elements. It turns every content element that is still stored as Insert plugin with one of the plugins academicjobs_newjobform, academicjobs_list or academicjobs_detail into a content element of the type of the same name. Such elements are left from version 1.x. The wizard reads tt_content.list_type , which TYPO3 14 removes, so run it before the core moves to TYPO3 14, by its name:

   vendor/bin/typo3 upgrade:run academicJobs_pluginContent

   Copied!

   Once the column is gone, the wizard finds nothing to do, and the elements it would have migrated keep a type nothing renders. TypoScript, page TSconfig or SQL of a site package that names one of the plugins through list_type matches on CType instead. See Breaking: Extbase plugins require CType on TYPO3 v14.

A wizard that TYPO3 recorded as done is offered again once it is marked undone. TYPO3 13 marks a wizard undone with vendor/bin/typo3 upgrade:mark:undone <identifier>.

Adapt the configuration 

The TypoScript and the page TSconfig are delivered per content element since 2.4, and the three content elements are hidden in the whole installation until the page TSconfig of their component is included. See Breaking: Site sets and static templates have been restructured.

vendor/bin/typo3 academic:upgrade:check

vendor/bin/typo3 academic:upgrade:check academic_jobs --site=<site identifier>

Adapt templates and assets 

plugin.tx_academicjobs.view.partialRootPaths {
    -1 = EXT:academic_base/Resources/Private/Partials/
}

Adapt your code 

• A class that extends \FGTCLB\AcademicJobs\Domain\Repository\JobRepository and overrides findByJobType() adds the parameter bool $includeHidden = false . One that declares findAllJobs() or findUidsWithHiddenDefaultRecord() renames it. See Breaking: Extended JobRepository method signatures.
• A listener of \FGTCLB\AcademicJobs\Event\AfterSaveJobEvent that sets a redirect page of 0 or below now sends the visitor back to the form page, which shows the form and the confirmation, see Important: A redirect page of 0 or below from a listener means none.
• Code that reads the answer to a submitted job gets an empty 303 now, and a page that renders the messages of the form no longer gets the error message of Extbase after a rejected submission, see Important: The job form returns to its page with the confirmation.
• A listener of \FGTCLB\AcademicBase\Event\ModifyTcaSelectFieldItemsEvent that changes the job types of the job record changes the option Job Type of the job list as well now. One meant for the record alone returns early when flexParentDatabaseRow is set, see Important: Job list offers the job types of listeners.
• A listener of \FGTCLB\AcademicJobs\Event\ModifyJobControllerNewActionViewEvent is no longer called. It listens to \FGTCLB\AcademicBase\Event\ModifyPluginViewEvent instead and returns early for every other plugin, see Breaking: The view event of the new job form is gone, Feature: The plugins dispatch the plugin view event and ModifyPluginViewEvent.
• PHP code that uses \FGTCLB\AcademicJobs\Loader\AcademicJobsSettingsLoader , \FGTCLB\AcademicJobs\Registry\AcademicJobsSettingsRegistry or the exceptions of \FGTCLB\AcademicJobs\Exception uses the settings classes of academic_base, see Breaking: The validation settings classes of jobs were removed.
• Code that names \FGTCLB\AcademicJobs\SaveForm\FlashMessageCreationMode imports \FGTCLB\AcademicBase\Form\FlashMessageCreationMode . The old name keeps working until version 4.0, see Deprecation: FlashMessageCreationMode moved to EXT:academic_base.
• The FlexForm files moved from Configuration/Flexforms/Core12/ and Configuration/Flexforms/Core13/ to one file each in Configuration/FlexForms/. Own TCA that names a data structure of this extension by its path takes over the new one, see Important: The FlexForm files moved to Configuration/FlexForms/.

Check the result 

• The upgrade check exits with 0, without and with the extension key, see The upgrade check.
• The content elements Job Form, Job List and Job Details, as they are called now, are offered for new content on the pages that should have them, and existing ones keep their type. See Important: Content elements have new titles and descriptions.
• Jobs that were hidden, scheduled or expired when the contact wizard first ran show their contact.
• The jobs the repair wizard listed carry a chosen employment type and job type.
• The header of the job content elements appears once.
• A job submitted through a form without a redirect page returns the visitor to the form, which shows the confirmation.
• Saving a job in the backend keeps its contact phone number, and a job without a company name or a description can only be saved there once both are filled in, unless the settings make them optional.
• A job submitted through the form reaches the editors. A notification mail that cannot be sent is logged instead of failing the form, so check the log after a change of the mail configuration, see Important: A notification mail that cannot be sent no longer fails the form.
• Jobs submitted with 2.3 may share one logo file. The query in Important: An uploaded job logo no longer replaces an existing file finds them. A logo uploaded now is stored with a random suffix to its file name, and a form shown again with errors asks for the logo once more, see Important: Job image upload uses native Extbase upload handling.