Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#30318 closed feature request (wontfix)

WP 4.0 default_editor bug

Reported by: wpxritter's profile wpxritter Owned by:
Milestone: Priority: normal
Severity: normal Version: 0.71
Component: Formatting Keywords: close
Focuses: administration Cc:

Description

Dear WordPress,

I using WP 4.0. I like WordPress..but
I´ve got the big Problem with the WP-Editor,
it have the property, that it overwrite the HTML-code
while saving or switching between the visual-editor and
the text-Editor funktion.
The problem exists longer - in other versions too.
The WordPress-Editor will supplement my code with -p an -br tags
or delete this. The result is it´will destroy my code.. its
an desaster to correct than after and I must stay in
the text-editor-mode to don´t have a again..

This is a great problem, and makes a lot of trouble by
using of developers or clients.
If you search in web, google "wordpress editor changes html code",
you´ll see.

Have the vision, you´ll write a book biography in a programm
,for example office-word, and save,
and the autosave-funktion will complete
your Manuscript with paragraphs, question mark and other markups
and delete the half.. What would you say?

To troubleshooting this problem, it exist a lot
of plugins, like RAW-HTML, where you must take
an raw-tags into the editor-code, to save it for
the overwrite [raw] ..my html-code.. raw

The Plugin-Editor TinyMCE Advanced have an checkpoint to
Stop Removing the -p and -br / tags. (He know the Problem too)
I tried it, but in WP 4.0 it don´t work, if I switch
between the visual and text mode.

My opinion is, there must be no plugin to save
the problem! This can do WordPress itself!

Could the wordpress default editor not have
a control-switch into the settings, to stop this funktion?
I mean real stop, that all you write into
the edit, it will exactly the same into
my frontend.

I need a real code.. (by saving and switching the mode, too)

I hope so that you make this update in near future,
hope just today :)

I look forward about a response,
With best regards

Ilja Ritter

Change History (6)

#1 in reply to: ↑ description @wpxritter
9 years ago

Last edited 9 years ago by wpxritter (previous) (diff)

#2 @DrewAPicture
9 years ago

  • Component changed from General to TinyMCE
  • Focuses administration added

#3 follow-up: @azaozz
9 years ago

  • Component changed from TinyMCE to Formatting
  • Keywords close added
  • Milestone Awaiting Review deleted
  • Type changed from defect (bug) to feature request
  • Version changed from 4.0 to 0.71

Hi wpxritter. If I understand you correctly, you're proposing to add a checkbox to the user settings that disables wpautop. Currently this can be done with a plugin and several plugins handle it in a slightly different way.

Disabling wpautop() is not recommended for most users. This functionality has existed since the very beginning. Some parts of core and many plugins expect post_content to have double line breaks instead of <p> tags.

In my opinion leaving this to plugins is the right thing to do.

Last edited 9 years ago by azaozz (previous) (diff)

#4 @nacin
9 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

#5 in reply to: ↑ 3 @wpxritter
9 years ago

Replying to azaozz:

Hi wpxritter. If I understand you correctly, you're proposing to add a checkbox to the user settings that disables wpautop. Currently this can be done with a plugin and several plugins handle it in a slightly different way.

Disabling wpautop() is not recommended for most users. This functionality has existed since the very beginning. Some parts of core and many plugins expect post_content to have double line breaks instead of <p> tags.

In my opinion leaving this to plugins is the right thing to do.


Hello azaozz :) thx for your answer!

Yes, that would be nice, if there will be a checkbox in the settings.
I hope I understand you too, you won´t have this update on default settings..
I think the selection for developers to have an wpautop() or not would be very good
for a better handling.

Why must this have only by the plugins? I googled so much people, which have my problem too.. I have asked shortly a german top level WPdesigner from Berlin and himself has no answer out of use the raw-plugin. For my example the TinyMCE-Plugin have the checkbox to stop wpauto but it don´t solve this Problem, it don´t run exactly!?

Can you perhaps show me a good plugin by a link, which have this function?
Sorry my english pronunciation..

with best greetings
wpxritter

#6 @wpxritter
9 years ago

I found a nice declaration with a solution about "custom Fields shortcodes"
a short youTube movie by Craig Smith:

https://www.youtube.com/watch?v=n4aMT1b8kN8

Is there a way without /[shortcode/] tags..?
The problem, to explain some clients the shortcodes is not easy..
and an overwrite by clients using WP independent is
preprogrammed - they'll call the developer help.

I wish you a very nice start in : and a lucky and good NEW YEAR 2015 =>

Last edited 9 years ago by wpxritter (previous) (diff)
Note: See TracTickets for help on using tickets.