Forums / Cotonti / Patches / Migration from Seditio 121/125 to Cotonti 0.0.2

12>>>

medar
#1 2009-02-01 17:07
1. Unzip Cotonti 0.0.2 release in some testing folder.

2. Copy to this folder from Seditio folder:
/datas/ all folders but not files
/plugins/ necessary
/skins/ necessary

3. Updating database.

There is two way to convert database.

UPD
Autoconvert
3.1.1 Use Seditio - Cotonti sql-updater. Unzip folder "updater" to Cotonti folder, set to folder rights 777, and launch updater/index.php .
3.1.2 Create in phpmyadmin database for future Cotonti database. Complete fields in updater and press Start.
All plugins will be deinstalled, all config values will be reset to default. Will set sed-light as default skin for admin.

OR

Manual convert.
3.1.1 Create in phpmyadmin copy of your seditio database and and follow these steps with this copy.
3.1.2 Convert database to utf-8. Instructions: eng, rus with ssh, rus without ssh.
3.1.3 Execute sql-update: http://www.cotonti.com/datas/users/sql_update_45.rar (one, for sed121 or sed125).
All plugins will be deinstalled, all config values will be reset to default. Will set sed-light as default skin for admin.
3.1.4 UPD install autoupdater from the previous step and execute "Postinstall correction".

4. Enter in admin area in your site and reinstall plugin Markitup.

5. Change config of site and install all necessary plugins.

6. Add in your skin new tags if necessary (see sed-light skin for details), Copy to your skin new tpl-files from sed-light skin.

7. Move Cotonti from testing folder to basic place instead Seditio.

Migration complete.
rangjungyeshe.ru
This post was edited by medar (2009-02-13 19:29, 15 years ago)
Lombi
#2 2009-02-02 02:25
Actually no, migration is far from complete. We still need a UTF encoder for the "special character people" here. I'm not sure about russian characters, but all characters from eastern/southern europe are all messed up.
<a href="http://www.domenlo.com">Surreal Art</a>
Trustmaster
#3 2009-02-02 02:59
If you are going to migrate to Unicode, the database must be converted to UTF-8 before migrating to Cotonti. You must make a backup first. Then you can try something like this.
May the Source be with you!
This post was edited by Trustmaster (2009-02-02 16:09, 15 years ago)
n0fx
#4 2009-02-02 08:17
why must i convert my database to utf-8? Can't i use latin5 for cotonti?
https://www.ultima-strike.com
esclkm
#5 2009-02-02 08:21
UTF-8 is universal for all languages, you can try to use latin 5. But I think you will have only errors/ Convert db in utf -8 is really easy
littledev.ru - мой маленький зарождающийся блог о котонти.
снижение стоимости программирования и снижение стоимости производства разные вещи. Первое можно скорее сравнить с раздачей работникам дешевых инструментов, чем со снижением зарплаты
n0fx
#6 2009-02-02 08:27
I know utf-8 is universal for all language but I wondered latin5 is unsupported cotonti.

I understand, Thanks.
https://www.ultima-strike.com
Kilandor
#7 2009-02-02 11:20
I think you can use others. Just its better to use UTF-8, we actually wasn't on UTF-8 for a while on this site. Though I can't make any that maybe something might go wrong.
Trustmaster
#8 2009-02-02 16:08
Sorry, that note was for people who are switching to UTF-8. Traditional charsets should work just fine.
May the Source be with you!
m_ogz
#9 2009-02-02 17:36
But charset must be set on config.php, right?
Ne hasta bekler sabahı, ne taze ölüyü mezar, ne de şeytan bir günahı, seni beklediğim kadar;<br /><br />
Geçti istemem gelmeni, yoklugunda buldum seni, bırak vehmimde gölgeni, gelme artık neye yarar...
Trustmaster
#10 2009-02-02 17:41
Normally it is in Admin => Skins => HTML Charset. That setting in config.php is optional, if problems with MySQL encountered.
May the Source be with you!
foxhound
#11 2009-02-03 07:12
First let me thank all involved in this great project for their hard work. I have been reading the forums and some documentation tonight about Cotonti and as far as I can tell now this will be the next thing to do to improve my website. :D

However, I am a bit confused by the install instructions in the first post (updating from seditio).

# medar : 1. Unzip Cotonti 0.0.2 release in some folder.

So.......cotonti does not need to be installed in the root public_html (where seditio is installed now)? Well, it has to be in there I guess but it can be in a subfolder?

2. Copy to this folder from Seditio folder:
/datas/ all folders but not files

This means I will loose all files my users and I have uploaded when changing to Cotonti?

Migration complete.

I understand all following steps (sql etc) although I cant understand how it will work from within a subfolder.
I did read we can move to Cotonti without loosing anything.....so thats why I am confused reading the first post.
Sorry if I am just missing something obvious.



[edit]
Ahummm
Just ignore me (should not be a problem here though). This is all for setting up a test site............
Remind me to not ask questions after a busy day of work.
<img src="http://www.armaholic.com/datas/thumbs/green-sea-battalion-uniforms-version-03-preview_4.jpg" alt="green-sea-battalion-uniforms-version-03-" />
This post was edited by foxhound (2009-02-03 20:24, 15 years ago)
donP
#12 2009-02-03 16:49
# Trustmaster : Sorry, that note was for people who are switching to UTF-8. Traditional charsets should work just fine.

My database actually has utf8_unicode_ci collation but my seditio 121 website always had setted-up to ISO-8859-1 charset.
Now, after migration to Cotonti (in local), all goes fine except markitup preview that shows strange characters instead of italian accented letters (àèéìòù).
TExtboxer also had that problem but I solved changing the preview code in js like I explained in this Neocrome Forum...
What can I do with markitup preview?
Please, help me... :-(
in [color=#729FCF][b]BLUES[/b][/color] I trust
Trustmaster
#13 2009-02-03 18:24
# donP : My database actually has utf8_unicode_ci collation but my seditio 121 website always had setted-up to ISO-8859-1 charset.
Now, after migration to Cotonti (in local), all goes fine except markitup preview that shows strange characters instead of italian accented letters (àèéìòù).
TExtboxer also had that problem but I solved changing the preview code in js like I explained in this Neocrome Forum...
What can I do with markitup preview?
Please, help me... :-(
Make sure you have chosen correct charset in site configuration. Usually the problem is connected with default charset in PHP output, or your webserver's default charset.
May the Source be with you!
donP
#14 2009-02-04 05:21
In Admin/Skin config I've set ISO-8859-1 / Western Europe, and ISO-8859-1 in datas/config.php...
In addiction, I have no problems in preview if I use fckeditor instead of markitup...

Another problem with markitup: no automatic refresh in preview (despite the fact I set that value in plugin configuration)...
in [color=#729FCF][b]BLUES[/b][/color] I trust
Trustmaster
#15 2009-02-04 05:59
You see AJAX uses UTF-8 by default, that's why previews are often messed. But sending correct header() with exact charset usually fixes the problem. But seems like not in your case.
May the Source be with you!

12>>>