Thread

Hello!  I’ve finally updated from 1.7 to 2.x and now my Persian language has disappeared from the site. This is supposed to be a bilingual site.  I have a feeling there is a simple setting somewhere (UTF?) to change. 

I got it to work before with 1.x but forgot how.

Help!

Thanks!
http://planiran.com

Now I’m worried.  It looks like I can type fresh Persian into the site, but somehow all previous Persian has been turned into question marks.  A database explosion?

Also, mysteriously, the “Status” box doesn’t work, so I can’t post new articles since I can’t “open” the status. 

Actually, it disappeared, although under channel administration, default status is set to open.

Hi RezwanR,

I’m sorry you’ve bumped into this problem. It’s not an imposible fix!

The “?” are the result of double-encoded data. As part of the upgrade process, ExpressionEngine converts your database to UTF-8. However, if any data is already set to UTF-8, it will be re-encoded and you will see the “?” or other bizarre characters.

Essentially, you need to roll back to the pre-upgrade state. Follow the the Wiki on Troubleshooting Upgrade Errors for a walkthrough on how to do that.

Once you are back on the pre-upgrade version, read this answer to prevent the double-encode.

Let us know if you need anything else!

~

Thanks Dan!

Essentially, you need to roll back to the pre-upgrade state. Follow the the Wiki on Troubleshooting Upgrade Errors for a walkthrough on how to do that.

I read the troubleshooting guide but didn’t see what I need to do.  By “roll back” do you mean uninstall EE2.x, reinstall 1.7?  Or delete the database and upload the backup?  Or both?  The wiki didn’t have directions for that as far as I could see.

Thanks! 

Also, the status box problem is bad.  I’ve gone in to change some of the posts by hand, and then they disappear. 

My edits and new posts aren’t showing up either.  In “Options” I see that I no longer have the drop down menu for status.  (It should be “closed” and “open”)

Over in Channel preferences: Statuses - the option is still there, clearly visible, and the default is set to open.

Why is it not in the publish form?  Image of the AWOL status menu was attached above.

Thanks!

Hello! 

I really need some help with the status issue.  I can’t post any new articles and some of the key older ones that I edited have disappeared. 

This site needs to function!

Best regards,
Rezwan

Hi Rezwan,

Yes, what Dan was suggesting is to scrap the current version of the site that you’re running with EE 2. By “roll back” he means that you should restore the upgrade of your EE 1-based site that you took before upgrading to EE 2. Once you’ve restored your EE 1-based site, follow the instructions outlined in this forum post.

Hi Rezwan,

Yes, what Dan was suggesting is to scrap the current version of the site that you’re running with EE 2. By “roll back” he means that you should restore the upgrade of your EE 1-based site that you took before upgrading to EE 2. Once you’ve restored your EE 1-based site, follow the instructions outlined in this forum post.

???

I don’t know that I upgraded the EE1-based site before upgrading to EE2.  I just did a backup (and don’t know if that worked - I have a zipped file, whatever that is) and then did the upgrade to EE2.

So, by “scrap”, do you mean use the ftp to go in and delete the system folder?  Or use mysql and go in and erase all the folders therein?  Delete the database? 

I’m not sure how to do that.

And then re-install the database? 

And that should be whatever I had before I did the upgrade?

Are there step by step directions for this?  Blanket verbs like “Scrap” and “Restore” don’t work for me.

And are you saying this is also related to the status bug?

Hi Rezwan,

Is there someone you trust who has some experience working with PHP-based applications and MySQL? It sounds like there’s a lot of hesitation here, and if you uncomfortable performing these kinds of tasks, then I certainly don’t want to encourage you to do something that might cause some serious damage to your site.

To broadly explain, what we’re recommending here is for you to abandon the current site since the data in the database is corrupt (having been double-encoded). You should have a backup of the EE 1-based site from before you upgraded to EE 2 since that is recommended in the documentation and again as a confirmation box that you must accept before proceeding with the upgrade. You said you had a zip, which might be the backup, but I’m not 100% positive since you don’t sound too confident. Did you have anyone assist you with the upgrade process?

Hi Kevin,
I think I would be able to do this, but I noticed from the other post that those guys who were experienced didn’t bother with the reinstall but just corrected the errors.  I am happy doing that as well. I don’t have that much that I have to change.  I may do it, but I’m trying to avoid it.

The unavoidable problem is the status button.  Is that also a data corruption problem?  It seems a separate issue.

Best, Rezwan

It looks like the fix Mike used in the other thread was to manually go through and edit every post to remove the errant characters. You could certainly do that if your site doesn’t have too many entries, but that doesn’t solve the encoding problems elsewhere in the site (parts of the database that were double-encoded that weren’t entry content).

I can almost guarantee that any other weirdness you’re experiencing with the site (like the status menu) is the result of having a corrupt database. Believe me, you need to do this one again, and there’s no point in fixing little things in the site if you’re going to wipe the database and give the upgrade another go.

I strongly recommend that you not try to salvage this upgrade. Please restore the backup you made before upgrading and try it again, and take Dan’s advice for preventing the double-encoding from happening again.

Believe me, you need to do this one again, and there’s no point in fixing little things in the site if you’re going to wipe the database and give the upgrade another go.

I strongly recommend that you not try to salvage this upgrade. Please restore the backup you made before upgrading and try it again, and take Dan’s advice for preventing the double-encoding from happening again.

OK.  About that.  Here’s a screengrab of the database backup files.  Does that look like I did a proper backup?  Did 2 types.  I also have older versions in case I did it wrong this time.

And I did download/copy the whole system folder, so I have that.  My concern is that I might not have backed up the individual multiple site theme folders and such from before - this is a 3 site site. 

Will that make it very tricky? 

And do you have a link to instructions on how to wipe the database and give it another go?  My host is enginehosting.com if that helps.

And do you have a link to instructions on how to wipe the database and give it another go?  My host is enginehosting.com if that helps.

If I recall correctly, EH will create a backup of your site files and database on request. Ask them about this, because if they’ll do it, that’s the best way to ensure you’ve got the backup you need. While the SQL file in your screenshot is the right type of file for a database backup, I can’t guarantee it’s a good backup by looking at the file name.

Hello!  FYI, I uploaded the old database and saw that it (ee1.7) has things coded in latin_1_swedish_ci whereas the new stuff (ee2) is in utf-8_general_ci - I thought it would be the other way around.

In any case, I made a backup of the corrupted database just in case, and will now delete it and try this again.

Happy Labor Day!