Tags Archive Page & Category Archive

[Joerg_Knoerchen]

Hi,

I wonder why my site http://www.sensorgrafie.de/blog/tag/feuerwerk and the categories page http://www.sensorgrafie.de/blog/category/fotografie/projekte do not look like my standard blog page?

At the archive pages the side widgets are displayed above the footer!? 

At least the settings for the blog page http://www.sensorgrafie.de/blog and all other pages are the same, they are all set to “Sidebars on Right”.

The only exception is for sites and the default pages which are set to “No sidebars, content only”.

Any idea what breaks it?

Many thanks.

Joerg

[scrambler]

These are usually caused by open close HTML tags missing. They break the container nesting.

Your first linked page does report a stray <div> tag, so go through your content carefully and find out where the problem is.

 

[Joerg_Knoerchen]

Mhmh, if there is an issue with a <DIV> at my content, why does the blog page or any other display well? I checked all widgets and they look ok to me, I also checked my custom shortcodes. So I wonder if the issue comes from the archive page itself?

[scrambler]

HTML errors will cause different problems on different browsers and with different content. The browser always tryes to figure it out, but depending on the context will reach different conclusions.

In your first linked page, you have an extra </div> at line 372 which is at the bottom of the content area. It destroys the nesting of the containers.

You also have an opened <i> tag in a widget ( <i>Thema Unerwünschte Bildelemente…) which is never closed

[Joerg_Knoerchen]

I know it is hard to find that buggy DIV, but first I cannot confirm that any of my random text do have an <i> tag that will never close, I have gone through all of the random text posts and all have valid HTML. Secondly you said that my first linked page has an extra DIV do you mean the article or just the RAW HTML? Because regardless of which category or tag I use all pages are broken. So the extra DIV must come from somewhere more generic not any specific Widget or Post.

I experience the same thing at a different blog where I use Weaver Xtreme by the way!

[scrambler]

on http://www.sensorgrafie.de/blog/tag/feuerwerk/ The extra div is after the posts so I am not sure how it gets there.

Check the content editor of the post page and also the post content HTML Insertion areas

The blog page appears to use two columns, but there is only one post. Can you try to switch it back to one column and see if it makes a difference.

Also create a test page and redo the post page in there to see what happens with that new test page (give us a link)

Ignore the <i> I don’t see it anymore.

if you have the problem on a different blog, please give us the link so we can check it and see it there is a similarity

[Joerg_Knoerchen]

Hi scrambler,

many thanks for getting back, as the issue exists also for any other tag or category I do not believe that the extra DIV comes from any of the posts. And as the TAG FEUERWERK only returns one post I did check that post with it’s content (it does not have a single DIV), but there is a custom field for the related posts plugin, which brings in DIV’s but there are only two openings and also to closures. If you mean with post page the “blog” page with “page with posts” template that is entirely empty.

If I set the Tag Archive Page to “No sidebars, content only” the tag archive looks ok, “Use Default” does not change anything, “Sidebars on right (stack Top)” works as expected but in my eyes this should also be the case when I simply use “Sidebars on Right” but then the widgets are below the content area and look like they belong to the footer area as they also get the background color of the footer.

Here is the link of the other blog with a different WP install: http://www.meinnovascotia.de/tag/cape-breton/

I don’t get what you want me do by “Also create a test page and redo the post page in there to see what happens with that new test page (give us a link)” a new blog page? The current one has nothing in it!?

[scrambler]

That new page has exactly the same problem, but I digged further, and the issue is not that there is an extra closing divs, but that there is a missing opening divs.

I understand you are using two columns masonry post settings, including for the archive page (please confirm all your related settings)

When I do that on my test site, the structure of the archive page is the following

<div class=”wvrx-posts”>
  <div id=”blog-posts” class=”cf”>
    <div class=”cf blog-post blog-post-cols-2″>
    .
    </div> <!– .blog-post –>
    <div class=”cf blog-post blog-post-cols-2″>
    .
    </div> <!– .blog-post –>
  </div> <!– #blog-posts –>
</div>

But on your pages it shows

<div class=”wvrx-posts”>
    <div class=”cf blog-post blog-post-cols-2″>
    .
    </div> <!– .blog-post –>
    <div class=”cf blog-post blog-post-cols-2″>
    .
    </div> <!– .blog-post –>
  </div> <!– #blog-posts –>

The Opening div with the ID #blog-posts  is missing, but its closing div is there, creating an open/close tag HTML error

if you have not already done so, you need to test deactivating ALL non weaver plugin, to check if one could be responsible for that.

Next you need to make sure you that have the latest versions of everything weaver related.

@weaver can you think of anything that could be responsible for the missing Opening div for the 2 column masonry archive post page??

[Joerg_Knoerchen]

Hi scrambler I need to check the settings tomorrow as I am now off. But as far as I know I have just used common settings so no customizations. The only thing we did was to make the first post on each blog page to be the featured one. For my understanding please, which page template is used to display the archive pages?

[scrambler]

You don’t have access to the archive template. it is one of the PHP template of the theme, but knowing all the options you have set can help me make sure I can test the same configuration as yours.

[Joerg_Knoerchen]

Wouldn’t it be easier to save my settings and send them to you?

[scrambler]

Have you tried deactivating ALL non weaver plugins, and what version of the X Plus and X theme support are you running?

You can save ALL settings from the +Xtreme Plus > Save restore page and send them to the email I will PM you

[Joerg_Knoerchen]

I’m using Weaver Xtreme 2.0.7 Options – Plus (2.0.1) as I can’t deactivate all non weaver plugins, I will try to do this on my stage. I’ll send you the settings right away.

I have deactivated all non weaver plugins on my stage and do have the same results. As soon as I enter the tag or category archive the sidebars slip down into the footer.

[Weaver]

So I am trying to get a handle on this one now.

The page in question seems to be: http://www.sensorgrafie.de/blog/tag/feuerwerk/ – is that correct?

On that page, I do see the div mis-matching as described by @scrambler.

That page seems to be a tag archive page – generated by the theme’s tag.php template file.

You are using 2 column layout.

I’m going to try to track down any missing generated div’s in the code (which is identical for all archives – archive, tag, category, author).

[Weaver]

Does seem to be a bug with options for archive columns and masonry columns option values.

[Weaver]

@Joerg_Knoerchen, @scrambler –

Found the bug. Amazing no one has ever found this one before!

The bug involved a problem with using Masonry columns on archive pages. There was an extra </div> being emitted in some cases. I’ll send a fixed version along for you to see. It is hard to know exactly what your options were, but just playing with the various options for masonry columns, it seems to be working properly now.

[Author]

Posts