Basename, skill level and pasting HTML
-
I have just posted an article and 3 matters arose which I wanted to tell you about: 1) If you fill in the first page (Naming and setup), press the "Next, article uploads" button and then for whatever reason decide to stop and start again later, you find that the basename you used has been created, and when you try again you get a "basename already in use" error and have to think of a new name. 2) I couldn't find the "skill level" selector on page 1 anywhere, although it is mentioned in the notes 3) I submitted a large article by preparing it as HTML first, selecting the "bare HTML <>" button on the subission page and pasting the whole lot in. When I pressed <> again to return to WYSIWYG view I found I could edit anything. I had to keep returning to the HTML view to make changes - made even more difficult because the cursor positions of the two views appear to be independant. Apart from that - it's a great site and I use it very often.
Dave
-
I have just posted an article and 3 matters arose which I wanted to tell you about: 1) If you fill in the first page (Naming and setup), press the "Next, article uploads" button and then for whatever reason decide to stop and start again later, you find that the basename you used has been created, and when you try again you get a "basename already in use" error and have to think of a new name. 2) I couldn't find the "skill level" selector on page 1 anywhere, although it is mentioned in the notes 3) I submitted a large article by preparing it as HTML first, selecting the "bare HTML <>" button on the subission page and pasting the whole lot in. When I pressed <> again to return to WYSIWYG view I found I could edit anything. I had to keep returning to the HTML view to make changes - made even more difficult because the cursor positions of the two views appear to be independant. Apart from that - it's a great site and I use it very often.
Dave
If you look at Dave's homepage he has three articles listed with the same title. Click on each one and two would appear to be 'ghosts', with only the middle one linking to the real article. I saw the same thing on someone else's homepage earlier today (federico strati I think).
Just say 'NO' to evaluated arguments for diadic functions! Ash
-
If you look at Dave's homepage he has three articles listed with the same title. Click on each one and two would appear to be 'ghosts', with only the middle one linking to the real article. I saw the same thing on someone else's homepage earlier today (federico strati I think).
Just say 'NO' to evaluated arguments for diadic functions! Ash
really? I see two, one on Reparse Points, one on Command Pattern. FF3.6.10 :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
really? I see two, one on Reparse Points, one on Command Pattern. FF3.6.10 :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
I see four, one on Reparse Points and three on Command Pattern. :Google Chrome.
Just say 'NO' to evaluated arguments for diadic functions! Ash
Thanks guys. I'm not a CodeProject regular and didn't realise I could delete the oddballs myself on the "my articles" page, which I have now done. I seem to remember reporting the same problem when I submitted the article on reparse points way back when. It would be nice if an article and its basename (.aspx page name) wasn't actually cast in stone until a bit later in the creation process, to allow the writer to change his/her mind. Or alternatively, if an article exists from the moment the first page is filled in and the basename defined, then the author should be able to then come back to that article and complete it, but as far as I know that isn't possible either - you can't edit an article until the final text page as been completed - or am I wrong? However I imagine that such upgrades would require fundamental changes to the way CP works, so I guess we live with it.
Dave
-
Thanks guys. I'm not a CodeProject regular and didn't realise I could delete the oddballs myself on the "my articles" page, which I have now done. I seem to remember reporting the same problem when I submitted the article on reparse points way back when. It would be nice if an article and its basename (.aspx page name) wasn't actually cast in stone until a bit later in the creation process, to allow the writer to change his/her mind. Or alternatively, if an article exists from the moment the first page is filled in and the basename defined, then the author should be able to then come back to that article and complete it, but as far as I know that isn't possible either - you can't edit an article until the final text page as been completed - or am I wrong? However I imagine that such upgrades would require fundamental changes to the way CP works, so I guess we live with it.
Dave
I have not used the article wizard so cannot answer your questions. However, there is an alternative, and that is to download the article template, create the article on your own PC and then email the finished product. After publication you are still able to re-download the sources and resubmit with any changes you want.
Just say 'NO' to evaluated arguments for diadic functions! Ash
-
I have just posted an article and 3 matters arose which I wanted to tell you about: 1) If you fill in the first page (Naming and setup), press the "Next, article uploads" button and then for whatever reason decide to stop and start again later, you find that the basename you used has been created, and when you try again you get a "basename already in use" error and have to think of a new name. 2) I couldn't find the "skill level" selector on page 1 anywhere, although it is mentioned in the notes 3) I submitted a large article by preparing it as HTML first, selecting the "bare HTML <>" button on the subission page and pasting the whole lot in. When I pressed <> again to return to WYSIWYG view I found I could edit anything. I had to keep returning to the HTML view to make changes - made even more difficult because the cursor positions of the two views appear to be independant. Apart from that - it's a great site and I use it very often.
Dave
1. This is a known issue because we allow members to start, and then come back to, half completed articles (they are in "composiing" status, as opposed the alternative status some of our extremely old articles are in). A better wizard is being planned which should solve this. 2. Good catch - I will fix the wording 3. This is, unfortunately, one of those things that the web does poorly. Trying to synchronise the code and design views (which are two completely different objects under the hood) has defeated us.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Thanks guys. I'm not a CodeProject regular and didn't realise I could delete the oddballs myself on the "my articles" page, which I have now done. I seem to remember reporting the same problem when I submitted the article on reparse points way back when. It would be nice if an article and its basename (.aspx page name) wasn't actually cast in stone until a bit later in the creation process, to allow the writer to change his/her mind. Or alternatively, if an article exists from the moment the first page is filled in and the basename defined, then the author should be able to then come back to that article and complete it, but as far as I know that isn't possible either - you can't edit an article until the final text page as been completed - or am I wrong? However I imagine that such upgrades would require fundamental changes to the way CP works, so I guess we live with it.
Dave
what you can do is fill each page of the Article Submission scheme, entering only a very short preliminary article body, and ticking the "Do not publish, still composing" checkbox. That will keep most others from seeing your article-to-be. Now you can return and finish it later at your leisure. I do agree, it goes wrong if you abort the process midway. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.