2008/11/26
2008/07/23
The Case of the Multi-Faceted Full-Blown Google solution... or so I hoped!
Let's call it my M2FBG project...
If you took the time to read the "main function" on the right, then you'll know what to expect browsing throught the archives; then again, not being your typical one man tech army guy - and not doing everything as it's supposed to be done! - I like to put a special flavour to everything I do...
So this being a Blogger blog, my intentions were and still are to build this virtual space out of everything Google! The idea first originate when, using the Google Documents, I saw it was possible to publish from GDocs to Blogger... little I knew about I was getting into...
The fact is that it's been more than 6 months now! At first, GSupport seems available to troubleshoot and fix the problem, but then it won't reply to my follow-up... how typical! Don't get me wrong : I'm pretty sure people at GSupport have plenty to be busy, but does that excuse them for poor assistance to users ? I do hope they don't take for granted offering free services makes up for bad support... from my point of view, the feedback vibes feel even nastier!
Wow : I don't even tell what this is all about do I ? :o|
So here we go, fast-forward style : GDocs has a function to publish a text to a blog of your choice (you can choose from Blogger, Wordpress, Livejournal and others); that way you can work with others on a document and have it automatically published everytime a modification has occured. In the vast infinity of the web, I've always liked the approach of Google solutions, so I thought the idea of publishing a GDoc to one of my GBlog (or Blogger if you prefer, and yes, I have many!) was cool; so the GDoc was rapidly created, the publish options set and tested, then applied...
WTH ? Refresh = NULL!
Little troubleshooting, to find out that the GDoc hasn't been published to my desired blog, but to one I used before to troubleshoot another issue (which I'll probably summarize in another post soon enough!)... then the fun started!
My first report of the bug was more than 7 months ago! At First, GSupport was giving me an impression of interest in the issue, as I replied rapidly after trying out several tips they gave out, they replied again stating the feedback I gave would likely help them solve the issue... over the next three months, I gave other infos, after renaming the blog, trying the GBlog english interface instead of the french one - yeah btw, I'm french and that probably explain the funny turn my writhing takes from time to time! ;o) - but GSupport never wrote back, and as I wrote this, the problem is still there!
Being in the field this is something I really resent, not being able to know where things stand : a good practice would be a freely accessible webpage showing how bug/case file are being handle! But like I said, the big G is, well, so BIG it probably is overwhelmed with the infinity (!) of projects it is trying to deliver/debug/support/develop...
Anyhow, I'm still faithful that my M2FBG solution (!) will eventually be functional, but for now it will rest in peace...
If you took the time to read the "main function" on the right, then you'll know what to expect browsing throught the archives; then again, not being your typical one man tech army guy - and not doing everything as it's supposed to be done! - I like to put a special flavour to everything I do...
So this being a Blogger blog, my intentions were and still are to build this virtual space out of everything Google! The idea first originate when, using the Google Documents, I saw it was possible to publish from GDocs to Blogger... little I knew about I was getting into...
The fact is that it's been more than 6 months now! At first, GSupport seems available to troubleshoot and fix the problem, but then it won't reply to my follow-up... how typical! Don't get me wrong : I'm pretty sure people at GSupport have plenty to be busy, but does that excuse them for poor assistance to users ? I do hope they don't take for granted offering free services makes up for bad support... from my point of view, the feedback vibes feel even nastier!
Wow : I don't even tell what this is all about do I ? :o|
So here we go, fast-forward style : GDocs has a function to publish a text to a blog of your choice (you can choose from Blogger, Wordpress, Livejournal and others); that way you can work with others on a document and have it automatically published everytime a modification has occured. In the vast infinity of the web, I've always liked the approach of Google solutions, so I thought the idea of publishing a GDoc to one of my GBlog (or Blogger if you prefer, and yes, I have many!) was cool; so the GDoc was rapidly created, the publish options set and tested, then applied...
WTH ? Refresh = NULL!
Little troubleshooting, to find out that the GDoc hasn't been published to my desired blog, but to one I used before to troubleshoot another issue (which I'll probably summarize in another post soon enough!)... then the fun started!
My first report of the bug was more than 7 months ago! At First, GSupport was giving me an impression of interest in the issue, as I replied rapidly after trying out several tips they gave out, they replied again stating the feedback I gave would likely help them solve the issue... over the next three months, I gave other infos, after renaming the blog, trying the GBlog english interface instead of the french one - yeah btw, I'm french and that probably explain the funny turn my writhing takes from time to time! ;o) - but GSupport never wrote back, and as I wrote this, the problem is still there!
Being in the field this is something I really resent, not being able to know where things stand : a good practice would be a freely accessible webpage showing how bug/case file are being handle! But like I said, the big G is, well, so BIG it probably is overwhelmed with the infinity (!) of projects it is trying to deliver/debug/support/develop...
Anyhow, I'm still faithful that my M2FBG solution (!) will eventually be functional, but for now it will rest in peace...
S'abonner à :
Messages (Atom)
