Zikula Community

• apslob
  
  

  • Rank: Registered User
  • Registered: Jun 30, 2009
  • Last visit: Nov 27, 2009
  • Posts: 8

  Posted: Nov 26, 2009 - 05:26 AM

  Is it possible to go back from 1.2 to 1.1.2?
  I noticed that I upgraded my site to early.
  
  Thanks,
  Piet

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Nov 26, 2009 - 07:24 AM

  Restore your file and database backup.
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• apslob
  
  

  • Rank: Registered User
  • Registered: Jun 30, 2009
  • Last visit: Nov 27, 2009
  • Posts: 8

  Posted: Nov 26, 2009 - 07:41 AM

  It is a live community enviroment. There is too much changed in the meantime.
  
  
  
  edited by: apslob, datetimebrief

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Nov 26, 2009 - 08:47 AM

  Then what is the reason that you want to revert to 112?
  
  I don't think there is an automatic downgrade solution, if you really want to do that it will be a difficult manual job I think. It might be easier to overcome whatever problem you have with 1.2
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Nov 26, 2009 - 09:25 AM

  Woops, there's no way to downgrade.
  What's your problem?
  weird chars on the screen? you should change the pnlang/ files to utf8...
  You must test the upgrade locally before put it live :-S
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• apslob
  
  

  • Rank: Registered User
  • Registered: Jun 30, 2009
  • Last visit: Nov 27, 2009
  • Posts: 8

  Posted: Nov 26, 2009 - 09:32 AM

  All kind of problems and bugs:
  
  -missing Dutch translation, had much trouble in a multi language environment
  -profile; 1.5 is much better but still not bug free
  -dizkus, datetime problem, problems with editing posts
  -eternizer; terrible user and datetime displays
  -simplegallery; cannot upload new photo’s anymore
  -admin panel has some display problems
  -character corruption; all characters like é and ë are displayed as �; the tekst in the database is ok
  - I don't know what possible problems are in content, news, newsletter, EZComments, addressbook and all kind of other modules but i am very suspicious.
  
  Lots of problems are solved with the updates of several modules and I can also see that everybody is working hard on the version 1.2. I also realize that it is my fault that I upgrade to the new version to soon.
  
  Can somebody tell me if it is possible just to restore the files and leave the (updated/upgraded) database as it is?
  
  Thanks
  
  
  
  edited by: apslob, datetimebrief

  • 
  •  
• pheski
  
  

  • Rank: Expert
  • Registered: Feb 27, 2005
  • Last visit: Apr 18, 2010
  • Posts: 1577

  Posted: Nov 26, 2009 - 09:55 AM

  apslob

  Is it possible to go back from 1.2 to 1.1.2?
  

  
  
  There's no downgrade path, if one has saved a backup of the files and DB, it should be pretty straightforward to restore the old site.
  
  (I learned the hard way how essential it is to have a current backup from which to restore whenever one makes significant changes. )
  
  
  
  edited by: pheski, datetimebrief
  
  --
  Peace
  ______________________________________
  The commonest cause of problems is solutions.

  • 
  •  
• Teb
  
  

  • Rank: Team Member
  • Registered: Feb 27, 2005
  • Last visit: Apr 12, 2010
  • Posts: 665

  Posted: Nov 26, 2009 - 12:03 PM

  apslob

  All kind of problems and bugs:
  
  -missing Dutch translation, had much trouble in a multi language environment

  
  Just a matter of not enough translators. Interested? :)
  

  apslob

  Can somebody tell me if it is possible just to restore the files and leave the (updated/upgraded) database as it is?

  Not possible AFAIK, since it's all converted to UTF-8. Not quite sure though if 1.1.2 has support...
  
  But, you could at least do it the right way now: Make a backup of your new, upgraded 1.2.0 environment. Copy that backup (at least the database) to a separate test-environment. Now also copy a backup of the files of your 1.1.2 site to that test-environment too. Finally, edit the config file, and try to set database character-encoding to UTF-8 (since that was all converted on your upgrade).
  
  Open the index file and pray :)
  
  --
  -- Teb
  -- Dutch Zikula Community
  
  Support questions in a Personal Message will be ignored. Use the forums at all times!

  • 
  •  
• apslob
  
  

  • Rank: Registered User
  • Registered: Jun 30, 2009
  • Last visit: Nov 27, 2009
  • Posts: 8

  Posted: Nov 27, 2009 - 01:56 AM

  Thanks to all for the fast replies.
  I have no test enviroment. Our website is running at the providers server. I am running on a Windows XP machine.
  We have decided to restore the backup.
  I will try to run the 1.1.2 files on the 1.2.0 database. Lets see what happens.

  • 
  •  
• Teb
  
  

  • Rank: Team Member
  • Registered: Feb 27, 2005
  • Last visit: Apr 12, 2010
  • Posts: 665

  Posted: Nov 28, 2009 - 12:54 PM

  With a bit more time, one could setup a test environment one the same server.
  Try putting the files in a subdirectory. For the database, you could import a copy in another database, or (if you only have one database) make a backup, and rename the tablenames by replacing a prefix. Then, modify that prefix in your config file, and you're good to go. I remember posting a bash script for this process here too.
  
  You need shell access to your server though, so skip this if you don't have that. I tested this only on a MySQL 5 environment. Use at your own risk, and at least test run it first somewhere!

  Code

  #!/bin/bash
  
  # Fill in correct values below
  dbuname=YOUR_DB_USERNAME
  dbpass=YOUR_DB_PASS
  dbname=YOUR_DB_NAME
  
  # Command below makes a complete backup of your existing database,
  # and gzips the result (handy for later use)
  mysqldump -u $dbuname -p$dbpass $dbname > $dbname.sql
  gzip $dbname.sql
  
  # Command below opens the backup, renames all tables in your gzipped file from nuke_* to zk_*, and
  # re-inserts them into the database. Change prefixes accordingly if necessary
  gunzip < $dbname.sql.gz \
   | sed -e 's/TABLE `nuke_/TABLE `zk_/g;s/TABLES `nuke_/TABLES `zk_/g;s/EXISTS `nuke_/EXISTS `zk_/g;s/INTO `nuke_/INTO `zk_/g;' \
   | mysql -u $dbuname -p$dbpass $dbname

  
  
  --
  -- Teb
  -- Dutch Zikula Community
  
  Support questions in a Personal Message will be ignored. Use the forums at all times!

  • 
  •  
•  
•  

Users on-line

• eledril

This list is based on users active over the last 60 minutes.