vrocks

In the websites main directory locate the file wp-config.php and edit the line that references WP_DEBUG and change FALSE to TRUE.

You should see errors that will give you more clues.

Changes to make the search inline with the menu.

#block-bd8540721a7c805a .nav-search-active .nav-search {
height: 45px;
line-height: 45px;
/* adding these two lines */
display: inline-block;
float: right;
}
.block-type-navigation .nav-search-active #searchform {
height: 100%;
/* commenting out the following line */
/* display: table-cell; */
vertical-align: middle;
}

Then consider appending “on your keyboard” to the wording inside the search box.

https://prntscr.com/4lsd25
Look at that screen grab and then tell me by number reference what gaps you are referring to.

This is happening because your Magnific Popup plugin is overriding the link and trying to make the image into a lightbox style popup.

<a class="image-link"

Not familiar enough with the plugin to know if it has some kind of override.

Instead of renaming the plugins folder, rename the folder for iThemes Security. That will stop the plugin from being found. You can rename it back and reactivate it inside the admin later.

Some basic instructions on creating a child theme:

1) Open an FTP program and go to the wp-content/themes directory in your server for the domain you are trying to do this on.
2) Notice the theme directory of the theme you are using. Example: twentyfourteen
3) Create a new directory in the themes directory and name it the same as your themes name with -child appended to it. Example: twentyfourteen-child
4) Copy as a BARE minimum the style.css file from your current theme into the new directory and open it. Add in this line (using our current example of twentyfourteen):
Template: twentyfourteen
5) Also consider appending to the line that says: Theme Name: the word child:
Theme Name: Twentyfourteen Child
6) Copy any files you wish to edit into the new theme’s directory. Edit them in there and don’t touch the files in the old directory. This way when a new version of that theme gets published and you update it in your blog the files you have changed don’t get overwritten.

Now go to your wordpress blogs admin and switch to this new child theme.

* Do not copy the functions.php file into the new child theme directory. This is break your blog. If you intend to add functions code just create a new file inside the child theme called functions.php and only place into it the new code which will be run along with the old functions.php file’s code.

To delete themes, click on a theme and it will popup the theme details. There is a delete link at the lower right hand corner of the popup.

You must have at least one theme to run a blog. Usually the default is twentyfourteen. Is that what you meant by no theme?

https://ts.w.org/wp-content/themes/twentyfourteen/screenshot.png?ver=1.2

When you get to your last theme, you cannot delete it because WP needs at least one theme to be present.

Works for me as well..

I am having the same problem too. Converts URI’s to absolute paths.

Hmm… I just got familiar with MONyog and found that W3TC was pulling the DB, getting hung in the process and then causing the server to run out of memory as the PHP processes that were opening to handle the MYSQL requests were freezing while they waited.

Odd because the entire idea of having a DB cache is to not pull from the DB…

But at least I got to familiarize myself with MONyog for the first time.

Oh, the site is was on gets about 15 hits a day… So this was all very odd..

Now it is looking like cronless postie plugin was possibly not compatible with this plugin. Somehow cronless postie got stuck in a loop… Never happened until I installed this plugin.

FreeBSD lightyear.bgci.net 7.1-STABLE FreeBSD 7.1-STABLE
Apache/1.3.41
PHP Version 5.2.9

Switching to white activated from green activated was the stupidest switch I can think off… Makes absolutely no sense… Whom among us came to that page and just about had a heart attack thinking they were all deactivated after the upgrade?

I concur… lame way of doing an upgrade… You can use the automatic upgrade plugin… I think it does preserve templates… But not 100% sure though…

Also, you should copy the template you are using to a new directory… Like if you use default, copy it to default2 and then upgrade and use that one… Makes it so you don’t have this problem… ever…

Upgrade still sux…

I could not reproduce error #2 in either the wordpress admin or by using Windows Live Writer to post via XMLRPC. Which means this is a problem specific to you.

What are you using to post to your blogs?