Jump to content


Issue information

  • #034417

  • Cannot Reproduce

  • -

  • -

  • 0 - None Assigned


Issue Confirmations

  • Yes (0)No (0)
Photo

Since upgrading ip.chat to 1.4 my blog description went missing

Posted by Breadfan on 08 November 2011 - 08:43 PM

I also noticed, when setting up Dynamic Headers, whatever logo I try to upload, it always shows the default forum logo. The logo description is completely missing.

Same happens on the default skin. Since I did the upgrade first on my live board, I decided to reproduce by upgrading to ip.chat on my localhost copy in which blog header worked just fine.

Guess what? Same happend on the localhost after the upgrade: blog logo always displays the board logo and there's no blog description. The tiles seem to be functioning though the blog banner area width is also using the default board height.

Ok, I disabled IP.Chat and the headers were back with the desc..everything worked fine. I then re-enabled Chat app and the blog headers were still there. I guess re-enabling did the trick?

I must note that I previously tried recaching and using the Template tools options but it didn't work.


moved issue from IP.Blog

I had same problem. Disabling chat and then re-enabling cleared it for me as well. Thanks


changed status to: Cannot Reproduce

Posted Image

I can't imagine any way whatsoever that installing/upgrading/enabling IP.Chat could effect blog dynamic headers. :blink:  The two are completely unrelated and share no central code, etc.

If anyone can reproduce this, please submit a ticket before reinstalling IP.Chat so that I can see it in action.  Unfortunately, this is one of those issues I'd need a live example of the problem to troubleshoot in order to resolve.


^^Well, already 2 persons had this problem: Bethanyrayne and me. I have a copy of my live board on localhost and I managed to reproduce it there. It's not a biggie IF you figure out you need to re-enable chat but for some folks it could be a real problem.


Well, tis why I added a note here to not reinstall and to instead submit a ticket so we can troubleshoot. :)  If I can get an example of somewhere this is reproducible, I am happy to look into it.  I did not reinstall locally and did not have a problem, so I'm at a bit of a loss on where to go from there.






1 user(s) are reading this issue

0 members, 1 guests, 0 anonymous users