Jump to content

DO NOT UPGRADE to 4.0.13.1


Gauravk

Recommended Posts

Posted

I have upgraded it successfully to 4.0.13.1 and everything looks good. And after 4 days I realized today that one of the IP Content database is not showing any fields while displaying the records. I had a classifieds database having about 12-15 fields and only one is showing for image. Total disaster and my community members are getting furious with this now.

Look's like a serious database conflict issue, as I reported this to support and they have been absolutely silent since few hours. Anyone thinking of upgrading from 4.0.13 to 4.0.13.1 please wait.

Posted

Good for them whose sites are fine. In my site one of the IP Content Database inside pages failed.

Mine is still in ICU with handicapped capability and doctors are still working and Im waiting outside the OT since over 2 days :-(

Lesson learned: After every test upgrade personally visit every million-billion pages to make sure upgrade worked fine before pushing to live site. Or never upgrade FULL-STOP.

Posted
9 minutes ago, Gauravk said:

Good for them whose sites are fine. In my site one of the IP Content Database inside pages failed.

Mine is still in ICU with handicapped capability and doctors are still working and Im waiting outside the OT since over 2 days :-(

Lesson learned: After every test upgrade personally visit every million-billion pages to make sure upgrade worked fine before pushing to live site. Or never upgrade FULL-STOP.

4.0.13 > 4.0.13.1 would not have caused an issue like this, the update contained one single CSS change.

Posted
5 minutes ago, Gauravk said:

Thanks Stuart for making an educated guess, but it actually happened coz of 4.0.13.1

Check below Test url (org) is 4.0.13 and live url (com) 4.0.13.1 :-(

 

I'm certainly not saying that you don't have an issue after upgrading. I'm just saying that it isn't something included in 4.0.13.1 over 4.0.13.

The only change in 4.0.13.1 waschanging

max-width: 0;

to

width: 0;

 

Posted
29 minutes ago, Gauravk said:

Check below Test url (org) is 4.0.13 and live url (com) 4.0.13.1 :-(

That doesn’t prove anything. It could also be caused by other differences in these installations than just the x.x.x.1 release. For example: Just visiting the different sites one time as admin and one time as guest could produce such an result. (I am not claiming that this is what is happening, I am just saying that the screenshots can’t prove that the problem must be related to the upgrade.)

By the way: I remember that you reported exactly(!) that problem of missing Pages fields and claimed it was I bug in the past. And it turned out to be just the category field settings you selected. Could be something similar. But its impossible to tell from just the screenshots. 

Posted

Im not here to prove any point to any one and I don't want people to get defensive and too protective about IPB software. It's indeed made by humans and error, bugs, misconfig is bound to happen in initial stage, we all know that.

All the admin access, ftp access and all required access have been given to support and like I said before they are working on it and even they have escalated this issue to advanced support. So let's save thread-bashing in wrong direction.

An yes it has only happened due to 4.0.13.1 upgrade and NOTHING ELSE. As last backup done on 16 Sep, which is placed on test site as of now. And as per IPB software touch-me-not behavior, I am not running or ever installed any third-party applications, skins, or blocks. It's 100% stock with just color customization done from ACP.

I created this thread to let other IPB users know that this type of situation MAY happen and they should be careful before pushing test changes to live site. That's it.

Posted

No one is bashing in your direction.You are just making unnecessary drama. Just look at your words:

  • “Total disaster”
  • “furious community members” 
  • “a serious database conflict issue”

This in neither a “friendly warning” for community members nor a “polite request” for help.

Posted
6 minutes ago, opentype said:

No one is bashing in your direction.You are just making unnecessary drama. Just look at your words:

  • “Total disaster”
  • “furious community members” 
  • “a serious database conflict issue”

This in neither a “friendly warning” for community members nor a “polite request” for help.

beauty lies in the eyes of the beholder. lol. I like your choice of words, very funny.

Do you have any serious community running or just come here for helping ppl....? If you have a community imagine one of the module dies and your member calls you on hourly basis and few unknown guys leave such comment: http://carnity.com/classifieds/other-brands/jaguar-xj6-sovereign-r44/

Posted

Finally guys, problem resolved: Support star: Brandon found out that each database category has 4th tab to select the fields that needs to be shown and that was having only image field selected and rest was unselected and that was causing all this unexplained mystery. I selected all their and site classifieds is back to normal, phew......!

Wondering why this issue was not there in 4.0.13, as my test url (org) still has one field - image - selected but still shows all fields in frontend.

Capture.JPG

 

Posted
11 minutes ago, Edward Shephard said:

It's a volkswagon! Maybe it has some special software so that it will only display correctly when you're testing... :smile:

lol. not really it's in all brand categories it's showing all fields in test url, just double-checked right now.

Posted
6 hours ago, Gauravk said:

Finally guys, problem resolved: Support star: Brandon found out that each database category has 4th tab to select the fields that needs to be shown and that was having only image field selected and rest was unselected and that was causing all this unexplained mystery. I selected all their and site classifieds is back to normal, phew......!

So it was no bug and was EXACTLY the problem you had before, which was fixed before and explained to you before. I even mentioned it in my earlier comment

Posted
6 hours ago, opentype said:

So it was no bug and was EXACTLY the problem you had before, which was fixed before and explained to you before. I even mentioned it in my earlier comment

Really surprise to see how judgmental you got, take it easy. This IPB community forum is to help other IPB user's than bullying or putting other's down. It's better to keep quiet if you can't help someone than just getting into a useless argument.

It was a misconfig from previous version of IPB that got to surface with this upgrade. Read below for more techy details.

Capture.JPG

Posted
6 hours ago, Gauravk said:

Really surprise to see how judgmental you got, take it easy. This IPB community forum is to help other IPB user's than bullying or putting other's down. It's better to keep quiet if you can't help someone than just getting into a useless argument.

Firstly, I did help you. I was the one who found out the last time that this is caused by your category field settings — that’s why I remembered it and that’s why I repeated it here. You wouldn’t even had needed those two support tickets if you would actually listen to what I said. 

Secondly, it’s really baffling how you misrepresent my comments. I’m stating facts and giving my opinion – that’s what discussions are for. There is no “bashing” or “bullying”. Those words are not justified just because you might not like my comments. 

Posted

On a later note, I agree you tried helping but may be you are right that I did not liked your comment as your first words were: "That doesn’t prove anything" sounds more like we are in a court and some detective is challenging the victim than in an online community. And once you started with that comment, rest everything went to ignore mode.

Secondly you had a good point that hinted on the root problem, but why would I change any setting and cause more havoc in my live community as all same setting were working great until last version. Im not a techy geek, so I have to wait until support staff advise or suggest some action for testing purposes.

Anyways, Im glad all is over now and let's close this thread, and thanks for your help.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...