July 06, 2007
Browser Issues.
The pictures on this blog don't seem to be visible with AOL or Internet Explorer
Firefox works fine at the moment.
According to Wonderduck this issue began sometime on the 4th.
Feh...
Comments are disabled.
Post is locked.
Firefox works fine at the moment.
According to Wonderduck this issue began sometime on the 4th.
Feh...
Posted by: The Brickmuppet at
08:39 PM
| Comments (7)
| Add Comment
Post contains 34 words, total size 1 kb.
1
I'll take a look and see if I can find out what's going on.
Posted by: Pixy Misa at Sat Jul 7 14:53:22 2007 (PiXy!)
2
Okay there is something interesting going on here. Yes, things are messed up in a browser-dependent way. Everything's fine in Firefox, but a number of things are broken in IE - and not the normal things.
I'll grab a copy of your blog to the test environment so I can take a proper look.
I'll grab a copy of your blog to the test environment so I can take a proper look.
Posted by: Pixy Misa at Sat Jul 7 15:20:37 2007 (PiXy!)
3
Thanks for the quick response.
"Interesting"...that sounds ominous.
I'm sorry my blog seem to be such a bother.
Thanks Again,
Ken
"Interesting"...that sounds ominous.
I'm sorry my blog seem to be such a bother.
Thanks Again,
Ken
Posted by: Brickmuppet at Sat Jul 7 22:22:34 2007 (V5zw/)
4
That's what it means to be part of a "beta". You and I have been turning up problems, and that's exactly what Pixy hoped we'd do. It's the reason he offered us free use of the system.
Better by far to find those problems now than to have them turn up after this place gets established with hundreds of paying customers.
Both of us are what are known as "black box" testers. The opposite is "white box" testing, which means that the tester understands the internals and is deliberately shooting for the places where problems are most likely to be found. Pixy has been doing his own white box testing.
But there's no substitute for black-box testing. "Black Box" testers don't know what's going on in the code so they attack with less predictability, across a wider front. To some extent a white box tester is limited by his preconceptions, but black box testers have no such limitations and will find some of the damndest things. I speak as a software developer myself when I describe this, and believe me, black box testing is essential.
So don't apologize for making things break. I haven't been. You and I have been doing exactly what Pixy hoped we'd do: to use the system heavily and to turn up problems he himself can't find.
Better by far to find those problems now than to have them turn up after this place gets established with hundreds of paying customers.
Both of us are what are known as "black box" testers. The opposite is "white box" testing, which means that the tester understands the internals and is deliberately shooting for the places where problems are most likely to be found. Pixy has been doing his own white box testing.
But there's no substitute for black-box testing. "Black Box" testers don't know what's going on in the code so they attack with less predictability, across a wider front. To some extent a white box tester is limited by his preconceptions, but black box testers have no such limitations and will find some of the damndest things. I speak as a software developer myself when I describe this, and believe me, black box testing is essential.
So don't apologize for making things break. I haven't been. You and I have been doing exactly what Pixy hoped we'd do: to use the system heavily and to turn up problems he himself can't find.
Posted by: Steven Den Beste at Sat Jul 7 22:51:22 2007 (+rSRq)
5
Hmmm, I seem to have failed my post roll as well...
OK, here is what I did Tuesday that may or may not have precipitated the issue.
I attempted to insert a picture into both the HEADER and BANNER sections of the TEMPLATE page. (I was unsure which controlled exactly what)
I failed of course (My Computer-Fu is weak) and carelessly lost the page with the original template for BANNER....this is why I asked if you has cheeseburger had stock templates or a reset to default function. As I generally use Firefox, I was unaware of the image issue at the time. I noticed it on AOL last night, and Wonderduck informed me mere minutes later that it was not a buggy Cybercafe computer, but an actual issue.
Both IE, and AOL refuse to show images. Additionally I've noticed today that when I follow an intra-blog link like the ENTRY hyperlink in the "Recent Comments" section I get a "Cant Find Web Page" error.....but #500 rather than #404.
Ultimately I'd like to put an image into the header or sidebar, be able to play with the site colors, have categories listed on the respective posts and possibly have category icons similar in principal to those on Shamus's site.
Note that despite the issues (which may or may not be self inflicted) I'm still quite happy with the move, for one thing customer service actually exists here, there has been no condescension, and the crack staff of support Pixies has been very quick at addressing all issues.
This is highly appreciated, especially since I am woefully ignorant web design.
Thank you for your professionalism and your patience.
OK, here is what I did Tuesday that may or may not have precipitated the issue.
I attempted to insert a picture into both the HEADER and BANNER sections of the TEMPLATE page. (I was unsure which controlled exactly what)
I failed of course (My Computer-Fu is weak) and carelessly lost the page with the original template for BANNER....this is why I asked if you has cheeseburger had stock templates or a reset to default function. As I generally use Firefox, I was unaware of the image issue at the time. I noticed it on AOL last night, and Wonderduck informed me mere minutes later that it was not a buggy Cybercafe computer, but an actual issue.
Both IE, and AOL refuse to show images. Additionally I've noticed today that when I follow an intra-blog link like the ENTRY hyperlink in the "Recent Comments" section I get a "Cant Find Web Page" error.....but #500 rather than #404.
Ultimately I'd like to put an image into the header or sidebar, be able to play with the site colors, have categories listed on the respective posts and possibly have category icons similar in principal to those on Shamus's site.
Note that despite the issues (which may or may not be self inflicted) I'm still quite happy with the move, for one thing customer service actually exists here, there has been no condescension, and the crack staff of support Pixies has been very quick at addressing all issues.
This is highly appreciated, especially since I am woefully ignorant web design.
Thank you for your professionalism and your patience.
Posted by: Brickmuppet at Sat Jul 7 22:56:20 2007 (V5zw/)
6
"You and I have been doing exactly what Pixy hoped we'd do: to use the
system heavily and to turn up problems he himself can't find."
Yay us! Woot!
Thanks Stephen
I was worried that my lack of knowledge would make me of limited usefullness as a a beta tester (Ye Gods I can barely type).... But that makes perfect sense actually.. I'm just sorry I didn't post a full explanation sooner (I was unaware of the issue as I've been hella busy).
Yay us! Woot!
Thanks Stephen
I was worried that my lack of knowledge would make me of limited usefullness as a a beta tester (Ye Gods I can barely type).... But that makes perfect sense actually.. I'm just sorry I didn't post a full explanation sooner (I was unaware of the issue as I've been hella busy).
Posted by: Brickmuppet at Sat Jul 7 23:02:22 2007 (V5zw/)
7
Steven's exactly right. The point of having beta testers is that they'll do things that I wouldn't expect. Which you have done.
I'll have it all sorted out soon - just a busy Sunday here, with annoying life-type-stuff interfering with my important coding. (You know, having lunch, talking to my family, that sort of thing.
)
I'll have it all sorted out soon - just a busy Sunday here, with annoying life-type-stuff interfering with my important coding. (You know, having lunch, talking to my family, that sort of thing.
)Posted by: Pixy Misa at Sun Jul 8 01:35:27 2007 (PiXy!)
28kb generated in CPU 0.0424, elapsed 0.2637 seconds.
68 queries taking 0.2464 seconds, 260 records returned.
Powered by Minx 1.1.6c-pink.
68 queries taking 0.2464 seconds, 260 records returned.
Powered by Minx 1.1.6c-pink.
