Forum Replies Created
-
Posts
-
flyingpylon:
I received several suggestions (below). I don't know that I should say which of these worked, since each install is unique. But it was an easy fix ...
1- Look at the functions.php file for your theme. Have you added any custom code? Could it be contributing to this problem?
2- At the following page, do you see a prompt to upgrade your WordPress database?
your-domain-whatever.com/wp-admin/upgrade.php
If you see an upgrade prompt, make a full backup of your site. Then click the button to upgrade your WP database.
Then upgrade Genesis to 2.2.62- Do you have a caching plugin enabled? When you deactivate plugins and test, do you clear the cache and deactivated the cache plugin? If not, first clear the cache of cache plugin, then deactivate the plugin. Then perform the
Genesis upgrade again to see if the error persists. If so, try deactivating other plugins again while the cache plugin remains disabled.But I would like to know if there's a way to make my HTML text editor (Notepad++) recognize errors in WordPress-specific text like shortcodes? It already does that with regular HTML.
User error. The process of carefully composing the post made me see that
mp3was missing from the meditation shortcode. WordPress was evidently pulling up the last good version of that. Now I know the likely diagnosis if a link on a WordPress page starts pulling old content. Thanks anyway.Well I searched the entire Outreach Pro child theme folder for the text string "search" and no results except inside style.css. I'm stumped. Seems like such a simple idea to just insert a back to top link. PS Searched for any files with string "search" in their name. Zip.
The code is what's in the browser if I do Ctrl-U. I've tried Notepad++ searches looking for various unique text strings* in any php or js file inside the WordPress directory.
( *footer-widgets-4, widget-area, widget-wrap, "Search this site", etc )When I get in front of the PC on Saturday I'll try again to find something in the Outreach Pro files. But I'm surprised nothing has come up before, since that's a sub-directory of the main directory I searched. And I had the box ticked to drill down. Thanks, Savvyjackie.
Two bits of news for anyone who may wander down this road:
1- Someone has proposed a simple CSS solution that I'm now using. By adding/removing the page-id selector, and by taking advantage of the fact that CSS is processed in order, with the most recent code having priority.
2- It's been suggested I can use a conditional tag inside functions.php via a WordPress hook. So that's my side project while the site functions happily via the CSS mod, proposed by "CrouchingBruin" ....nav-primary #menu-item-572, .nav-primary #menu-item-658, .nav-primary #menu-item-747 { display: none; } .page-id-2 .nav-primary #menu-item-572, .page-id-2 .nav-primary #menu-item-658, .page-id-2 .nav-primary #menu-item-747 { display: inline-block; } .page-id-2 .nav-primary #menu-item-834 { display: none; }From the codex:
You can only use conditional query tags after the posts_selection action hook in WordPress (the wp action hook is the first one through which you can use these conditionals). For themes, this means the conditional tag will never work properly if you are using it in the body of functions.php, i.e. outside of a function.
Not a happy camper.
Partial progress. The css file being loaded had to go in the Genesis directory instead of the Outreach Pro directory where everything else is going on.
The last remaining problem is getting this PHP "if" statement to tell the difference between the default first page in the site and everything else. I tried it with both || and && between the two names for such a page.
if ( ! is_front_page () && is_home() )Using these two ampersands nothing at all happens on either the splash page. Using two pipes does load the style but the not (!) is somehow non-functional. The css loads everywhere including the splash where it's not needed.