After updating FTP files for website – blog link doesn't work

Since the rest of it works, maybe it’s something simple like you need to reset the posts page? Did you check that setting and the menu?

So after you log in you get a blank page?

You can see it, kmessinger. The blog link on the menu gives you a blank page.

Sorry. I wanted to know if they can get to the back-end.

Alright sunrader and kmessinger – heard back from bluehost and they suggested a few solutions. Only problem is that the files they reference (i.e. wp-content/themesfolder, .htaccess etc.) aren’t in the FTP section of our account. Then I just realized that when I go to the plugins section of wordpress it says we don’t have any plugins (we had a bunch). When I go to the ‘editor’ section I get a message saying the requested theme does not exist. Nothing other than that pops up. I’m at a complete and total loss. Is there something I’m missing? All of our posts/media are still there though… I wish I was smarter…

Unfortunately, we’re not allowed to offer to look at things. Makes it hard to help in a situation like this. Since your site is up, you must have wp-content and you must have the themes folder so I have to guess you are not looking in the right place. In your file manager these would not be in the ftp section. They’d be in a folder with the domain name or under public_html.

Hey sunrader – I’m sorry if I wasn’t clear – our blog site is not up. And I used the term FTP incorrectly, I was looking in public_html in our ‘blog’ subcategory (where those files formerly resided). While in the dashboard of our WP-site – all plugins are gone, all themes are gone (we had a custom built theme). And we hadn’t changed anything on our wp-blog for quite awhile. Cannot figure out what to do or what altered these things. Was thinking about installing a new theme and when I went to the theme’s page I got these warnings at the top of the page –

Warning: Invalid argument supplied for foreach() in /home7/apluslph/public_html/blog/wp-admin/theme-install.php on line 37

Warning: array_keys() expects parameter 1 to be array, boolean given in /home7/apluslph/public_html/blog/wp-admin/theme-install.php on line 59

I’m not sure if I’m looking at a bluehost issue or WP.

Where did you get the pagelines theme?

the pagelines theme was custom made for us by a designer who shortly after designing it, disappeared.

But I also have an update: bluehost “fixed” something on their end which brought back our themes/plugins etc. But now I’m getting errors at the top of our WP dashboard. And when you go to the public view of our blog there are tons of error messages at the top.

Since bluehost was able to correct some things, I’m assuming the problem originated from them. Especially since last week our email accounts were mysteriously deleted from their server. What a headache. Appreciate all the help and if you have any other advice I will continue appreciating it!

here are some of the errors – there are about twenty more like this…

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/admin/class.options.metapanel.php on line 270

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/admin/class.options.metapanel.php on line 270

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/admin/class.options.metapanel.php on line 270

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/admin/class.options.metapanel.php on line 260

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.layout.php on line 24

Warning: Creating default object from empty value in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.layout.php on line 203

Warning: Illegal string offset ‘type’ in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.typography.php on line 585

Warning: Illegal string offset ‘type’ in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.typography.php on line 585

Warning: Illegal string offset ‘val’ in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.css.php on line 82

Warning: Illegal string offset ‘type’ in /home7/apluslph/public_html/blog/wp-content/themes/pagelines/includes/class.css.php on line 89

That clearly shows a problem with your theme.

Switch to the twentyfourteen theme and see what happens.

Custom themes are not supported on this forum. We have no way of knowing what the developer did with the theme or even the wordpress files.

Simple answer..

This theme was written pre PHP 5.3 and your host has updated you to PHP 5.4 or above, which has stricter warnings.

2 choices…

1. ask your host why errors are printed to your end users, this is off by default in PHP
2. Update the theme, the source has been available for a couple of years now
https://github.com/pagelines/PageLines-Framework

If you dont want to update the whole theme ( we dont know what version you have as you didnt give anyone a URL to work with ) then you can just update the one file that has the fix that suppresses the warnings – https://github.com/pagelines/PageLines-Framework/blob/master/functions.php

Its probably a good idea to focus on updating the theme to a more recent version… If you leave old themes or plugins that havent been updated on your site for long periods of time, it would be a recipie for getting hacked eventually. But, while you’re figuring this out you could just set the account to use php5.2

Also recent versions of wordpress work better/faster on php 5.4 (so theres a lot of other benefits other than just not getting hacked which is “huge”).

———————-
Also 2 things, make sure that you have a php.ini file that has these lines (without a semicolon in front of it), display errors by default is on – not off (https://www.phpknowhow.com/configuration/php-ini-error-settings/)
display_errors = Off
error_reporting = E_ALL & ~E_STRICT

and that in wp-config.php (near the bottom) there is a line that says:
define(‘WP_DEBUG’, false);