max-sewell

I’m experiencing this error too –with WordPress 5.7…

Will this plugin be compatible with WordPress 5.7?

I’ve been receiving warnings about the 5.7 update and other sidebar plugins.

You ROCK, Michael. It works like a charm! Thank you very much.

Max

Hi, Thanks. Now I get it.

I had originally created a static page for “blog” and just had to go into that page and change the permalink.

I’ve found I’d been using the wrong code on header.php. It should have been:

<!– #site-navigation –>
<nav id=”site-navigation” class=”main-navigation” role=”navigation”>
<button class=”menu-toggle”><?php _e( ‘Menu’, ‘twentytwelve’ ); ?></button>
“><?php _e( ‘Skip to content’, ‘twentytwelve’ ); ?>
<?php wp_nav_menu( array( ‘theme_location’ => ‘primary’, ‘menu_class’ => ‘nav-menu’ ) ); ?>
</nav><!– #site-navigation –>

I found I’;d been using the wrong code on header.php. It should have been:

<!-- #site-navigation -->
<nav id="site-navigation" class="main-navigation" role="navigation">
<button class="menu-toggle"><?php _e( 'Menu', 'twentytwelve' ); ?></button>
<a href="#content">"><?php _e( 'Skip to content', 'twentytwelve' ); ?></a>
<?php wp_nav_menu( array( 'theme_location' => 'primary', 'menu_class' => 'nav-menu' ) ); ?>
</nav>
<!-- #site-navigation -->

Thanks I will do that.

My son figured this out for me. We replaced the php code in the form action with the domain: and everything works.

<form method=”get” id=”searchform” action=”https://newsite.discovereuropeltd.com/newsite/”&gt;

Sorry for the bother.

This is the code I used (on the page) –A variant of it is in the template for the second field:

<div style=”width:440px;height:30px;”>
<form method=”get” id=”searchform” action=”<?php bloginfo(‘url’); ?>/”>
<label class=”hidden” for=”s”><?php _e(‘Search for:’); ?></label>
<div>
<table><tr><td>Search Upcoming Tours: </td><td><input style=”width:150px;” type=”text” value=”Type in a country name” name=”s” id=”s” onfocus=”if (this.value == ‘Type in a country name’) {this.value = ”;}” onblur=”if (this.value == ”) {this.value = ‘Type in a country name’;}” /></td><td><input type=”submit” id=”searchsubmit” value=”Search” /></td></tr></table>
</div>
<input type=”hidden” name=”taxonomy” value=”tours”>
<input type=”hidden” name=”term” value=”2013″>
<input type=”hidden” name=”orderby” value=”date”>
<input type=”hidden” name=”order” value=”asc”>
</form>
</div>

You rock! Thank you for taking the time to answer this.

Max

I have resolved this issue. The host had created the database and installed WordPress on the server, giving me (only) access by FTP and PHPMyAdmin. This host didn’t respond to phone or email when contacted. To complicate things, the host had actually created two WordPress installs, and I was left to determine which install was associated with the DB I had PHPMyAdmin access to. It turned out that neither WP install pointed to that DB, and I had to do some searching to figure out how to point one of them to that DB (I ended up using the IP in wp-config which I had never done before). Once that was accomplished, the site operated fine.

Yes, and while I haven’t changed the site addresses before this switch (I was planning on doing so after the move), I still would expect SOME change in a browser view. Not just the same virgin install. Broken pages. Even (heaven forbid) a white screen of death. Some difference.

Does what I have done seem like that was a reasonable expectation? Did I miss moving some file or directory that I would need?

I think I’ve managed to solve this problem with my host. It was an issue of the domain and subdomain both pointing to the root directory. Sorry for the bother.

Thanks WPyogi. We’ll give those suggestions a try. I haven’t tried access at her home, because she’s in the next state. I may have to though. I expect the idea of running terminal will be pretty intimidating to her.

Still no luck on this issue. The client can load wp-login.php on their laptop at school (running OSX Lion 10.7.5), but not at home using Chrome, Safari, and Firefox.

Any ideas?

I’ve replaced wp-login.php in case there was a corrupt file, though I’ve been able to access the page on Mac using Firefox, Safari and Chrome; and PC using Explorer, Firefox and Chrome.