Craig

When I added:

php_value memory_limit 256M

to the .htaccess file my site went down with an internal error.

Removing the line brought my site back up.

CraigM

I have changed wp-config.php for this site:

From: define(‘WP_MEMORY_LIMIT’, ’64M’);
to: define(‘WP_MEMORY_LIMIT’, ‘128M’);

Still getting the error:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 64 bytes) in /home1/craigmc/public_html/BirdFeet.Net/wp-includes/wp-db.php on line 2255

CraigM

I set the PHP.ini in the root directory of my host assigned server.

I have multiple sites off the root. Do I need to edit a different PHP.ini?

CraigM

I finally got the memory limit to 512M
I then got this error:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /home1/craigmc/public_html/BirdFeet.Net/wp-includes/wp-db.php on line 2255

What needs to be adjusted now, Please?

CraigM

max_execution_time = 30
max_input_time = 60
memory_limit = 256M

My PHP.ini file is already set to 256M. It has been that way for about a year. When I try to increase it to 512MB it resets itself to 256MB.

Is there another file I need to edit?

Thanks, CraigM

Warning: Illegal string offset ‘handler’ in /home1/craigmc/public_html/BirdFeet.Net/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.gtld.php on line 57
Whois Server Version 2.0

This error occurs when the prefix “www.” or “https://” is used on the WHOIS function.

I just figured this one out. I cannot be the only person seeing this behavior.

Perhaps checking the “Enter IP Address or Domain Name:” string to strip off those characters, if found, would eliminate this learning curve for others.

Thanks, CraigM

Warning: Illegal string offset ‘handler’ in /home1/craigmc/public_html/BirdFeet.Net/wp-content/plugins/all-in-one-wp-security-and-firewall/lib/whois/whois.gtld.php on line 57
Whois Server Version 2.0

This is the error I get when I use the WHOIS function. I have tried it on multiple domains including https://www.cnn.com.

Do I need to make some addjustment to get this corrected?

Thanks, CraigM

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /home1/craigmc/public_html/BirdFeet.Net/wp-includes/wp-db.php on line 2255

This error occurs when I attempt to back up the database from the WP Security -> General Settings page.

I have opened a ticket with Hostgator, my web hosting provider.

Was this action correct or do I need to change something else?

Thanks, CraigM

My comment above is NOT correct.

I just did another search using only a portion of the SKU and both Variable and Simple Products were returned.

I am Sorry, my error!

Your Plugin is working correctly!

CraigM

Here is an oldy but a goodie!

When you convert a Simple Product to a Variable Product…the Simple Products Shipping information is not cleared out. So you enter the shipping weight and sizes in the Variations and the Simple Products old Shipping information remains….Overriding the Variations Shipping Information?

It gets better!

When you move an item into the trash, you are sent to the first page of products.

If you are working on say page 15 of 20 that you have sorted by sku and you send an item to the trash…you get sent back to the first page of Products. You must sort by sku again and then move back to page 15.

2.4.2 is a very poor implementation, clearly not an upgrade.

The Remove Attribute Button is not visible until you move the mouse over it.

Very confusing as I am forced to guess where the hidden link is and move the mouse around to find it.

Just a REALLY bad programming choice. New users would be lost and tempted to use mySQL to edit Attributes where a visible link would work fine.

This has been resolved in Woocommerce 2.4.2 which was just released.

My Variable Products are now correct in both the front and back ends.

Craig

Don’t ask but now the Product Variations are showing up on the customer side. The Backend still shows “Any Size” for all Item Numbers.