murokoma

marking as resolved.

awesome! Thanks ??

awesome! Thanks ??

Hi Pawel,

I followed the standard procedure of deactivating all themes and plugins and re-activating them.

Turns out an incompatibility with “Shortcodes Ultimate” caused the issue.

After deactivating SU, it’s working now, except for one issue – but I’ll open another ticket for that.

Cheers,
Rob

Hello Pawel,

I tried IE (9) and FF (latest), both don’t work.
I don’t see any errors in the console, no.

If I can provide you with anything ellse that could help (admin access etc.) please let me know!

Thanks for your help Pawel!
Rob

does not work for me, either

I got the same problem.

Hi Tyler,

thanks, great support here ??

It’s not the 75 issue; also, none of the fixes in 69 do the trick.

The broken page is here:
https://www.robkonrad.com/the-50-most-downloaded-wordpress-plugins/

and here’s a screenshot how it looks (broken):
https://screencast.com/t/3kaSHrjYk

Thanks
Rob

Thanks for the info!

What do you use to re-encode them?

Thanks, Rob

Same problem here!

Two months ago, that would have been helpful.

I am now with another service.

SEOhosting.com, which is the “seo specialised” branch of hostgator.

Hi Andrea,

as I have the exact same issue, I’ve checked with my hosting company, here’s the answer I got:

Hello,

DNS has nothing to do with anything in your browser other than what it resolves to. The www CNAME already exists and is configured correctly.

$dig -t CNAME https://www.onlinemarketinghome.com

;; QUESTION SECTION:
;www.onlinemarketinghome.com. IN CNAME

;; ANSWER SECTION:
https://www.onlinemarketinghome.com. 14387 IN CNAME onlinemarketinghome.com.

;; ADDITIONAL SECTION:
onlinemarketinghome.com. 14387 IN A 69.41.236.43

It is possible to create a CNAME for each subdomain/site created. The record would look like the following:

https://www.subdomain in CNAME onlinemarketinghome.com.

The above will not force anything to load and would be redundant because if it weren’t created it would still work because of the www CNAME configured as shown above is pointing to the same place along with the wild card subdomains that should be configured.

Unfortunately to accomplish this you will need a complex rewrite rule which may conflict with WordPress itself and possibly cause an infinite redirect loop. The coding is not something we can support.

Any other ideas? Thank you very much,
Robert

Hi there,

I tried removing the additional lines from config.php and resetting .htaccess.

While the blog seems to be working okay, when I login as admin pretty much everything is gone – I can login and logout, but that’s pretty much it.

Did this happen to anyone who tried this as well?

Ugh…. obviously, I didn’t RTFM (is there any??) ??

My apologizes and thanks for the help!
R.