James Hall

Anytime you setup something “new” on Linux there’s a chance it will setup with the wrong owner.

This doesn’t happen a lot but in rare cases it can happen. In any case, if this isn’t a dedicated server you may need to contact server support to have them check for you who the “Owner” of your account or files is.

If you have a dedicated server, and you have root access, run ls with the -l flag to show the owner and group-owner of files and directories in the current directory (or in a specific named directory).

You can change owners with the CHOWN command

James

Hi juicystar,

The “Call to undefined function” error is likely originating from within the functions.php file of your theme. Did you recently try to add some code manually to your theme files?

If you did, you should still be able to FTP in to your site files. Go to: wp-content/themes/ and rename or delete your theme.

Then your website should revert to a default theme and come back online.

James

Hi michael5211,

It looks like you have accidentally messed up the shortcodes either for that post by manually editing under the “text tab” or you have a child theme where you’ve added some content that should be in every post?

Anyway, I counted 3 copies at the link you provided, and at the bottom of the post you can see this partial shortcode: [/vc_column][/vc_row]

Those improperly place closing brackets are whats causing your content to duplicate, I’m sure. Try disabling your theme builder plugin and see if your content still duplicates?

James

Try launching a private “incognito” browser page, then view your form page.
Did that clear it?

Hi namil7,

It looks like you have 2 plugins adding or re-writing meta tags and titles.
SEO All in One and <!– Meta Tags Generated via https://heymeta.com –>

I would delete the Meta Tag Generator or whatever that plugin by heymeta.com is.
Any WordPress theme worth its salt will have meta tags already – no need for a plugin.

Have a great day!

James

I think this is being triggered by hacker bots looking for security holes. I disabled mine as well.

Hi Andrew,

Okay, that makes sense to me. Thanks for the fast reply!

James

Hey everyone,

If you are as stupid as I was and are having the same issue, make sure you have prices set for each variation that isn’t showing.

Steve over at themeComplete clued me in to what was happening when he looked due to my purchase of their WooCommerce Extra Product Options which I absolutely LOVE and highly recommend for the price.

Excellent support as well.

Yes, I did.

With all the other changes in the editor to adapt to, this seems like overkill. Setting a red flag or changing background color to red or whatever is sufficient to let the author know there’s a coding issue, but blocking from saving is an over-reach in my opinion.

That missing quote doesn’t hurt a thing, but I lost 20 minutes of work time because I couldn’t see it.

I think this error is from the new “ads” the author is promoting on the “welcome page”. The Ad was probably removed –

Thank you for looking at this AskApache!
I had the same thought about the database the other day and after your post I downloaded a fresh copy and found/replaced 10,086 occurrences of https://www.mydomain with https://www.mydomain – you were right about that.

I didn’t want to take the site down so I made a new database and imported the edited version there, then updated my wp-config to reflect the change (I was afraid of serialized data corruption).

Unfortunately, it didn’t fix it and your header-test-tool still shows a 400 Bad Request error.

I had my hosting company look at the issue and this was their reply:

The online tools which you are using don’t appear to integrate with SNI and the following error is recorded when a test is initiated:

[Mon Feb 15 01:25:55 2016] [error] Hostname xx.xx.xx.xx (the IP addresss) provided via SNI and hostname wake-up.org provided via HTTP are different

Then, they offered no solution.

RESOLVED:

First I removed the redirect regex on lines 3 and 4 from my original post, then installed the “Really Simple SSL” plugin by Rogier Lankhorst.

Originally, this issue came about from many warnings in Bing Webmaster Tools. I discovered that I had added these sites to “My Sites” before I moved them over to HTTPS. I had to delete the sites from BWT and add them back again. It now shows that they’re being crawled correctly.

Another coder over at https://www.codementor.io showed me 2 other header checking sites that showed correct “HTTP/1.1 200 OK” responses. Those sites were: https://tools.seobook.com/server-header-checker/ and https://web-sniffer.net/

Be sure to check multiple sources if you have the same issue. Good luck!

Thanks for looking at the issue Dipak. However, if I remove the “force ssl” code (yours or mine) the response headers are perfect with no “Bad Request” error. That is a generic Apache error, and what is shown when a redirect loop is happening.

The “force ssl” code is only being added to FORCE the whole site to use ssl. I don’t want a duplicate content penalty for having both HTTP and HTTPS versions of the site. However, every snippet of regex I’ve tried either doesn’t redirect all traffic to HTTPS or results on a redirect loop.

Same result – HTTP/1.1 400 Bad Request.
Here are my “Response Headers”:

* Connected to www.wake-up.org (143.95.34.102) port 443 (#0)
> GET / HTTP/1.1
> Host: www.wake-up.org
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-US,en;q=0.5
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Accept-Encoding: gzip, deflate
> Connection: keep-alive
> Referer: https://www.askapache.com/online-tools/http-headers-tool/
> Cache-Control: max-age=0
> Keep-Alive: 115

< HTTP/1.1 302 Found
< Date: Tue, 09 Feb 2016 04:27:09 GMT
< Server: Apache
< Location: https://www.wake-up.org/
< Vary: Accept-Encoding
< Content-Encoding: gzip
< Content-Length: 186
< Keep-Alive: timeout=5, max=256
< Connection: Keep-Alive
< Content-Type: text/html; charset=iso-8859-1
--------------------------------------------------------------------------------

> GET / HTTP/1.1
> Host: www.wake-up.org
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-US,en;q=0.5
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Accept-Encoding: gzip, deflate
> Connection: keep-alive
> Referer: https://www.wake-up.org/
> Cache-Control: max-age=0
> Keep-Alive: 115

< HTTP/1.1 400 Bad Request
< Date: Tue, 09 Feb 2016 04:27:10 GMT
< Server: Apache
< Content-Length: 347
< Connection: close
< Content-Type: text/html; charset=iso-8859-1

Thanks for the fast reply and the link –

As time moves on, WordPress and all the available plugins and themes become more and more complex (meaning more conflicts). I don’t know anyone who can install and configure WordPress from scratch without significant experience, a hundred or more hours of reading, or professional support.

I personally support 20+ WordPress sites for clients, and 5 of my own, all on different hosts.

I don’t see how adding phpinfo(); and mysqli_get_server_info(); would add any significant overhead, or security issues.

It would be much smaller and far more useful than “Hello Dolly” …