mailworm

Hi Prajakti,
hey CyberChimps,

well, I just tried to update another page from Responsive 4.0.5 to (in the meantime) 4.2.4. The update progresses without any error. After calling the front page (or any other page) the screen is empty.

I followed the advice and copy-pasted the content on the home page and saved it. Now the content appears, but the full design is totally destroyed: The menu looks shit, the logo is gone, etc.

I am not using any deprecated page template, but simply the default template. I am of course using a child theme, but without any custom template copies, only with a custom functions.php and style.css. Both shall not be a reason for the logo being removed for example.

I will move the page to some other theme, because now that I obviously have to re-work the full site I will use another theme, which is more reliable.

We were told to be ready for some radical changes, when updating from Responsive 3.x to 4.x and it was really some work to do. Now I am surprised that obviously even more rework has to be done after this, without any notice and all the theme devs now suggest is to follow some half baked hint from another user.

• This reply was modified 4 years, 7 months ago by mailworm.
• This reply was modified 4 years, 7 months ago by mailworm.

Honestly? Is there no other way?

I mean, luckily the affected website has only like 7-8 pages. However, this manual workaround takes time.

How come, that first the big migration to 4.x requires lots of manual adjustments to existing design, etc. and then from 4.x to 4.2 the next manual steps are required!?

That’s kind of disappointing. Sorry to say.

@vanvox: Thanks, works like a charm. Suppose this to be fixed in with an update. Have a good day.

Great news! Thanks for Your fast interaction!

Here You are:

66.249.93.153 – – [08/Sep/2016:17:46:48 +0200] “GET / HTTP/1.1” 403 1439 “-” “M
ozilla/5.0 (compatible; Google-Site-Verification/1.0)”

Additionally although not blocked as per my settings the following RX 403s:

180.76.15.11 – – [09/Sep/2016:06:12:07 +0200] “GET / HTTP/1.1” 403 1402 “-” “Mo
zilla/5.0 (compatible; Baiduspider/2.0; +https://www.baidu.com/search/spider.htm
l)”

@frankmarion:

Did You get which tweeks in BWS are those interfering with Twitter Widget Pro?

@nbruley:

OK so at this time do NOT insert the a.m. code into Your .htaccess!!! It will result in a Serer 500 error (endless redirect www>none-www>www)!

Check WP preferences tab, first menu item there. Check whats noticed in site-url and wordpress-url.

I suppose, You

1) Have altered the whole WP SEO part of this post.
2) The link has been at least once liked on Facebook BEFORE that?

Use the Facebook URL Linter and go cleaning the Facebook URL cache. To fasten Likes & Shares, Facebook stores the meta-data of a page in their own system.

https://developers.facebook.com/tools/debug

@nbruley:

You should add the following to Your .htaccess in the next line to “Rewrite Base /” to avoid Google to index duplicate content (once via gospelriver.com and once via https://www.gospelriver.com):

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L]

Yes You can – I suppose.. Go in Backend to WP SEO, choose last menu item (Edit Files?) and add to the end of robots.txt:

Disallow /

You should wait to import the sitemap in GoogleWebmaster Tools until go live is done.

Do You have CHECKED “Ping Yahoo! & Ask.com”???

Uncheck, save settings & Your sitemap will be there. Seems to me like a bug.

This happend to me when I additionally checked the boxes to ping Yahoo! & Ask.com.

I unchecked them boxes, saved settings & my sitemap was back.

I just posted a solution:

This happens, for what reason ever, if You additionally check the boxes @ Yahoo! & Ask.com pinging.

Uncheck these boxes, save settings & Your sitemap will be 200!

@thethefly:

I’m sorry to say, but it still does not work in IE8 nor IE9 (via IETester). In IE7 it works, but calls 2 errors in the plugins js file as in the prototype.js.

Actually I am building my own slider. It uses the jQuery fadeIn, fadeOut plus addClass and removeClass. Last one shows up 1 error in IE7 or IE8 dont remember exactly, but it works and does not crash the Lightbox plugin, which I am using.

Please go ahead with fixing, while I am building my KISS-Slider.

Oh I see.. Well yes, I forgot about the error in Lightbox.js, which has nothing to do with the slider at all.

Made the experience conserning IETester myself yesterday. My PC at work has IE8 installed, but its a stripped down corporate version.

Well for now, it looks all good. Unfortunately they took down IPinfos Netrenderer, so I have to find someone else to test it for me.

Anyways thanks a lot for this interesting discussion! Alltough I lost almost one day on this tiny problem, I learned a lot and am scared about the IE8s behaviour. ??