Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
S
sg_jobs
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TYPO3
sg_jobs
Commits
b40af577
Commit
b40af577
authored
6 years ago
by
Kevin Ditscheid
Browse files
Options
Downloads
Patches
Plain Diff
[TASK] Add migration advices in the readme
parent
a5c0d796
No related branches found
Branches containing commit
Tags
1.6.3
Tags containing commit
1 merge request
!10
Feature departments
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+13
-1
13 additions, 1 deletion
README.md
with
13 additions
and
1 deletion
README.md
+
13
−
1
View file @
b40af577
...
...
@@ -8,7 +8,7 @@ Repository: https://gitlab.sgalinski.de/typo3/sg_jobs
Please report bugs here: https://gitlab.sgalinski.de/typo3/sg_jobs
TYPO3 version: >
7.6
TYPO3 version: >
8.7
## About
This extension provides job application functionality for a TYPO3 installation.
...
...
@@ -76,3 +76,15 @@ access from the .htaccess file. Example:
```
RedirectMatch 403 ^/fileadmin/JobApplication/.*$
```
## Migration from version 1 to version 2
If you update from sg_job version 1, you need to execute the Upgrade Wizard, that migrates the old area field.
To do so, please visit the Install Tool and click on Upgrade Wizards. Check the Job Upgrade Wizard and execute it.
This Wizard will migrate your area data into department records.
Also please be aware of changes to the Fluid template regarding the area -> department migration and change the area
occurences of variables in the template to department records accordingly.
This version also introduces correct exclude field configurations for the tables, so check your backend user
and backend usergroup permissions and adjust them accordingly.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment