About vanishing icons, -1 and HTML mode
|2 min read
linux-rules's avatar
By linux-rules   |   
0 9 1K (1 Today)
Published:
The most interesting tip when this happens, would be to be able to enter into the HTML mode for making a backup of a lenghty description.

When in HTML mode (that you enter with Control+E) you can save a description into a TXT notepad and have a copy if something happens to the description.

There is also another bug that I hope that don't appears to you. It appears with certain trigger words like "technical support". If you write that in any description the description turns into "-1" and you can lost everything in the description.

That is why is good idea to save the code of a description.

There are certain things to know about this. You can add as much icon as you want when in rich mode that most probably they won't vanish. Is when you reload the description (like editing again or coming from HTML mode) when the editor have problems to load all icons again and just remove them.

So, when you finish a description, you press Control+E and you can copy all the description to save it in a txt.

If for any reason (like in comments) you didn't do that and you notice that some icons dissapeared there are two ways: trying to use control+Z (undone) or just switching again to HTML mode (Control+E) when you luckily could still see the code of those vanishing icons.

You have to take also in mind that code it gets almost instantly saved, while rich text it can take a couple of seconds. In sta.sh you have an animation in the "file menu" that warns you when something gets "updated" (synchronized). So, if you change from rich text to HTML too fast you can lost some editing.

I know that all of this sounds confusing because it maybe be first time you hear about it. So, if anything is not clear ASK ME.
Comments9
anonymous's avatar
Join the community to add your comment. Already a deviant? Log In
mitoXD's avatar
mitoXD General Artist
Well, I didn’t know about Ctrl+E, but I’m ’hard-coding’ my dA comments etc. anyway; no need to manually change the input mode.

Further, always I’m trying to mind pre-composing my (longer) texts in a text-editor before pasting them into the dA comment or description fields (and submit).
This way spares me from annoyances and gives the option to save a draft.  :iconbeardstrokeplz:
linux-rules's avatar
linux-rulesHobbyist Artist
thank you for the comment. So, when you write html in normal mode it works fine too? like doing nesting:
  • 1
  • 2

mmm, seems it works but sometimes the code is has some problems and writing directly saves that, I  believe.

yes, that is a good idea :D
mitoXD's avatar
mitoXD General Artist
At least it works for the dA sites (for me). The tags are automatically detected and converted, such as e.g. the (emot)icon shortcuts in the form of ":xxx:", regardless which graphical browser is in use. – However I remember running into problems when I mixed formatted contents with raw HTML. Hence I’m trying to avoid that. Besides interactively pasting icons into HTML via "Add Media" functions flawlessly of course.

Within other CMSes like WordPress or Typo3 it’s different though: In their editors, you simply must explicitly select HTML mode.

Yet pre-composing large portions of text externally (in HTML within an editor that knows syntax highlighting) yields other advantages, too. First, it saves you from data loss in case the website is crashing, or closing the dA browser window by mistake! Further, you can check out your drafts in another tab without submitting. – Look at this gallery for example: The descriptions are all pre-composed and heavily tested.

The only little draw-back with this method is when it comes to post-editing. You’d have to decide whether to do that in the browser or in your editor again for not getting confused with version conflicts and posting old stuff~ But it’s worth the effort!
linux-rules's avatar
linux-rulesHobbyist Artist
Indeed! woah, I couldn't do before a div id. how did you do that? My code with div id was always reconverted...
mitoXD's avatar
mitoXD General Artist
A "div id"?! Please specify.

Any "div id" in the source is dA-internal. Deviants can’t do that; such special tags will be ignored. Please see inetc. (again) what is allowed.
linux-rules's avatar
linux-rulesHobbyist Artist
but you did something similar in here:  ssid-holo by mitoXD ssid-holo#cnts . how you get that placeholder? (#cnts) I don't know much HTML so I though than that could be only achived with div id...
mitoXD's avatar
mitoXD General Artist
That’s just internal hyperlinks. Within the deviation description, I gave different source/reference anchor tags <a ...></a> (empty = unclickable!) at certain positions individual names (like IDs) and referred to them from elsewhere. The source URL href="#" just means the very same page to avoid reloading. So clicking a target link beginning with a hash directly jumps to a named position.

Do a Control + U, find e.g. "cnts" via Control + F and learn about this technique. Find out what happens when the target link is only "#" and requires no explicit source name.

HTH
linux-rules's avatar
linux-rulesHobbyist Artist
You don't know how useful it wast this comment for me. Thank you so much :worship:
View all replies
linux-rules's avatar
linux-rulesHobbyist Artist
I know :D I love internal hyperlinks :D I didn't know that it can be done without div id's Is what I have always used in my blog.

so...a <a href="#" name="cnts"> behaves like a <div id="cnts"> ? :D awesome!!

thank you very much!
View all replies
anonymous's avatar
Join the community to add your comment. Already a deviant? Log In