-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathUPGRADE FROM 1.1.x RC3
executable file
·101 lines (74 loc) · 3.61 KB
/
UPGRADE FROM 1.1.x RC3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
Upgrade from 1.1.x RC3
----------------------
This document explains in detail how to migrate from AlphaLemon CMS RC3 to RC4. If you
come from a the Beta4 release or older, read the paragraph at the end of this document.
Database backup
---------------
It's strongly suggested to backup your database before start with this upgrade. You can
use a tool like phpmyadmin for that.
Composer dependencies [IMPORTANT]
---------------------------------
Since Release Candidate 4, AlphaLemon CMS does not require anymore the editor for hypertext
blocks, neither the default theme, so you must require them explicitely in the main
application's composer.json file, if you need them:
{
[...]
"require": {
[...]
"alphalemon/app-tinymce-block-bundle": "dev-master",
"alphalemon/bootbusiness-theme-bundle": "dev-master",
},
}
Be careful and sure to add the "alphalemon/app-tinymce-block-bundle" requirement, if
you do not use another bundle which manages hypertext blocks.
If you want to use the CKEditor instead of the TinyMCE editor, just require the
alphalemon/app-ckeditor-block-bundle instead of alphalemon/app-tinymce-block-bundle.
Update the database
-------------------
AlphaLemon CMS RC4 introduces a new table in the database, so it must be updated to get
this new entity.
The upgrade process is really easy. After you upgraded you AlphaLemon CMS application,
just open a terminal and run the following commands:
./php app/console --env=alcms alphalemon:update-to-1-1-x-RC4 "[DSN]"
Between double quotes add your dsn. If you don't remember it, open the app/config/config_alcms.yml
file and read it from the Propel's configuration:
propel:
path: "%kernel.root_dir%/../vendor/propel/propel1"
phing_path: "%kernel.root_dir%/../vendor/phing/phing"
dbal:
driver: mysql
user: root
password:
dsn: mysql:host=localhost;port=3306;dbname=alphalemon
Upgrade from AlphaLemon CMS Beta4 or older
------------------------------------------
If you need to upgrade from an AlphaLemon CMS 1.1.x Beta4 version, you must upgrade to
AlphaLemon CMS RC3 and do all the required upgrades. After that you will be able to
upgrade to AlphaLemon CMS RC4, as explained in this documentation.
AppKernel bug fix
-----------------
Open the app/AppKernel.php file and change the following code:
public function registerContainerConfiguration(LoaderInterface $loader)
{
$configFolder = __DIR__ . '/config/bundles/config/' . $this->getEnvironment();
$finder = new \Symfony\Component\Finder\Finder();
$configFiles = $finder->depth(0)->name('*.yml')->in($configFolder);
foreach ($configFiles as $config) {
$loader->load((string)$config);
};
$loader->load(__DIR__.'/config/config_'.$this->getEnvironment().'.yml');
}
as follows
public function registerContainerConfiguration(LoaderInterface $loader)
{
$configFolder = __DIR__ . '/config/bundles/config/' . $this->getEnvironment();
if (is_dir($configFolder)) {
$finder = new \Symfony\Component\Finder\Finder();
$configFiles = $finder->depth(0)->name('*.yml')->in($configFolder);
foreach ($configFiles as $config) {
$loader->load((string)$config);
};
}
$loader->load(__DIR__.'/config/config_'.$this->getEnvironment().'.yml');
}
This prevents an exception thrown when you add or remove a Block / Theme.