|
|
38.
|
|
|
Once b2evo is up and running, in the admin, go to the Tools tab and launch the WordPress import utility.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/upgradefrom_wp.src.html:37
|
|
|
39.
|
|
|
Follow the instructions on screen and provide connection information to your WordPress database (Read Only)
|
|
|
|
|
Postępuj wg instrukcji na ekranie i wprowadź informacje dla połączenia z bazą danych Wordpress (tylko do odczytu)
|
|
Translated and reviewed by
skrzat
|
|
|
|
Located in
../../doc/upgradefrom_wp.src.html:38
|
|
|
40.
|
|
|
Import will only take a few seconds/minutes depending on how many posts you import.
|
|
|
|
|
Import potrwa tylko kilka sekund/minut, w zależności od ilość wpisów do zaimportowania.
|
|
Translated and reviewed by
skrzat
|
|
|
|
Located in
../../doc/upgradefrom_wp.src.html:39
../../doc/upgradefrom_mt.src.html:41
|
|
|
41.
|
|
|
To install b2evolution you need a PHP/MySQL web server (see <a %s>requirements</a>). Renting a fast server from a reputable hosting company is getting cheaper every day. Check out our <a %s>recommended hosting offers</a>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:35
|
|
|
42.
|
|
|
Once you have unzipped the b2evolution distribution on your local computer:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:37
|
|
|
43.
|
|
|
On your server, try to create a new (empty) MySQL database for b2evolution (For example, you can call it "b2evolution". The exact procedure to create a new database depends on your host/server setup. Alternatively, you can also use an existing database which b2evolution will share with existing applications.)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:39
|
|
|
44.
|
|
|
Note:
|
|
|
|
|
Uwaga:
|
|
Translated and reviewed by
skrzat
|
|
|
|
Located in
../../doc/install_new.src.html:41
../../doc/install_new.src.html:44
|
|
|
45.
|
|
|
b2evolution will create about 25 tables in the database you select. Unless you changed the config, all these tables' names will be prefixed with evo_ . Unless you already have an application using the same prefix, this makes it safe to install b2evolution in a database shared with other applications. Your existing tables will not be affected in any way.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:41
|
|
|
46.
|
|
|
Upload the b2evolution files to your website.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:42
|
|
|
47.
|
|
|
Only the contents of the <code>/blogs</code> directory need to be uploaded to your site. If you want b2evolution to handle the homepage of your site, upload the contents of the <code>/blogs</code> folder to your website root. Otherwise, it's best to upload the files to a subdirectory of your webserver. You can keep the <code>/blogs</code> subdirectory name, but you can also choose another.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../doc/install_new.src.html:44
|
