Dandy Plow

If you remove the <?php get_sidebar(); ?> from the page you find it on, does it remove it from the page you want to remove it from?

It could be that what appears to be a sidebar is actually contained somewhere else (like in the footer). One thing you can do to find out is to right click the site and click “view source”. Find a div or something that is contained within the sidebar’s source code (ie <div class="sidebar-nav">) and then see if you can find that content in the template pages to track down exactly where the undesirable sidebar is being pulled from.

Are you actually putting “https://” in front of <?php echo get_permalink('28'); ?>? Because that’s uneccessary.

What exactly is happening on the page where it’s not executing?

If you made functions.php produce an error (which could easily happen if you accidentally deleted a brace, semi-colon, or any number of things when you were deleting bad code) then that will completely break the site.

Try going into your ftp and removing everything from your functions.php file, and see if it works then.

Have you looked for the <?php get_sidebar(); ?> call on the page template file? You can remove that from any page to have it not load the sidebar.

You can add other pages to the list with a simple &&:

<?php if( (!is_page( 'en-vivo' )) && (!is_page( 'some-other' )) && (!is_page( 'this-page' )) && (!is_page( 'your-page' )) ) : ?>

Maybe ‘home’ is reserved? Try something random and see if it fixes

Hmmm… And you put the above code into the file? Make sure the template name (where I wrote ‘whatever the name of this is’ ) is unique

Just drag all of the content of your plugins folder onto your desktop, then delete them from the ftp. If that doesn’t work, then you can drag them all right back in and you won’t have lost anything!

can you access via ftp and try removing plugins?

Well if you can connect via ftp with your client, then there must be some other issue than the credentials. FTP login info is FTP login info, so what works for Fugu should work for the WordPress updater.

Maybe your hosting blocks access attempts from certain IP addresses?

It looks like you’re hosted by nearlyfreespeech.net? Might look at some of the info they have on ftp:

https://faq.nearlyfreespeech.net/section/uploading/ftpdoubletrouble#ftpdoubletrouble

your config.php details refer to your mysql database, NOT your ftp.

Hostname is often just your url (ie mysite.com), though it can vary depending on hosting provider. If you log into your hosting website, you should find a section on adding FTP users, where you can create a new username and password

Hmm… my praise of the Crack Fox seems to have been removed. Perhaps too far afield from the matter at hand. At any rate, looking through the Wayback machine, it seems your site went from being WordPress to a custom job at the end of 2010/start of 2011

From your dashboard, go to Page >> Add New then make the new page have just the two links. Then go to Settings >> Reading, select “A static page”, and then choose the page you just created from the drop down.

However, if that page isn’t blank enough because it incorporates elements of your theme, you’ll need to create a new template file. You can access your site via ftp, navigate to yoursite.com/wp-content/themes/yourcurrenttheme and drag in a text document you’ve created on your computer called whatever.php, with the content:

<?php
/*
Template Name: Whatever the name of this is
*/ ?>

Go to this <a href="https://www.cnn.com">external site</a> or <a href="mygreatsite.com">Proceed</a>

You can also more easily create a custom theme template file like this with the FTP-Free Theme File Creator Plugin I built.

Once you’ve done that, create a new page, and before you publish it, look over on the right side where you’ll see “Page Attributes” which has a “Template” dropdown. You’ll see the file you created there. Choose it and publish.

A lot of times, code elsewhere on the site cause a conflict with some random line of code in the WordPress core, and the core file is listed as being the problem even though it’s not. So the fault isn’t actually with the wp-db.php file.

Try switching themes and see if the problem is fixed.

Otherwise, you might review recent comments or posts made to your site… If they have certain types of code written into them, they might be causing strange behavior.

If none of this helps, perhaps you could share a bit more detail? As in whether this only happens on one particular part of the site or every page?

A changed theme can’t change administrative access exactly, though I did notice that going to yoursite/wp-admin brought up a blank page. Is that the issue? Because you can work around that by going to yoursite/wp-login.php

Not sure if that’s what’s going on, but best guess. Again, changing a theme can’t alter log in privileges