In article the <p> tag is not displaying. Paragraphs are all attached, no space between them. Why?

Originally Posted by tralci2013

In article the <p> tag is not displaying. Paragraphs are all attached, no space between them. Why?

Have you tried code validation?

Elsewhere (Opera for instance) it works.

Originally Posted by tralci2013

Elsewhere (Opera for instance) it works.

Most browsers autocorrect and try to figure out what they think you meant to code. They all do it to varying degrees of success, but it's safest to have valid code. Did you validate your code?

Is this happening on the blog page or on a single post page?

On the blog page I don't have any new paragraphs. The problem is in the single pages.

Originally Posted by jerryc

Most browsers autocorrect and try to figure out what they think you meant to code. They all do it to varying degrees of success, but it's safest to have valid code. Did you validate your code?

The validation says there are tens of errors, also regarding parts of the code I never touched.

Originally Posted by tralci2013

The validation says there are tens of errors, also regarding parts of the code I never touched.

There probably aren't that many, but one of them is throwing the others off. For example, sometimes one missing closing </p> or </div> will show all similar tags as errors.

On the validation page, there's an option to view source. Select that. Then, when you click on the error message, it'll show you your code where it's seeing the error. Pay particular attention in the area where you did your edits.

Good luck.

One of the ways to avoid having this be so hard in the future is to validate early and often. If you validate after each edit, it's usually pretty easy to find your mistakes.

Originally Posted by tralci2013

In article the <p> tag is not displaying. Paragraphs are all attached, no space between them. Why?

If you used firebug, you'd see that your p tags are all there, and the style you have set for them is just:

margin: 0;
padding: 0;

Is that what you want? That's what you see. Did you edit this tag at all?

Originally Posted by jerryc

If you used firebug, you'd see that your p tags are all there, and the style you have set for them is just:

margin: 0;
padding: 0;

Is that what you want? That's what you see. Did you edit this tag at all?

Never touched this.

Originally Posted by tralci2013

Never touched this.

OK, I compared it to mine, and it's the same, so it's probably the code validation. Keep digging.

I'm thinking about resetting all the files and upload the modified ones one by one. What do you think?

Originally Posted by tralci2013

In article the <p> tag is not displaying. Paragraphs are all attached, no space between them. Why?

This thread seems to have gotten more complicated than needed.

You won't see the <p> or <br /> tags in the text view.

If you use the visual editor and hit enter it will give you a paragraph break. In the text view you will just see a space between the areas that have the <p> tags.

As mentioned the <p> tag is generated when you hit enter once in visual view or twice in text view leaving a space. for a <br /> you have to hold the shift and hit enter in the visual view or hit enter once in the text view.

Originally Posted by lmilesw

This thread seems to have gotten more complicated than needed.

You won't see the <p> or <br /> tags in the text view.

If you use the visual editor and hit enter it will give you a paragraph break. In the text view you will just see a space between the areas that have the <p> tags.

As mentioned the <p> tag is generated when you hit enter once in visual view or twice in text view leaving a space. for a <br /> you have to hold the shift and hit enter in the visual view or hit enter once in the text view.

When I say that <p> is not displaying I am meaning that on the browser I can't see the paragraph space.

Could you post and example of what is in a post? A cut and paste from the text view would do.

Chrome MacBook

Originally Posted by tralci2013

Chrome MacBook

What does this mean?

SOLVED!

The plugin WP Content Slideshow was conflicting with someone else.