I like to be an early adopter of new technologies, so when Google Chrome came out, naturally I downloaded it. There are many features I liked, including the quickness of loading and the ability to turn my Gmail into an application. However, there are still some problems that need to be ironed out, and until they do, I will not be using this browser for anything at all, save development (yeah, thanks for another browser to check. Ugh).
First of all, Google Chrome isn’t actually a new rendering browser; it’s essentially Apple Safari re-branded. So if your pages work in Safari, typically they’ll work in Chrome. But I don’t use Safari, and now I know that if ever given the chance I wouldn’t. The way it handles things is so dumb compared to IE7. For instance, if I want to add a link in Gmail using IE7, I highlight the text I want to link, click the link button, enter my link, and hit enter, and the highlighted text is now a link. In Chrome, I follow the same steps, except when I’m done, there’s an additional space after the word. At this point, you’re thinking, you nitpicky a-hole, but the problem with this is, let’s say I want to put a comma next to the linked text. If I try to do that (which I do whenever I process an order), Chrome assumes the comma is part of the link, and then any text following the comma that I type becomes the link. Now if I only linked to things in emails every once in a while, I could live with it, but this is something I do 20-30 times a day. It gets annoying.
There are a plethora of other weird (and admittedly nitpicky) differences. For instance, when holding Ctl and pressing an arrow key to highlight a word, it selects the word and the preceding space. Or when copying and pasting something with formatting, some of the formatting is stripped, some is kept, with no rhyme or reason as to what. Also try pasting anything copied from Excel. Gross.
While yes, these annoyances are small, remember that if I’m going to start using a new browser over one that I’m already comfortable with, it has to provide me with features the incumbent does not without pushing me out of my comfort zone. Even still, due to sheer geekdom and willingness to be on the “cutting edge”, I endured these minor hardships.
Until I started receiving reply emails from people wondering who the hell I was.
I have several email addresses that forward to my main (hub) Gmail account, and I have them set up as “Accounts” within Gmail so that I may send as that email address. I use this feature very frequently, as I like to keep certain emails separate during certain parts of the order lifecycle (ordering, processing, shipping, support, etc). However, I also run several other websites on which I have email accounts that I run into my Gmail account. In IE7, I choose which address I want to send out as and it works, no problem. In Chrome, I pick the one I want to send as, and it picks whichever one it wants, often resulting in a very incorrect FROM address. Unfortunately, this is a dealbreaker.
So until Google Chrome undergoes some signficant changes (the last one being the most important), I will not be using this browser outside of the development arena (again, thanks for giving me another browser to check, Google).
Has anyone else experienced any other bugs in Chrome? Maybe in certain apps/sites?
Let me start off by saying that BlogEngine.NET is a fantastic piece of software with a ton of awesome features and is relatively easy to use.
That said, I’ve spent nearly all of my free time in the past month building a custom site using the BE.NET framework as a base, and while it’s been frustrating at times (I basically had to teach myself C#), I learned a lot about programming just by getting into the core and messing around and seeing how things are linked up and organized. It’s been working great on my local machine (first hooked up to my local MySQL database and then hooked up to the hosted MySQL database) and I was really excited to upload it and get it going.
I fired up good ol’ FileZilla, took a deep breath, and hit “Upload” and watched with mounting anticipation as the 700-some files in the queue slowly (actually, really quickly, but it seemed slow) dwindled. Finally, it was time! I opened my browser, typed in my URL, and held my breath as IE7’s thinking circle went round and round.
That’s when disaster struck.
The YPOD popped up with an unfamiliar error message: “Unable to find the requested .Net Framework Data Provider. It may not be installed.” Exqueeze me? What does that even mean?? My first instinct was that there was something wrong with my Web.Config file, so I checked there. Some idiot (read: me) forgot to change over the local DB string to the hosted DB string. Fixed. Uploaded. Ta-da!….. ? What? Still not working? Oy… this is going to be a long night…
Well, I did some digging and found out that my instincts were correct and that there is probably an issue with my Web.Config. I found a CodePlex thread by someone who got the same error and tried their solution, but to no avail. I also created my own thread, but as of this writing, no one has responded to my cry for help. I found this tutorial by Al Nyveldt and my spirits were raised again because he is one of the authors of the damn software, but again they were dashed when his tips were also unable to help me out. I even downloaded his sample Web.Config and applied it to my own.
I downloaded the latest MySQL/ASP.NET connector (220.127.116.11 as of now), placed it in my /bin folder and modified the versions in the Web.Config to match (they are 18.104.22.168 in the Web.Config). Still nothing.
With frustration and utter lack of any idea where to turn, I emailed both Mads Kristensen and Nyveldt beseeching them for advice on what to do. I don’t expect an answer (as I’m sure they get 290352268 emails a day from guys like me who are too dumb to figure out their software), but hopefully they will help me out.
Unfortunately, there is no happy ending to this story as of yet… no magical fix that I can present to you that will get you out of the same rut. But maybe I’ve pointed you in the right direction where someone’s suggestions may help you. If you have any ideas, please please please post them or email me. If it works, I will definitely post your solution with a link to whatever site you want. I would not be surprised if it’s a one-line fix in my Web.Config that makes me smack my forehead. With a hammer.
Thanks in advance for any help you can provide!
EDIT: I’ve received a bit of help from the wonderful nberardi and we (he) came to the conclusion that my host is running a pre-5.1 MySql/ASP.NET connector (they are running an outdated MySql.Data assembly) [22.214.171.124, to be exact]). The 5.1 release included support for Roles and Memberships, so anything older than that will not work with this engine. Should they update it (or I go elsewhere) I will keep you posted.
8/30: SOLVED! But you’ll never guess what the problem was. You ready for this? My hosting company had a stray character in their Machine.config file that was right by the DbProviderFactories node… no, I’m not kidding. Everything is working fine now… I will post more on this tool later.
Ever since version 10301 of the AJAX Toolkit, the Accordion control has been acting a little wonky for me, but only in certain circumstances. The recent release of the AJAX Toolkit still has not addressed this issue. I’ve posted about it in the ASP.NET forums hoping that someone will get back to me or that they will at least address the issue. I’m not the only one having problems, but apparently I’m the only one having this particular problem: basically, my Accordion control’s headers’ text is set at
text-indent: -5000px to make the text not appear on the page so I can replace it with a background image. Pretty standard procedure. But when using the versions of the ASP.NET AJAX Toolkit later than 10301, when the user clicks on a header to get the content in the AccordionPane, all the background images for the headers disappear and the text returns. It’s a really weird bug that I don’t think they’ve quite figured out how to fix, but I am confident that they will. Check the link above for my full code.
When they figure out what’s wrong and fix it, you’ll see it here.
EDIT 10/15/07: I’ve been informed of a work-around for those who like workarounds. Click the link above to my post to the ASP.NET forums and read the thread. It’s definitely a workaround and a bit kludgy, but it will work.
A few days ago, Microsoft released the newest version of the AJAX Toolkit (10920)! Go check it out, download, and install in your Visual Studios. A lot of old bugs were fixed in the “Calendar, PopupBehavior, AutoComplete, Accordion, ConfirmButton, ModalPopup, MaskedEdit and Slider”, so this release should prove to be the best one yet (as most new releases are).
While working on my newest creation, PROUDWear Sports, I’ve run into a little snag trying to implement the ModalPopupExtender. Of course it works fine in IE7 and FireFox, but in IE6, it just refuses to work correctly. I’m pretty sure that I’ve implemented it correctly, but one can never be too sure. I watched the How Do I: Use the ASP.NET AJAX ModalPopup Extender Control video provided by Microsoft and followed it pretty much exactly, except including my own functionality (which is essentially nothing! Basically showing a picture in the hidden panel with a close button, that’s it.) and still it refuses to work in IE6.
I posted in the ASP.NET forums about my issue a few minutes ago, detailing my total problem (6th post down, you can find it by searching for “.NET Discussion”). If you don’t want to go there, basically what happens is in IE6, instead of properly displaying the chosen modal panel, it displays the panel inline with the rest of the page and then goes modal, rendering the page inaccessible to the user.
If anyone has any suggestions, please please let me know. Thanks!
Status: Solved! (8/17/07)
Solution: Upgrade your AJAX Toolkit DLL. This version is not the newest version, but the ModalPopupExtender functions correctly in IE6 when this one is applied. I am not using the latest version because the accordion control does not function correctly in the newer versions. When they fix that, I will go to the newest version.