We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

SOLVED: None vs. XHTML Formatting Error with LG TinyMCE

Development and Programming

R.BIRD's avatar
R.BIRD
41 posts
17 years ago
R.BIRD's avatar R.BIRD

There may be an error with Text Formatting XHTML versus None in the custom Field Type selector WYSIWYG.

I’m not sure how best to describe this. But, it appears that the results of WYSIWYG field type are being processed by EE as if XHTML rather than NONE.

I’ve discovered this while editing a blockquote in LG TinyMCE. If I look at html in the editor, I see:

This is a paragraph before the blockquote
<blockquote>This is the blockquote paragraph</blockquote>
This is a paragraph after the blockquote

Which, is correct form. But, here’s what’s being rendered to the browser by EE:

This is a paragraph before the blockquote


<blockquote>


This is the blockquote paragraph


</blockquote>
This is a paragraph after the blockquote

The same effect can be duplicated by using EE’s First Party TinyMCE extension and choosing XHTML as the formatting type. By changing formatting type to NONE, the problem is eliminated.

So, it appears as if EE is processing the WYSIWYG LG field type output as if it were labeled XHTML. Does this make sense?

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Hey R.BIRD,

When using a WYSIWYG editor the output should always be set to ‘none’. This is because the WYSIWYF editor is already adding the markup as you go. The latest version of LG TinyMCE automatically chooses ‘none’ for you so if your not using the latest I recommend upgrading.

Cheers Leevi

       
R.BIRD's avatar
R.BIRD
41 posts
17 years ago
R.BIRD's avatar R.BIRD

I think that’s what I’m getting at. It doesn’t appear that LG TinyMCE is, indeed, automatically setting “none” for formatting.

EE 1.62 TinyMCE 3.1 LG TinyMCE 1.2.1

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Try this…

Go to your custom field.. change the field format to text.. Then back to WYSIWYG and save. You might have had an older version that was not setting the formatting by default.

If that doesn’t work change the field type to textarea, change the formatting to none and then change the type back to WYSIWYG

Cheers

       
R.BIRD's avatar
R.BIRD
41 posts
17 years ago
R.BIRD's avatar R.BIRD

The first of your two suggestions did the trick.

How am I going to remember this one?!

Thank you very much.

+

(By the way, documentation on your website says the following:)

  • Create a new custom field in an existing weblog and choose LG TinyMCE as the field type.
  • Set the default text formatting to None
  • Hide the formatting menu
  • Save the custom field
       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

You shouldn’t have to 😊

I’ll add a note for those who are upgrading from a previous version to the latest that this is a set.. Time to add an upgrading section to the docs me thinks… Glad you got it working….

Can you add “SOLVED:” to the front of your post title so others who have this issue can see we came to a quick and simple resolution?

Cheers Leevi

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

I tried this solution but here’s what I get:

This is a test

March 15

summer school

When it is supposed to be this:

This is a test

March 15

summer school

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Ventistudios,

Which version of LG TinyMCE are you using?

Cheers

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

This is what I downloaded:

lg-tinymce-2.1.1

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Do you mean 1.2.1? What is the extension management showing as the version number?

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

I am really not sure how to tell. What I posted is what the folder was labeled.

I think this is the one I downloaded from this site:

Download old TinyMCE 2.1.3 stable

http://tinymce.moxiecode.com/download.php

I just followed the word “stable”, should I have done the 3.0 version.

Could you direct where and what I need to download and how I might go about upgrading if necessary?

Thank you very much!

       
Leevi Graham's avatar
Leevi Graham
1,143 posts
17 years ago
Leevi Graham's avatar Leevi Graham

Hey Venti,

I was actually referring to the LG TinyMCE extension version number not TinyMCE itself.

Cheers

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

The name of the folder is “lg-tinymce-2.1.1”.

I looked at the code within the extension.php file and found this:

version 1.2.1

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

And it’s also in the extension manager like you said.

LG TinyMCE (v.1.2.1)

       
ventistudios's avatar
ventistudios
56 posts
17 years ago
ventistudios's avatar ventistudios

Leevi,

Should I replace the extension?

Thanks.

Bryan

       
1 2 3

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.