We would like to fix as many inconsistencies and problems as we can before we unleash the new editor on all Blogger users, so we’d really appreciate reproducible bug reports when you see a problem.
The three key pieces of a helpful bug report are:
- “I typed/clicked/did…”
- “I expected to see…”
- “What I really saw was…”
My post template is:Comments on this post are a fine place for these bug reports, or, if you post them on a blog, just link to them from the comments.
<span id="fullpost">
Full post
</span>
I opened up a new post in Firefox on XP and typed two paragraphs in Compose mode. When I switched back to Edit HTML, I expected to see:
<span id="fullpost">First paragraph
Second paragraph</span>
But what I saw was:
<span id="fullpost">
First paragraph</span>
<span id="fullpost">
Second paragraph</span>
We realize that writing about HTML can be tricky in the post editor or the comments form. You can replace “<” with “<” or put a space right after the “<” to prevent the editor from treating it as HTML. Or, if you make the post with the new editor, you can turn on “Show HTML literally” in the Compose Settings section of the Post Options.
While we can’t commit to making the new editor work exactly like the old in every regard (if we did, that might break some of the new useful features, such as drag-and-drop image placement), we really want to keep the differences down to as few as possible. Your feedback and bug reports will make this possible.
Thanks in advance!
Posts
93 comments:
Hey ! I haven't faced such problems but have a major problem which is Too serious for me !
I can't find the buttons like : Bold , Add Images etc . I am suing FireFox3 at XP and have tried many things to get rid of this like switching back to FF2 , using Opera - IE , Checking status of Java and JavaScripts etc .
Please , help me on this . I have stored the screenshot here : http://arpit123.googlepages.com/problem.jpg !
Okay Guys ;)
I have no post template, 'couse i wirte my posts from ground up. But i'm using often "hackosphere's Selective Expandable posts"-Hack.
So i have often this post structure
A Picture
First paragraph
< span id="fullpost">
Second paragraph
A Quote
Rest of Post
< /span>
in the old editor ... no problem. The Post was published as i written it.
But in the new editor i get this, when i publish ist - and i don't know why.
A Picture
First paragraph
< span id="fullpost">
Second paragraph
< /span> <--- the problem.
A Quote
Rest of Post
Please Guys, fix that problem - it makes me insane. I'm using 'indraft' since it started and tested all stuff. But if this is not get fixed, i will return to the normal blogger.
... one more thing. Yes, please return the Formating buttons in the html-View like in the old editor.
I start with
<p class="more">more text</p>
from the post template in Edit HTML mode. I click "Compose" and "Edit HTML" (no text entry) and get:
<div class="more">more text</div>
I understand you want to have block-level elements to be able to move images around, but P is as block-level as DIV :)
I want to add a blog roll to my blog..everytime I get to the page that says add a page element, I am unable to click on it. I went under layout like the video told me to, but that is as far as I can get. Thank you for your help.
dnmissujen@aol.com cfandbc.blogspot.com
(Sorry, third try's the charm)
In HTML mode I typed "#include <iostream>" when talking about some code, then I switched to compose mode and noticed that my file said "#include"... back in HTML mode my text had been changed to: "#include <iostream><iostream>". > and similar HTML directives should not be changed to literals as this confuses not only the blogger, but the post editor.
HELP!!! There's this philippine lotto who has a bunch of other users with simalar names. He's spamming me!!! The most common post is" I'm sorry if I commented on your blog, but you have a nice idea". And he has a few users, so how do I block him?
I second Anonymous' request:
"... one more thing. Yes, please return the Formating buttons in the html-View like in the old editor."
Cheers,
Mungo
Interestingly, I can only use the "Edit HTML" mode for editing my post. What happens to the "Compose" editor? It is gray out.
My biggest problem, which just started since you guys upgrades the draft post box: Any time I go in there to schedule a post it automatically removes all my paragraphs, all my blank lines, etc. and makes everything just a stream of the text. If I go back to regular blogger to fix it...the screw up is there and no matter what I do manually, the text auto reformats to the straight text version without any paragraphs or line breaks. It's never done this before. But I won't use Draft until it's fixed. I sometimes spend 2 hours on a post...and when the post screws up like that I have to rewrite it, which is going to take me a while. It's very irritating.
As this example has spoken about it self, why don't you give as an ability to split post with some <!--more--> or something so we don't have to worry about having problem with the new editor?
If Comment Form Under Post is so important, I guess Have a Read More Feature is even more important for bloggers. It can help Google avoid Duplicate Content on indexing our pages, and make the page load faster. that would help our readers who doesn't have fast internet connection a lot (need more advantages list?).
Just my two cent anyway. Thanks Pete + Blogger Team, I love your work.
I second the problems about the <span id="fullpost"> when using a post template.
I've chosen the "interpret typed HTML" option and now add these span tags manually in the post.
A word of advice to others using this: add your <span id="fullpost"> and </span> tags after you have written your content and are ready to publish. If you preview or switch to Edit HTML mode after adding the tags, extra span tags will be added which messes up the post!
I've also noticed that if we add <p> tags in compose mode, these are converted to <br/> instead, even when the "ignore newlines" option is checked. It seems the only way to use paragraphs in this way is to add manually in edit HTML mode, which can be a little awkward for those who style paragraphs.
Is there any chance of preventing <p> from becoming <br/> please?
Jacky's suggestion about using <-- more --> would be warmly welcomed. After these massive and great changes, I wouldn't expect this anytime soon, but if you could add it to your list of things to do in the future, you'll make us all very happy indeed :)
Thank you Pete and the Blogger team!
First thing that makes Blogger users move to wordpress.com is comment form under post. Second thing is the ability to split post to two parts with Read More function. In wordpress, users silmpy type <!--more--7gt; to do that.
A creative Blogger users had coded a hack to help Blogger users split their blog post using Selective Expandable Post or Peekaboo Post hack. Now, do you want to make that hack does not run?
Come on, Pete...
I added an image and expected it to be bordered as all images were previously, but it was not. You can see the difference between the pictures in these to blog posts:
With the old editor and with the new editor.
I'm having the exact same problem as S.M.D., for the same reasons. I worked around it by putting a fake header between paragraphs ([h][/h]) but I don't like that workaround. Neither [p] nor [div] works.
(Yes, I'm using the correct brackets in the actual post).
Thanks for the responses so far. Let me see what I can answer:
Anonymous: Great detail. This is very helpful. I think that the <span> solution just won't work in the new editor, given that block-level elements will split it up. Nevertheless, a <div>-based solution should work. It doesn't now, but that's a bug that we will definitely look into.
Leif902: Very odd. Did you change the Compose settings at some point? I'm only able to reproduce if I switch from "Interpret HTML literally" to "Interpret typed HTML" while in Compose mode. Also, if you can repro consistently please let me know what browser and OS you're using.
Mungo (and Anonymous): Edit HTML toolbar will definitely be back. Maybe not the next release, but it's high on the list of features from the old editor that need to be ported to the new editor.
Dannie: Sounds like the new editor is unsupported in your browser, or there was some other error during load. What browser / OS are you using?
S.M.D. and Laura: Yeah, we have a known issue with linebreaks when starting a post in the new editor and then editing it in the old editor. We've got a fix in the works.
Jacky Supit: Great feature request! That's something I've wanted as well.
Amanda: Can you post more specific steps about where you'd want to type <p> tags and where they'd appear? It's true that right now we mostly eliminate them for compatibility with browsers' rich text editing, but if I know what you want we might be able to come up with a workable solution.
blogportant.com: Point taken. I certainly don't want to break anything. :) Hopefully by having a dialog like this ahead of time, we can get the new post editor solid and reliable and only break the things we absolutely need to. With luck, that will be nothing.
Duncan Drennan: Thanks! The new editor is overriding the border styles on images. We're working to get this fixed for newly uploaded images.
oh and somehow, after insert an image and added it onto the new post editor, I can't select that image.
I meant, I can't click that image. I want to remove the link from it, but it's "untouchable" :)
And can I add the image only? without link and wrapper div on it?
thanks
*just ignore this comment in case only me who face this problem.
For Pete: Thank you for the responses!
I generally type my posts like this:
<p>This is a paragraph</p><p>Here is another paragraph</p>
<span id="fullpost>
<p>More content here</p>
</span</p>
If I switch modes or preview after typing the <p> tags, they are replaced by <br/><br/> instead.
But I must say I'm slowly getting used to using the line breaks instead :) Please don't worry about debugging this unless there are many others who are struggling with this!
However, I do second Jacky's comment about the images. I'm unable to change the alignment or drag the images, and have to edit this in edit HTML mode instead.
I've tried with both Firefox and IE6 so far if this is any help to you.
Thank you!
Whoops! Strike the last part of my comment about the images, I've managed to make this work.
It would be helpful if the cursor could change or something to indicate when the image is selected and draggable :)
Safari has inserted a mess of divs and spans in the Post Editor for a long time - wish I knew why they chose that - but now with 10.5.4 and your gorgeous new post editor, even when I write the HTML Blogger recognizes, and line breaks appear correctly when I switch to Compose or Preview ... they're gone if I switch back, replaced by divs.Tried posting from HTML, no Preview ...still gone, in the published post ... and why not, all Blogger sees are those damn divs.
Maddening, and of course I can use another browser ... A fix would be nice, but probably nothing you can do? ... just reporting.
Well first off why did we loose buttons on the HTML editor? I've always used the HTML editor but its still nice to have a button to insert the italics code for me, or to insert an image. I used those buttons for simple HTML and wrote my own more complicated stuff by hand. Please put the buttons back!
The editor also no longer allows a "save." In the past I hit Ctrl+S as I went to save the post, now Ctrl+S does nothing and hitting "Save as Draft" saves the post and closes the editing window. This is a pain and means I can't save as I go when working on long or complicated posts.
I do use a template like this: (< replaced with [)
The summary is here
[span id="fullpost"]
Full post Here
[/span]
And have noticed the ending [/span] field is quite often deleted if I flip to the WSYSWYG editor and back to HTML (this didn't happen before).
Que va a pasar con en icono de subir video de blogger en la barra del editor de entradas nuevo?
Viene algo nuevo en video blogger?
Concidero que una opciĆ³n importante seria agregar, al agregador de link, dar la posibilidad de que los enlaces habran en ventana emergente.
Saludos
Love it, but whenever I click on 'Save As Draft' it takes me back to the dashboard, rather than leaving me in the edit mode for that post. Previously, when I clicked on Save As Draft, it saved it and then allowed me to keep editing. Is this a change, or just a glitch? I liked it better the old way.
I guess the team must be working on the line breaks in the post editor now..?
I wondered what all the <div class="separator"> lines were all about in the HTML code dropped by here to see if there was any news in the comments.
At present, the preview is showing only single line breaks where I would prefer a double break (to separate paragraphs). I'll let you know how this looks once published :)
The <div class="separator"> added for the line breaks in my latest post didn't create the desired breaks between my paragraphs.
I had to edit in HTML mode and removed them all for the post to display as I wanted.
It was a good idea though! When designing Blogger templates, I've always had problems with div's used to clear floats (especially the differences between IE6 and FF), so this may be the cause of the problem for my blog.
Thanks for these updates :)
Hey,
I think the new post editor is lovely. If some of the bugs reported above were fixed, it'd work like a dream. I do have one prob in particular:
Blogger in Draft is my default dashboard. But whenever I edit my posts via the quick edit option on my blog, i get redirected to the Blogger version that's not Blogger in Draft. That sometimes screws up my HTML. And offers me less functionality all of a sudden.
Could you look into that, please?
And how can I add a link to an image?
Previously I only had to select the image and click the "link" button.
Now it doesn't work.
(Or am I missing something?)
Pete, I tried both browser - Firefox 3.0 and Microsoft Internet Explorer. My "compose" function is totally gray off. When I click on it, the message is "javascript: void(0).
Please help me urgently. I am having a hard time posting my blog entries. Thanks!
1. Opening and closing div-tags
* “I typed/clicked/did…”
I wrote a post, and added a >div style="text-align: justify;"< (with proper brackets of course) at the beginning of the post, in html mode.
I then added a >/div< at the end of the post (again, with proper brackets).
* “I expected to see…”
My post justified properly. I also expected to see a clean html code, with my opening div-tag at the beginning, and the closing div-tag at the end.
* “What I really saw was…”
After publishing I returned to the post. Now the first paragraph contained the opening div-tag, and had a closing div-tag at the end, of the paragraph that is.
Since this closed the justification, the rest of the post was now left-aligned.
2. Screwed up html
* “I typed/clicked/did…”
I wrote a post, and selected the text. I then, in Composer mode, clicked on the left-align button.
* “I expected to see…”
My post left-aligned properly. I also expected to see a clean html code, with an opening div-tag for left-aligning at the beginning, and the closing div-tag for the left-aligning at the end.
* “What I really saw was…”
I then switched to html mode, and found that the editor had set an opening and closing left-align div-tag on each paragraph and empty line, thereby making the html incredibly cluttered and difficult to read.
Maybe, just maybe, this is how things are supposed to work according to standards, but I vastly prefer the editor not to change the position of my tags without my consent. I put them where I want them to be, and the editor shouldn't try to second guess me. I also would like the editor not to format empty lines, adding unnecessary html for no appearant good reason. Shouldn't one opening tag and one closing tag for the entire post be enough?
Note that I am not up to speed on the latest developments within html coding. The behaviour displayed by the editor might be standard nowadays, but to me, this is flashback time to when I was wrestling with Frontpage, trying to get it the lay its grubby hands off my clean and easy to read html.
Cheers!
/Magnus
The post comment won't except html tags
I post you tube html into non wysiwyg mode and I get this
... object width="425" height="344"> ...
I switch to wysiwyg mode and back again and I got
... object height="344" width="425"> ...
I want the key functions like link and add image etc to be in none wysiwyg mode as well. Otherwise I have to keep switch between modes
This is a real step forward. Very nice. The only thing that I miss are tables. I can put them in by hand, but they look awful (no styles in the template).
Thanks also for the improvement to the quick poll results. it is now possible to cut and paste the results in to a spreadsheet. :-) It would be better still if the polls were an article, not a layout item, so that they would show up in RSS feeds, be linkable, etc.
i posted this comment earlier at another post. later, found that this is the right place for this comment. apologies for repeating.
i like many features in blogger draft. but the new post editor causes some headaches. the most disturbing is the reformating of the html codes.
usually, i upload images to the ftp server and then place it at blogger with html codes. but when i do it now, the new post editor automatically adds a link to it, which is the last thing i want to. please find an example below:
code i placed: < a> < img alt="anwar rasheed" src="http://indulekha.com/picture_library/anwarrasheed.jpg" /> < /a>“
new post editor changed it to: < a href="http://draft.blogger.com/"> < img alt="anwar rasheed" src="http://indulekha.com/picture_library/anwarrasheed.jpg" /> < / a >
( < is used instead of < )
this make the image clickable and misleads the readers. please do something to fix it.
When you create a link using Safari 3 with BinB you lose your position in the post. So after the link is created, the cursor is at post top.
Would like to see a blank and easily editable image descriptor (i.e. ALT="") included in the code string created by the new image management system. Thanks!
Brian
One thing that would be nice is changing the font size controls to insert <span style="font-size: blah;"> rather than using deprecated <font size="blah"> tags/attributes.
Just in case. The drop down comment section didn't work with me and formatting isn't working.I've gone back to the old format. Keep up the good work.
I work on a Mac (with Firefox 3 I might add) and I know things are seen differently on Macs than on PCs, but I completely agree with Magnus Seter's comments above.
In "compose" mode there is no "justification" button, so apparently my posts can only be right, center or left aligned (I really dislike any other alignment than justify). I tried out the left-align to see what it looked like..
* “I typed/clicked/did…”
I selected the whole text of the post and clicked on the left align button in compose mode.
* “I expected to see…”
Just one alignment code for the whole selected text in html mode, as I had been accustomed to see before.
* “What I really saw was…”
Every single paragraph had the align html code (with opening and closing tabs) in html mode, even though I had selected the whole text and not paragraph by paragraph. I had to manually change the tag from "left" to "justify" for every single paragraph. This could be very tedious when you write long posts.
Seeing a justify button in back in compose mode would be really nice.
*"I typed":
A fully functioning blog post, and then I went back to include two pictures.
*"I expected to see":
The paragraphs inbetween the pictures to be separate paragraphs.
*"What I reall saw was":
What you see now, a conglomeration of all the smaller paragraphs into one.
I've tried editing the post in both "show HTML" and "compose" format, and the HTML code is all fine. But when I hit publish, it all turns into one paragraph.
SUMMARY: sometimes the paragraphs between two uploaded images will concatenate into the one huge paragraph.
Any news on fixing the problem with the line breaks?
When I code them manually putting in the p-tag for every paragraph it messes up the spacing (it is almost line and a half) it I try using br-tag instead it just ignores it (whatever boxes I have ticked). If I try to fix it with the old version it takes out the breaks altogether!
It now takes me an hour to make a post because I have to manually type in the paragraph breaks and it doesn't even look good!!!
I have been doing a work around to enable me to caption photos with a float. I place the photo and the text in a div and float the div. When I tried to do this in the new editor, it deletes the new div that I added. Can you add photo captioning? It would make my life easier.
I noticed in the Blogger in Draft dashboard there is no Blogs of Note section. May you guys please put one?
The new post editor is grate. Easy to write and configurate. But, I had 2 problems; 1st, I can't justify de text. The option doesn't apear.
The 2nd, I like to link the images to a Web page, but I can't do it with the new post edito.
I hope this help.
Could you add comment count and post count thing on the dashboard. I want to know how many posts I wrote on my blog, and how many people commented on them...
I like a lot of what I see in the new editor though I, too, am concerned that the "Read More" hack many of us are using seems to be broken.
The most annoying problem for me is something different though. I either type my piece in the HTML editor or type it in an external word-processor and paste it straight into the HTML editor. So far, so good: all looks fine in the preview.
I then tend to insert an image partway through and this action inserts additional formatting code that affects any text below the image. In particular, it condenses the line-spacing so that it's normal above the image and uncomfortably squashed up below.
I'm not clever enough to see what exactly is causing the problem but is there something specifically I could be doing to rectify this?
Line-breaks don't work in the editor.
When I hit enter, it does not show
Any information on improving compatbility with Opera 9.5?
The editor changes any & character in a URL to a & which makes the URL invalid - this occurs while switching from WYSIWYG to HTML editor.
Is there a way to stop this automatic changes? or it not, fix it so that & characters in strings are not modified.
tia.
yes, like anonymous and mungo, i need the old editor's html post buttons back, like those allowing me to change the color of text, the size and type of font, and other buttons that were at the top of the post editor.
pete, what date can we expect these buttons to be back?
Hi Guys, theres a small Problem with the new editor. If i use Pictures over the import by URL there are no borders around the picutres like it was in the past.
please return the Formating buttons in the html-View like in the old editor!!!
they were much better!
I sent an MMS from my cellphone to my Mail-to-Blogger email address. I expected so see what I worked out in my MMS messages, text and low-res photos, it worked fine before. What I really saw was blocks of code. I tried copy/pasting the code here but that's not allowed. They're in some recent posts on my lone blog.
My cell service provider is Globe, I can send picture messages just fine to other cellphones, just doesn't work with Blogger anymore. Globe isn't listed as one of the supported carriers in go.mobile, but that didn't matter before, and I was ok with the cost per MMS.
When you turn on spell check, I hope you will configure it to check spelling in the headline for the post as well as the body. The current spell check ignores errors in the headline.
“I typed/clicked/did…”
Nothing. Just started using Daft Dashboard.
“I expected to see…”
My blog as it has allways been.
“What I really saw was…”
All my posts are now mono-blocked. Aparently I have never used the Enter key. I don't want to edit all of them again (hundreds of posts) looking for where did I change paragraph. Not talking about how mad my Feeds would look like.
It screwed up all my blog. It wasn't funny.
PS: I highly recomend not using Blogger Draft.
I have created a Greasmonkey script that will increase the size of the editing text area to take up all the available screen size.
It would be great if you could integrate this into Blogger as I think everyone wants more editing space.
Hi, it's me again :P Just wanted to post an example of what happened to me. This meme should look like an "answer-question" model. Now it looks like this.
Just in case it helps you to figure out the problem.
1. In Firefox 3 on XP using the new editor, I press Enter on the keyboard and see a line break/return appear. I publish and the line blank is there as desired. I return to the new editor and add empty lines in other areas by pressing return. I publish and the previous lines are gone (no empty space). I repeat until exhausted and frustrated.
2. I view a post that looked fine earlier in the day, haven't edited it or even opened it in any editor. Lines are all smooshed together: line breaks/returns are gone. I do #1 until nutty and give up.
3. I edit HTML to include
's where I want blank lines. I get double blank lines. I delete one line and publish. It looks fine until #1 or #2 screw it up again.
4. Fat Knowledge is right: the postage stamp area for editing is unworkable at times, such as when dragging large images around other large images.
On edit html page, I insert <p> tag like this. When I switch to write page and back to edit html page again. The <p> was GONE!!
Please bring back my <p>s tag.
The new editor seems to have problems with URLs which contain an & character. When adding such a URL in the compose mode and changing into HTML mode it gets changed into the HTML code for the ampersand character, which of course breaks the URL. This apparently happens every time I change between the two editing modes.
I can confirm an odd behavior - url encoding of special characters displays in the compose view after toggle between compose and html.
Try this.
Type an "arrow" composed of a hyphen and right angle bracket in compose view:
->
Now switch to html view and back to compose a few times. Sooner or later you will see in html view a URL encoded right angle bracket.
That's fine, but in compose view you ALSO see the url encoding.
If you view in browser, or publish, you will, however, see the right angle bracket.
The compose view, after a few roundtrips to edit view, is showing URL encoded characters instead of the usual browser representation of those characters. However the underlying data is correct.
Tested on XP and OS X with Firefox 2 and 3.
Here's a link to a problem where newlines are not properly converted to <br /&rt; : http://dkozinn1.blogspot.com/
Incidentally, for some reason, I'm not able to put a title on that post; I've never seen that before. The blog posting gives a narrative of what I did, the shows the resulting HTML. What I'd expected between the paragraphs was the "br /" but got empty <div>s.
The new editor ate most of my auto-install-widget-on-your-blogger-blog code.
Using the new editor to edit posts created in the old editor. I uploaded a new image to a post using the new editor and when I tried to save I received error:
Your HTML cannot be accepted: Tag is not closed: (I can't post the rest here, it won't accept it)
Embedded media (from boopm3) error says has a tag is open but this error does not show up in the old editor either when I created the post or when I use the old editor to edit the posting. There is no tag to close that I can see, boomo3 is pretty simple, just c/p the code they give you.
A bigger preview window would be great - you currently need to scroll left and right as well as up and down if you have wide posts. Also, a bit more height would be good.
The new post editor keeps changing my ampersands to "&", and I have to keep changing them back.
Barf! THIS comment post editor did the exact opposite--it changed the character entity back to an ampersand!
The new post editor changes the plain ampersand to ampersand, a, m, p, semicolon.
I was trying to edit things in html and the button to switch between Plain Text and HTML was not there HELP
HELP. I cannot switch between the 'compose' tag and 'Edit HTML' tag. The Tags just are not there HELP
Iam having trouble embedding an mp3 player in Blogger in Draft.
In the standard dashboard I can include the following html and the mp3 payer will embed as I expect.
< embed type="application/x-shockwave-flash" src="http://www.google.com/reader/ui/3247397568-audio-player.swf?audioUrl=http://countingtb.googlepages.com/radhashar-thelibrarysong64k.MP3" allowscriptaccess="never" quality="best" bgcolor="#ffffff" wmode="window" flashvars="playerMode=embedded" width="400" height="27">< /embed>
If I use the same code in Blogger in Draft I get an error message saying the tag is not closed.
http://websearchengineoptimizationtips.mscsector.com
http://websearchengineoptimizationtips.mscsector.com improve your web ranking on web seo tips
Initially I could use him and I succeeded in sending my article to posting. but afterwards all the menus are lost up until today on September 2 2008, already around one this Sunday I could not send my article.n fact I has update Java and mozilla and practised all the indications from blogger help,tapi results were not available. Please I, through the e-mail if4zn9@gmail.com
i'm using mozilla and recently i can't see and use new editor features like compose and preview. If not because im learning simple html languanges, i will confuse now. And I am, i can't manage size of picture in my posting cause
i'm not learning yet about it. How to fix this problem ?
rimless frames
flexible frames
titanium frames
metal frames
plastic framesreading eyeglasse
prescription eyeglasses
cheap eyeglasses
prescription glasses
eye glass
I expected to see buttons for html tags when using html editor. Not only buttons for styling text...
Buttons for "break line", "paragraph", etc. as you can find in a good html editor. Every time I must copy&paste an old article into Quanta Plus editor for html formatting. Also for new articles I'm using the same external editor. Because I care about having a good html code of my articles.
BTW, how about having a valid XHTML and CSS code for Blogger? Also very friendly SEO? I mean (you know what I mean) having meta descriptions for articles and labels from them can be used as meta keywords.
If I'm using Webmaster Tools on a Blogger blog, he is saying that everything is ok. But when I'm using it on a different domain, then, every little "bug" is displayed... And on my site http://www.morisca.net the html code is ok (from SEO perspective) and for http://pigeons-ro.blogspot.com the code is not. But you saying: "It's ok" :p I can't believe you. The truth is: is not ok, you are making an exception.
oho, here is spam! I wasted my time... this article is not viewed by owners...
Maybe I missed it but I don't see the spell check in this new editor. Not sure if it is an issue with it in this browser or if I'm missing it but there isn't a way to spell check like in the old one.
MB2-498 /
70-638 /
70-648 /
70-649 /
MB3-528 /
MB3-529 /
MB3-637 /
MB3-532 /
70-555 /
70-634 /
70-400 /
70-544(CSharp) /
70-544(VB) /
70-556 /
70-639 /
70-540(VB) /
70-540(CSharp) /
70-541(VB) /
70-541(CSharp) /
70-542(VB) /
70-542(CSharp) /
70-543(VB) /
70-543(CSharp) /
70-545(VB) /
70-545(CSharp) /
70-547(CSharp) /
70-547(VB) /
70-548(C++) /
70-548(CSharp) /
The post editor is still broken if a post containing an iframe is re-edited and compose/WYSIWYG edit mode is enabled. The worst part is it appears that the post was lost, i.e. the editor appears empty (after a brief flash of the actual post content). Unless the user tries preview or edit html, they wouldn't know it was broken. Even then it just seems odd not broken. ANY changes or additions to the post disappear, even though Blogger seems ok and even accepts the Publish Post without complaint. The unsuspecting novice user without a FF Error console will lose ANY edits!!
Now I haven't found anything about this issue in either the online help or the users group.
See bloggerblurbs.blogspot.com for full description of the problem and a workaround.
Does anyone know about this issue? Is there a formal bug tracking area outside the garbled mess of the users group?
ä»åŗ蓧ę¶|äøéAåč“§ę¶ ä»åØ蓧ę¶|äøéBåč“§ę¶ åŗęæ蓧ę¶|ęØŖę¢å¼č“§ę¶ å”ęęē|ę ęæ é¢ęē|é¢å¶ęē ęå å¼ä»åØē¬¼|ä»åŗē¬¼ ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ ęē|é¢ęē ęē|å”ęęē åØč½¬ē®±|å”ęåØč½¬ē®± ęē|ēŗøęē ęē®±|é¢å¶ęē®± å·„å ·ę|å·„å ·č½¦|ę½å±ę å·„ä½å°|å·„ä½ę” åå ·ę|åå ·č½¦|åå ·ę¶ ęåØę¶²åęēę¬čæč½¦|ēµåØęēę¬čæč½¦ ęåØę¶²åå é«č½¦|ęåØåč½¦ ä»åØē¬¼ ä»åŗē¬¼ åäŗ¬ä»åØē¬¼ åøøå·ä»åØē¬¼ ę é”ä»åØē¬¼ čå·ä»åØē¬¼ å¾å·ä»åØē¬¼ åéä»åØē¬¼ éę±ä»åØē¬¼ čæäŗęøÆä»åØē¬¼ ę³°å·ä»åØē¬¼ ę¬å·ä»åØē¬¼ ēåä»åØē¬¼ ę·®å®ä»åØē¬¼ å®æčæä»åØē¬¼ č½»éå蓧ę¶|č§é¢č“§ę¶ äøéAåč“§ę¶ äøéBåč“§ę¶ č“§ä½å¼č“§ę¶ ęØŖę¢å¼č“§ę¶ éę„¼å¼č“§ę¶|é¢å¹³å° ę¬čå¼č“§ę¶ č“Æéå¼č“§ę¶|éå»å¼č“§ę¶|é©¶å „å¼č“§ę¶ č¾č½®å¼č“§ę¶|ęµå©ę”č“§ę¶ åå „å¼č“§ę¶ ē§»åØå¼č“§ę¶|åÆéę¶ ęØ”å ·č“§ę¶ ę½å±å¼č“§ę¶ ę±½č½¦4Såŗč“§ę¶ ę±½é åŗč“§ę¶ čŖåØåē«ä½ä»åŗč“§ę¶ ęē|é¢ęē|é¢å¶ęē ęē|å”ęęē ęē|å”ęęē ęē|å”ęęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ ęęØč½¦|éęæęęØč½¦ ęęØč½¦|éé³ęęØč½¦ ē½®ē©ę¶|å·„äøē½®ē©ę¶|家ēØē½®ē©ę¶ å åę¶|å·§åŗę¶ ęęæę¶|ē©ęę“ēę¶ ē»é«č½¦ ē©ęµå°č½¦|č½½ē©å°č½¦ ęē®±|é¢å¶ęē®± ę¬čæč½¦|ęåØę¶²åęēę¬čæč½¦|ēµåØęēę¬čæč½¦ å é«ęŗ|å åęŗ|ęåØå é«ęŗ|ēµåØå é«ęŗ åč½¦|ēµåØåč½¦|å ēåč½¦|åč½¦å č“§ę¶ č“§ę¶ ä»åØč“§ę¶ ä»åØč“§ę¶ ä»åŗč“§ę¶ ä»åŗč“§ę¶ č“§ę¶å 蓧ę¶å 蓧ę¶å ¬åø 蓧ę¶å ¬åø ęē é¢ęē éęē é¢å¶ęē å”ęęē ä»åØē¬¼ ä»åŗē¬¼ ęå å¼ä»åØē¬¼ ęå ä»åØē¬¼ ä»åØ蓧ę¶|ä»åŗ蓧ę¶|åŗęæč“§ę¶ åäŗ¬č“§ę¶|ęØŖę¢å¼č“§ę¶|äøåč“§ę¶ é¢ęē|å”ęęē|ēŗøęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ é¢å¶ęē®±|å·„å ·ę|å·„ä½å° ęåØę¶²åęēę¬čæč½¦|ęåØę¶²åå é«č½¦ ä»åŗ蓧ę¶|äøéAå蓧ę¶> ä»åØ蓧ę¶|ęØŖę¢å¼č“§ę¶|蓧ä½å¼č“§ę¶ ęē|å”ęęē|é¢å¶ęē|ēŗøęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼|č“č¶ē¬¼|åØē©ē¬¼ ęåØę¶²åęēę¬čæč½¦|ęåØę¶²åå é«č½¦ ä»åŗ蓧ę¶|äøéAåč“§ę¶ ä»åØ蓧ę¶|ęØŖę¢å¼č“§ę¶|蓧ä½å¼č“§ę¶ ęē|å”ęęē|é¢å¶ęē|ēŗøęē ä»åØē¬¼|ęå å¼ä»åØē¬¼|ä»åŗē¬¼|č“č¶ē¬¼|åØē©ē¬¼ ęåØę¶²åęēę¬čæč½¦|ęåØę¶²åå é«č½¦ ä»åØ蓧ę¶|ä»åŗ蓧ę¶|åŗęæč“§ę¶ åäŗ¬č“§ę¶|äøå蓧ę¶|ęØŖę¢å¼č“§ę¶ é¢ęē|é¢å¶ęē|å”ęęē|ēŗøęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ é¢å¶ęē®±|å·„å ·ę|å·„ä½å° ęåØę¶²åęēę¬čæč½¦|ęåØę¶²åå é«č½¦ ä»åŗ蓧ę¶|äøéAåč“§ę¶ ä»åØ蓧ę¶|äøéBåč“§ę¶ åŗęæ蓧ę¶|ęØŖę¢å¼č“§ę¶|蓧ä½å¼č“§ę¶ é¢ęē|é¢å¶ęē|éęē|ę ęæ ęē|å”ęęē|ę ęæ ēŗøęē|ę ęæ ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼|č“č¶ē¬¼|åØē©ē¬¼ é¢å¶ęē®±|é¢å¶åØč½¬ē®±|ē½ę ¼å¼ęē®± ę¬čæč½¦|ęåØę¶²åęēę¬čæč½¦|ēµåØęēę¬čæč½¦ ä»åŗ蓧ę¶|äøéAåč“§ę¶ ä»åØ蓧ę¶|äøéBåč“§ę¶ åŗęæ蓧ę¶|ęØŖę¢å¼č“§ę¶|蓧ä½å¼č“§ę¶ é¢ęē|é¢å¶ęē|éęē|ę ęæ å”ęęē|å”ęę ęæ ēŗøęē|ę ęæ ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼|č“č¶ē¬¼|åØē©ē¬¼ é¢å¶ęē®±|é¢č“ØåØč½¬ē®±|ē½ę ¼å¼ęē®± ęåØę¶²åęēę¬čæč½¦|ę¶²åę¬čæč½¦ ä»åØ蓧ę¶|>ä»åŗ蓧ę¶|åŗęæč“§ę¶ åäŗ¬č“§ę¶|äøå蓧ę¶|ęØŖę¢å¼č“§ę¶ é¢ęē|é¢å¶ęē|å”ęęē|ēŗøęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ é¢å¶ęē®±|å·„å ·ę|å·„ä½å° ęåØę¶²åęēę¬čæč½¦|ęåØę¶²åå é«č½¦ ä»åŗ蓧ę¶|äøéAåč“§ę¶ ä»åØ蓧ę¶|äøéBåč“§ę¶ åŗęæ蓧ę¶|ęØŖę¢å¼č“§ę¶|蓧ä½å¼č“§ę¶ é¢ęē|é¢å¶ęē|éęē|ę ęæ å”ęęē|å”ęę ęæ ēŗøęē|ę ęæ ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼|č“č¶ē¬¼|åØē©ē¬¼ é¢å¶ęē®±|é¢č“ØåØč½¬ē®±|ē½ę ¼å¼ęē®± ęåØę¶²åęēę¬čæč½¦|ęēę¬čæč½¦ 蓧ę¶|ä»åØ蓧ę¶|ä»åŗ蓧ę¶|åŗęæč“§ę¶ åäŗ¬č“§ę¶|äø굷蓧ę¶|åäŗ¬č“§ę¶ č½»å蓧ę¶|äøå蓧ę¶|ęęæå¼č“§ę¶ éå蓧ę¶|ęØŖę¢å¼č“§ę¶|ęēå¼č“§ę¶ ęē|ęØęē|ēŗøęē|ęØå”ęē ęē|é¢ęē|å”ęęē|é¢å¶ęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ ęęØč½¦|éé³ęęØč½¦|éęæęęØč½¦ ē©ęę¶|ę“ēę¶|ęęæę¶ ęē®±|é¢å¶ęē®±|é¢å¶åØč½¬ē®±|ē½ę ¼å¼ęē®± ęåØę¶²åęēę¬čæč½¦|ēµåØęēę¬čæč½¦ ęåØę¶²åå é«č½¦|åēµåØå é«č½¦|ęåØåč½¦ å”ęåØč½¬ē®±|ē©ęµē®±|å”ęåå·„ę”¶|å”ęå”ęæē®± å·„å ·ę|äøęµ·å·„å ·ę|åäŗ¬å·„å ·ę|ę½å±ę å·„ä½å°|å·„ä½ę”|åäŗ¬å·„ä½å°|äøęµ·å·„ä½å° åå ·č½¦|åå ·ę|åå ·ę¶|åå ·åŗ§ č“§ę¶ č“§ę¶å 蓧ę¶å ¬åø ä»åØč“§ę¶ ä»åŗč“§ę¶ åŗęæč“§ę¶ åäŗ¬č“§ę¶ äøęµ·č“§ę¶ ęē é¢ęē é¢å¶ęē 蓧ę¶|č½»éå蓧ę¶|č§é¢č“§ę¶ 蓧ę¶|äøéå蓧ę¶|ꬔéåč“§ę¶ č“§ä½å¼č“§ę¶|ęØŖę¢å¼č“§ę¶|ééåč“§ę¶ ä»åØ蓧ę¶|éę„¼å¼č“§ę¶|é¢å¹³å° ä»åØ蓧ę¶|ę¬čå¼č“§ę¶ ä»åØ蓧ę¶|č“Æéå¼č“§ę¶|éå»å¼č“§ę¶|é©¶å „å¼č“§ę¶ ä»åŗ蓧ę¶|åŗęæ蓧ę¶|ę½å±å¼č“§ę¶|ęØ”å ·č“§ę¶ ä»åŗ蓧ę¶|åŗęæ蓧ę¶|ę±½č½¦4Såŗ蓧ę¶|ę±½é åŗč“§ę¶ č“§ę¶å|蓧ę¶å ¬åø|åäŗ¬č“§ę¶|äø굷蓧ę¶|ę é”蓧ę¶|čå·č“§ę¶ 蓧ę¶å|蓧ę¶å ¬åø|åäŗ¬č“§ę¶|å¤©ę“„č“§ę¶|ę²é³č“§ę¶|大čæč“§ę¶ č“§ę¶å|蓧ę¶å ¬åø|å¹æå·č“§ę¶|ę·±å³č“§ę¶|ęå·č“§ę¶ ęē|é¢ęē|é¢å¶ęē ęē|å”ęęē ä»åØē¬¼|ä»åŗē¬¼|ęå å¼ä»åØē¬¼ ē½®ē©ę¶|å¤åč½ē½®ē©ę¶|å«ęµ“ē½®ē©ę¶ ęē®±|é¢å¶ęē®±|é¢å¶åØč½¬ē®± ęåØę¶²åęēę¬čæč½¦|äøéé¢ęēę¬čæč½¦|ēµåØęēę¬čæč½¦ ęåØę¶²åå é«č½¦|åēµåØå é«č½¦|ēµåØå é«č½¦|å åč½¦ č“§ę¶ ä»åØč“§ę¶ ä»åŗč“§ę¶ č“§ę¶å 蓧ę¶å ¬åø ęē é¢ęē éęē é¢å¶ęē å”ęęē ä»åØē¬¼ ä»åŗē¬¼ ęå å¼ä»åØē¬¼ ęå ä»åØē¬¼ č“§ę¶ č“§ę¶ č“§ę¶ ä»åØč“§ę¶ ä»åØč“§ę¶ ä»åØč“§ę¶ ä»åŗč“§ę¶ ä»åŗč“§ę¶ č“§ę¶å 蓧ę¶å 蓧ę¶å ¬åø 蓧ę¶å ¬åø ęē é¢ęē éęē é¢å¶ęē å”ęęē ä»åØē¬¼ ä»åŗē¬¼ ęå å¼ä»åØē¬¼ č“§ę¶ č“§ę¶ č“§ę¶ ä»åØč“§ę¶ ä»åØč“§ę¶ ä»åØč“§ę¶ ä»åŗč“§ę¶ ä»åŗč“§ę¶ ä»åŗč“§ę¶ č“§ę¶å 蓧ę¶å 蓧ę¶å 蓧ę¶å ¬åø 蓧ę¶å ¬åø 蓧ę¶å ¬åø ęē é¢ęē éęē é¢å¶ęē å”ęęē ä»åØē¬¼ ä»åŗē¬¼ ęå å¼ä»åØē¬¼ ęå ä»åØē¬¼ ęē å”ęęē é¢ęē é¢å¶ęē éęē 蓧ę¶å ä»åØē¬¼ ä»åŗē¬¼ ęå å¼ä»åØē¬¼ ęå ä»åØē¬¼ åäŗ¬č“§ę¶ 蓧ę¶å ¬åø 蓧ę¶å ä»åŗč“§ę¶ ä»åØč“§ę¶ č“§ę¶ č“§ę¶
I have searched this topic long time ago. Finally I have an insight of my problems.
Thanks.
Btw, what were you saying peter w.?
Blogger in Draft Potential Bug
I compose most posts in Word or the Open Office Word proccessor, and do all my linking there. The copy / paste into blogger.
In the draft blogger, the links don't seem to make the past, and you have to relink.
This renders the new blogger composition page nigh on to worthless.
Suggestions?
hah,icone
"Compose Mode" no longer works on my computer.
I have tried so many hacks for the Read More feature -- It's not "I may be going mad" any more. I have gone stark raving. Barking mad, c'est moi.
A Read More feature should keep the formatting (Paragraphs and bold & italic; image too!!) on the front page of the blog. You should be able to insert Read More where you actually want it.
Best would be if there were an auto-Read More option for people in a hurry. And for those of us who really care about the look of our front page, an Insert Read More -- so it would only appear on long posts AND it would appear at the suspenseful place we would like it to.
This is the main missing feature on Blogger in terms of its looking like a proper, serious blog.
I am very grateful to Blogger for all its fab features -- including that it's FREE.
But an easy Read More feature would be the biggest improvement most of us non-geeks could think of. Thanks!
Thanks for your updating.i want to give some commands about this post that's all..I understand you want to have block-level elements. thanks for sharing..
Thank you a really nice blog site I am writing you follow your good works constantly...
Thanks ever so much, very useful article. I don;t have any problem with Blogger in Draft so far...
Signature: Kenali dan Kunjungi Objek Wisata di Pandeglang
You know, I have to tell you, I really enjoy this blog and the insight from everyone who participates. I find it to be refreshing and very informative. I wish there were more blogs like it. Anyway, I felt it was about time I posted, I've spent most of my time here just lurking and reading, but today for some reason I just felt compelled to say this.
SERP Kenali dan Kunjungi Objek Wisata di Pandeglang Kembali Berubah Pendatang Baru Kenali dan Kunjungi Objek Wisata di Pandeglang, Kembali Optimasi Kenali dan Kunjungi Objek Wisata di Pandeglang, Kenali dan Kunjungi Objek Wisata di Pandeglang Persaingan Semakin Sengit, Kenali dan Kunjungi Objek Wisata di Pandeglang, Optimasi Spam, Bolehkah?, Kenali dan Kunjungi Objek Wisata di Pandeglang SERP Baru, Kenali dan Kunjungi Objek Wisata di Pandeglang Turun Naik, Google “Ngedance” Pada Kenali dan Kunjungi Objek Wisata di Pandeglang, Kenali dan Kunjungi Objek Wisata di Pandeglang Masuk Halaman Pertama, Mencari Backlink dari .edu dan .gov, Masihkah Perlu?, Pandeglang, Banten – Eksotisme Pantai Tanjung Lesung, Pandeglang, Banten – Taman Nasional Ujung Kulon, Kenali dan Kunjungi Objek Wisata di Pandeglang, smart
thanks for this useful information..
now i find what i want to know..
thanks..
Kenali dan Kunjungi Objek Wisata di Pandeglang | Blog SEO | cah bagoes | oes tsetnoc | blogger
Post a Comment
Let us know what you think about what’s happening on Blogger in draft!
Don't see the feature everyone's talking about? Make sure you've logged in to draft.blogger.com. Learn more.
Having a problem with something else on Blogger? Get support at our help center.
Off-topic posts will be deleted