Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Daniel Floeter

    (@kometschuh)

    Can you try to delete the old instance in the widget-area and move the widget new to the sidebar?
    Or try to make a new clean installation for the widget?

    We change a lot of namespaces, constances, etc. Don’t know if this curse the appereance.

    Plugin Author Mark-k

    (@mark-k)

    The HTML is actually still there, but your CSS positions it outside of the screen with the following rule

    #recent-posts-3, #categoryposts-3, #category-posts-2
    {
    position: absolute;
    left: 750px;
    }

    found in your 2c-r-fixed.css file

    Thread Starter greyjunk

    (@greyjunk)

    Thanks, but the 2c-r-fixed.css file has been in use and unchanged since before v 4.1.9?

    Plugin Author Daniel Floeter

    (@kometschuh)

    The style sheet in 2c-r-fixed.css select our widget with ‘#category-posts-2’. Don’t know why there is a selector which is exactly what we are using in our renderd html.

    If you don’t want to change the 2c-r-fixed.css file and delete the selector ‘#category-posts-2’ in line 126 you can try to drag&drop our widget a again to the widget area and delete the old, that the widget get a id like ‘category-posts-3`’.

    Plugin Author Mark-k

    (@mark-k)

    hmm, I see where the bug comes from. The id on the UL is not needed. Not sure what I was thinking of when I added the code (probably the shortcode….). Will need to think about how to resolve it.

    Plugin Author Mark-k

    (@mark-k)

    I just updated from 4.1.9 to 4.6.1 as well and all of the post disappeared on my pages (11 pages of them) as well. I got a “plugin not found” error on each page.

    I deleted each instance of the plug in on each page and then re-added the widget (and all details) and it worked fine.

    Pretty disappointing to have to re-do all of those pages because of an update. I hope the new update keeps working.

    Plugin Author Mark-k

    (@mark-k)

    🙁 it is not very helpful to come and say “there was a problem” and not let us try to figure out what it was so we can fix it to the benefit of all other people.

    Anyway, that message did not come from our code, so can’t even guess what was the issue you faced.

    Thread Starter greyjunk

    (@greyjunk)

    Sorry for the late update guys, the plugin version 4.6.2 certainly solved my problem.

    Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Update from 4.1.9 to 4.6.1 posts no longer showing’ is closed to new replies.