Thread

This question may be related to a resolved thread.

Exactly the same issue as the Post above. Just updated a site from 1.6.8 to 2.1.3 build 20101220.

This site only has 2 members total and they are both Super Admins. I’m going to go reset this in the database.

Is this a squashed bug for the next release, or do we need to report this one?

Kurt,

Is this a squashed bug for the next release, or do we need to report this one?

It hasn’t been reported as a bug as we have not been able to replicate it. That related thread and yourself are the only reports so far

Do you have any similar add-ons to the the other user?
Can you remember if 1.6.8 was a fresh install or had it been upgraded from a previous version?

Hi John,

I believe that this site started out years ago in pMachine, I know the owner has been around the community for that long and there were references to pMachine in the config file I moved over.

Since an update to EE 2.1.x and/or a move up in PHP versions will break most older vintage add-ons, I don’t move any of that stuff to a new site and didn’t look to see what was installed. We did have to uninstall the wiki in order to get this site’s data through the upgrade scripts in the installer.

The only thing that really stands out about this site to me, is that it has only 2 members, and both are super admins.

The site is a classic blog, with only a half dozen non-blog content pages and thousands of blog posts so it didn’t need many add-ons for functionality like some of the CMS sites EE is used for today.

When we move a client from 1.6.x to 2.1.x we try to abandon the old site and not start the new site with old data, we just do a clean instal and move content over by hand. With close to 4,000 blog entries, that wasn’t an option this time.

Every time we’ve had to build on a converted site, we’ve run into strange things like this. That said, EE 2.1.3 is pretty stable and with the exception of all the issues right now with the Category editing, sorting and such, has been the best yet. The rest of it seems to have done the update well, including the tabs in the publish page that were such a mess for months last year.

Looking forward to 2.1.4!

Kurt,

Thanks for the follow-up and history. I honestly don’t see a way through to troubleshoot this at this stage unfortunately. If you have anther site similar that you are going to upgrade maybe we could revisit it and check those database tables before where there may have been some legacy data. I hope you understand that.

With close to 4,000 blog entries, that wasn’t an option this time.

Take a look at DataGrab. IT truly is an excellent add-on. I did a site recently and imported over 10,000 entries from a different CMS altogether

Hi John,

Troubleshooting this would be time consuming and ugly, I mostly just want folks to be aware of it so that others will find as quick a resolution as I did in the related post, and so that the dev-team has an early warning in case this turns out to be a symptom of a larger issue.

There are many other things I would like to see resolved before this one. I would rather time be spent fixing bugs, fixing disabled features, and working on feature requests. I know the team is working on these things, and I’m confident things will get better.

I had considered a tool like DataGrab, but had no clue how it would convert Trackbacks into comments and some of the other nice little things the Installer/Updater scrip does.

The main reason we’ve not done data imports though is that frequently we’re inheriting EE sites where the initial data structure (using 19 custom channel fields when only 3 or 4 are needed) are so messed up, that we really need to start over with the good old “less-is-more” and DRY methods. As you know EE is an amazingly flexible tool… and that gets some folks into a huge mess.

That DataGrab does sound cool…. hm….

DataGrab would be a great use to clean out those kinds of entries. It can even import RSS feeds.

Anything else we can help you with?