![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
WTH LJ?!!!
Aug. 22nd, 2008 02:02 pmFRIGGEN HUGE DILEMMA THAT I CAN'T SEEM TO SOLVE!!
Okay. Need to rant. I tried to be patient but I am quickly loosing my nerve over here.
It seems that LJ is getting more and more fussy with entries then ever before, or is that just me???
Posting entries is fine. The "rich text" option makes things a hell of a lot easier than using the old html system. I have no complaints about that. HOWEVER when I go to edit entries, it now doesn't work for me!! The screen automatically loads the HTML version! But I need to edit using the RICH TEXT system because I am not a computer engineer student who can translate a million computer codes!!
Often, my entries need lots of edits before I make the final post because I often write too much for LJ to handle. Then I get stuck with the "post client error" crap. FINE. I got used to that and worked around it. BUT how am I supposed to work around it if I am no longer allowed to edit in the RICH TEXT mode?! It's impossible to post a new chapter without making a few edits.
Why is it all of a sudden barring me from RICH TEXT in my edit option??
Are you starting to understand my dilemma? Until I can edit in RICH TEXT code like in the past, I can't see how I'd be able to post up the new chapters.
LJ wth is wrong with you?!!
Is this problem just happening for me? If so, then that's not even funny. T___T
I'll see if I can update the new chapter all in one hit but I really don't have much time to be fooling around here with that giant pile of uni work laughing at me. ^^;;
*SIGH* I looked at a special LJ announcement just then:
Users using Firefox 3 have reported problems creating links in the Rich Text editor. Developers are investigating this issue, but in the meantime, you can create links in your journal entries by using the HTML editor.
Yeh sure, thanks. Yes I have Firefox 3 but Ive updated chapters before using firefox 3!!! It doesn't explain what is happening NOW! Plus, I tried doing it in my Internet Explorer and the same problem happened. Aiiiiiish. I'm getting such a headache.
Okay. Need to rant. I tried to be patient but I am quickly loosing my nerve over here.
It seems that LJ is getting more and more fussy with entries then ever before, or is that just me???
Posting entries is fine. The "rich text" option makes things a hell of a lot easier than using the old html system. I have no complaints about that. HOWEVER when I go to edit entries, it now doesn't work for me!! The screen automatically loads the HTML version! But I need to edit using the RICH TEXT system because I am not a computer engineer student who can translate a million computer codes!!
Often, my entries need lots of edits before I make the final post because I often write too much for LJ to handle. Then I get stuck with the "post client error" crap. FINE. I got used to that and worked around it. BUT how am I supposed to work around it if I am no longer allowed to edit in the RICH TEXT mode?! It's impossible to post a new chapter without making a few edits.
Why is it all of a sudden barring me from RICH TEXT in my edit option??
Are you starting to understand my dilemma? Until I can edit in RICH TEXT code like in the past, I can't see how I'd be able to post up the new chapters.
LJ wth is wrong with you?!!
Is this problem just happening for me? If so, then that's not even funny. T___T
I'll see if I can update the new chapter all in one hit but I really don't have much time to be fooling around here with that giant pile of uni work laughing at me. ^^;;
*SIGH* I looked at a special LJ announcement just then:
Users using Firefox 3 have reported problems creating links in the Rich Text editor. Developers are investigating this issue, but in the meantime, you can create links in your journal entries by using the HTML editor.
Yeh sure, thanks. Yes I have Firefox 3 but Ive updated chapters before using firefox 3!!! It doesn't explain what is happening NOW! Plus, I tried doing it in my Internet Explorer and the same problem happened. Aiiiiiish. I'm getting such a headache.
