JohnPiantanida

I hope it works for you.

In an odd sort of way, I guess that is what I did. I am sure GoDaddy uses a ftp type file transfer, not just the WP auto-update or it would have already known I had used the auto-update a few days before. And it would have just recreated the problem if this post is correct.

Good luck!

It worked on all 3. And no, I did no changes to the PHP. Now maybe GoDaddy did an update or something. Not sure. Maybe that is part of the problem. I don’t know, just guessing, but maybe there was a PHP update that a few of us got bit with.

Or maybe there was a PHP config change for the WP update… but either way, all is fixed for now. No telling if it will hold or not. I wish I had more that would help you with your installation. If I hear of anything or can think of anything I will be back to let you know.

Okay… the first test done. And it fixed things. Using the host update (to 3.2) repaired the dashboard. Now I am going to try another one and see how that goes.

I am going to try a few things. I have no idea what will work, but as I go, if I make any progress I will let you know.

Still waiting on the illusion of the GD 3.2 update. It was already 3.2 but GD thought otherwise. So I am letting it do its thing on this installation to see what happens. I have a backup from a week ago… but I am not sure at this point it would help. Nothing changed at my end since then except adding posts on one of the 3 installs.

I am using my third install, as it was just set up as a place to test new ideas. It is the most recent. I thought it installed with version 3.2 or maybe I did the WP update same day. Either way, I know it was 3.2… not 3.1.4 as GD thinks. So I will see what happens. It is like the css file is missing or corrupt… “all blank” structure of the page, just the data and form boxes with an ugly font. All of the menu images are out of place, no tabular formatting, and that early VB boxy look to it.

Bizarre.

To add…

Now it is happening on all 3 installs. And GDaddy says I am using version 3.1.3 and 3.1.4, not 3.2 like WP says I am. I had not done the 3.2.1 update yet… didn’t know existed until just now.

I am doing the update on one of the sites using the GDaddy admin site to do it. I will post if this makes a difference. Up till now I always did my updates through WP not GD.

I had the same thing happen on 2 out of 3 installs, all on same server in same domain. It started around 7 hours ago… I don’t think it was due to the upgrade, as I did that several days ago and things were fine up until late this morning. Nothing else was changed or added since the upgrade so I don’t see how it could be theme or plug-in related.

I have seen this once before a few months ago, and it cleared itself up in less than an hour… but not this time. I just assumed it was a Go-Daddy problem when it happened before.

Who is your host blipfish? Is it Go-Daddy? If so, maybe it IS a problem at their end.

Thanks. It is another one of those “Live and learn” experiences.

I am curious what our blogs might have in common that caused this. Or maybe we are the only ones importing from LJ. ??

Either way, I am sure it would be useful to us and others if we knew the “why” to this happening. So if you figure out any more patterns or details, post them. It may not help us, but maybe we can help others in the future.

For me it started slow at end of 2010, one per post… then two… then three. The farther back, the fewer duplicates. But by early 2011 it grew fast, with the most recent 2 months being the worst. I was told by the person I am doing this for (my girlfriend) the comments were not so important.

But after reading them I reminded her this was part of her business history. I guess I am my own worst enemy here. So I went to the comments section in the control panel and have been working my way back from the end. This is a low volume blog, few posts, few comments for the most part. But at 159 dupes per comment (at this point in the posts), it is a slow process. I am up to January 24th, and still have 1062 pages more to clean. I wish there was a delete duplicate command.

Also, it is not in a language I can read (I have to use a translator program if I want to actually read them)…. which makes it even more of a challenge. But after an hour or so, you get a rhythm to the deleting. So I do a few hours every day. Sooner or later it will be done.

I want to start off by apologizing for my last post. I had gotten some very bad news yesterday evening when all of this was happening and it was wrong of me to take it out on you. I hope you will accept my apology. I was upset and frustrated. Normally I am a very calm thoughtful person.

I will look into cutting out the comments and doing another import. I will have to wait until the person I was doing it for is available to do a restore to the previous database. I will let you know how it goes.

And thanks, really thanks. I will try to behave better in the future.

Okay, I would like to thank you (WP employees, programmers, and shills) for all of your help.

Your silence as you respond to dozens of other “common” issues speaks volumes.

At least an “I don’t know, tell me more about the problem” would have been appreciated. That is how I treat people I work with, professionally, personally, and even just in forums I participate in.

We all know it is easier to ignore a problem than it is to admit there is one. That is the bane of all users of software products, yours and others. If issues come up, talk about the easy ones… ignore the rest. Of course it is easy to blast others (like MS) while doing it yourself.

I guess that is why so many 3.1 upgrades have gone bad. Just looking around at the forum, it is “assumed” in the replies that your final code is good. I doubt it from what I have read. If it was, there wouldn’t be 100’s of complaints a day.

Is there any QC in your programmers group? Or is it all 20 year old coders that feel they know everything and if it is not being done the way they envisioned, it is wrong?

I have recommended WP do dozens of people, and now I need to clean up all of the problems it has caused them. My bad. It will not happen again. In fact, the exact opposite…

Once again, thanks for the good work. {/sarcasm and former trust in WP support off}

Most of the time, I figure things out for myself when there is a problem. I am not a person that needs my hand held at every turn. It would help if there was some admission that there as a problem. At least I would know how to proceed.

Actually, I guess I do… don’t ask for help here. Sigh… I hoped this would be better, or at least for a simple response.

Once again… Thanks.

Back to work now. I have a deadline to fix this problem that has already passed, and I am not being paid. Sucks after a 10 hour day working on this… and knowing it is going to take at least 2 more days.

Okay, it looks like anything commented on or after Jan 7th 2011 is the problem.

Before that, it all has looked good.

Hmmmmmmm…..

Reminds of another problem I have seen in other systems. And I do not mean Y2K…

One of these systems (WP or LJ) has a bug in date interpretation. It is all just clock clicks from an arbitrary date. Somewhere in 1970 for most systems. The problems come with the role-overs… sigh.

Here I go again, having to compensate for myopic programmers who think in terms of weeks or months, and not years.

Am I the only one that has seen this problem?

Did someone not realize 2011 would sooner or later happen?

Another addition…

So far (I have only looked at 30 pages of the oldest comments so far) if I start at the end… the older comments were not duplicated. It seems the oldest (maybe archives were not duplicated?) were not duplicated. Still going with manual delete, with 1322 pages of comments still to go. Damn. 15 duplicates of each would have been much easier. ?? Before the comment import it was about 9 pages…

John

Edit to add: It seems to have imported each comment 159 times.

I did the math on a few posts, and this is the number I come up with.

John