jstallard

The CDN I’m trying to configure is Cloudfront. Cloudfront says:

Amazon Route 53 automatically creates a name server (NS) resource record set that has the same name as your hosted zone. It lists the four name servers that are the authoritative name servers for your hosted zone. Do not add, change, or delete name servers in this resource record set.

If I did that, all my clients’ domain mappings would break.

The only way I can see to get this to work is if I use the Cloudfront distribution name, duzjoog605274.cloudfront.net for my website, which would then appear in my URLs. I don’t want to do that!

This is what I did:
1 Added the following lines to .htaccess:

RewriteCond %{HTTP_HOST} ^(www\.)?webhive\.com\.au [NC]
RewriteRule ^wp-signup.php(.*)?$ https://webhive.com.au/$1 [R=301,L]

2 Put the following line in robots.txt:
Disallow: /wp-signup.php
3 Went into Google Search Console > Google Index > Remove URLs and asked Google to remove the URL (which I won’t insert here because Google might see it!)
4 Went to Crawl > Fetch as Google and asked Google to crawl https://webhive.com.au

Hopefully that’s sorted it!

• This reply was modified 7 years, 10 months ago by jstallard.

Thanks @lumberhack

But that seems to redirect all URLs on my website to the home page. Really need to do a plugin audit but I don’t have time to troubleshoot it now!

Hi Mike

Found the problem.

I can’t save the product price unless the product variation SKU field is filled in.

I tried the woocommerce-product-sku-generator plugin. That didn’t help.

It won’t work if the parent SKU is filled in and product variation SKU is blank. The product variation SKU must be set explicitly.

Thanks
Jackie

Hi Mike

Thanks for your reply

No javascript errors listed in console.

To begin with I had this error several times – WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403.

That stopped when I disabled Jetpack.

I shortened the attribute names and value. There are only 3 variations – ‘One Stacker, Two Stackers, Three Stackers’. Attribute name is ‘Please Choose’

Thanks
Jackie

Ok thanks Bet. Am wary of installing another big security plugin. Was hoping to get a find a multisite-compatible login captcha plugin. Will check it out though.

Thanks

Great! Thanks ??

Hi Dennis

I have a multisite network with clients on it. I want the default space quota to be 50MB. And I want to be able to change the space quota manually when needs be. I can do that on all blogs except the main blog.

Thanks
Jackie

Ok thanks Mika ??

Hi Mika

I just tried clearing browser caches and running CCleaner.

The dashboard CSS only loads if ‘define( ‘CONCATENATE_SCRIPTS’, false );’ is set in wp-config.php.

I think that rules out a browser caching issue?

The multisite hit no resource limits while I was testing this.

The dashboard CSS works with the CONCATENATE_SCRIPTS directive, that’s the main thing. Would like to know why it’s necessary though ??

Jackie

Ok panic over.

The Events Manager Events widget caused this problem. The blog widgets normalised as soon as I moved it to the blog’s Inactive Widgets area.

No don’t think so Mika. Tried clearing all the caches I could find – Firefox, WP Super Cache, Eaccelerator. Made no difference.

Initially, increasing system resources helped (am running CloudLinux). I commented out the CONCATENATE_SCRIPTS line and it was fine for a few weeks. Now the problem has just reoccurred. Yet the system hasn’t hit any of its resource limits. Am flummoxed! It’s Saturday evening in Australia. Could be a peak internet time but I don’t know how that could create this problem, unless it’s something to do with my Microsoft Azure server.

I’d leave the CONCATENATE_SCRIPTS line uncommented, but I assume scripts are concatenated to speed things up?

I found a fix in this post: Fix WordPress Admin Styles Not Loading

It’s weird but it works.

I added this to wp-config.php:
define( ‘CONCATENATE_SCRIPTS’, false );
And then the dashboard CSS came back.

Anyone know why I’d have to do this?

Thanks
Jackie

This was a permissions problem. My server support team fixed this. They said:

Many files were having 660 permissions but in suphp handler max permission allowed in 755 and that working permissions for folder (755) and for files (644). So I changed the files permissions to 644 and folders permissions to 755

Thanks Jeremy ??