Issues with Nom Nom since updating to WordPress 3.7.1

Featured Theme Forums NomNom Theme Issues with Nom Nom since updating to WordPress 3.7.1

This topic contains 4 replies, has 2 voices, and was last updated by  Zeaks 1 year, 8 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #13457

    David Stembridge
    Participant

    I’ve been using Nom Nom on my site for the past year, love the options, and flexibility. Since updating to WordPress 3.7 though, I have had some issues.

    I went through initially and deactivated all of my plugins, and have gone though one by one reactivating and checking. When I load the NomNom – Theme Options page, it doesn’t load the individual option sub pages.

    Is there an issue with WP 3.7 and Nom Nom? Is the theme still considered “working”

    Thank you!

    #15336

    Zeaks
    Participant

    Hi David, NomNom should still work fine with WordPress 3.7.1 I checked it and the options the day 3.7.1 was released and did not see any issues. I just checked the demo site http://demo.zeaks.org which is running 3.7.1 and everything is fine.

    When you say it doesn’t load the sub pages, are you not able to click on them, or is it displaying them in one long page? Take a screenshot if you can

    #15337

    David Stembridge
    Participant

    When I click on custom css I get this in the menu: http://www.wbcrd.com/wp-admin/themes.php?page=nomnom-theme-options#tabs-5[/COLOR][/FONT][ATTACH=full]136[/ATTACH]

    http://www.wbcrd.com/wp-admin/themes.php?page=nomnom-theme-options#tabs-5

    [ATTACH=full]136[/ATTACH]

    #15338

    David Stembridge
    Participant

    Here’s the link for the attached screenshot: [HTML]http://greenpeas.us/david.stembridge/media/theme-issue.jpg[/HTML]

    #15339

    Zeaks
    Participant

    If you haven’t made any modifications to the template files, you could try uploading files from a fresh zip and overwriting them. I can’t think of any reason it would be displaying like that without any plugins active, it looks like a javascript conflict.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.