So you might notice some apps or scripts are executing slowly, and if you have the time and inclination (and access to your cpanel via your host), you might want to increase the memory limit of your php.  Hayden James at haydenjames.io (not to be confused with Britney’s youngest son) has a really good explanation, which I am shamelessly using to help me pick the featured image for this post.  First, think of the memory limit like a speed limit on the road – if it’s higher, you can go faster.  And second, remember that the memory limit is per script, (php is not designed for multi-threading and the scripts will not share the memory limit setting) and that generally you don’t want inefficient scripts that need a lot of memory, you’d rather optimize your scripts and therefore your site.  But if you do want to increase the php memory limit, here are the steps.  And theoretically, things will run faster and better for you.

Remember, php is the language that runs a wordpress site in the background; html and css are what makes it look good on the front end.  So if you are improving the performance on the back end, your site should load faster.

There are some ways to approach this, like the wp-config.php file and your .htaccess file.  Here are a few tutorials:

• Fame Themes walks you through this and other ways to increase the memory limit for your wordpress site.  They rock.
• Rocket.me also has basically the same info, also helpful and clear.
• InMotion lists a few ways to get at the memory setting, too.
• Beaver Builder has some helpful info, as well as an explanation of why you need more memory allocated to php.

Or you can edit your php.ini file.

• a phpinfo.php page is very helpful – it’s a snapshot of your php environment on your server (version, stats, server info, configuration options, etc).   It will show your your php memory limit.  You can generate a phpinfo.php file, if you don’t have one, very simply with the steps here.  Don’t forget to delete the file when you’re done!  It’s a goldmine for hackers.  (another example, InMotion hosting also has their steps for generating a phpinfo.php file.  Basically the same.)
• Sometime you won’t have a php.ini file.  One way to generate one automagically is update your version of php (or even keep the same version number and just click update) in your php version.  You may have to click around for a few minutes or search via where your host put that.  But it will generate a php.ini file already populated.   (here’s a couple of links for bigger hosts
  • Bluehost
  • InMotion
  • GoDaddy you can go to php version and switch to php settings and up your memory limit there, but you are restricted to 512M I think.

Ever tried an update, often for a plugin, on your WordPress site and the “Briefly unavailable for maintenance” page is not brief?

I will spare you the uninteresting details of why you’re stuck, 50% because boring and 50% because don’t completely understand.  I am dumb but honest, like a large Newfoundland dog.  Per the nice people at WPBuffs, basically, you need to stop clicking the update button too fast if you didn’t spring for fast hosting.  And let’s just get right to fixing your problem!  You need to delete that .maintenance file.  Try going through your cpanel to your root or your public html folder and find that sucker, right click and delete.  If any of this sounds confusing, please call me or some other nerd and let us do it.  Then go back in time and do your updates on a staging site.  There’s so many times in life when we have to swing without a net, why would you chance your website you worked so hard on it when it’s so easy to test things first on an unsuspecting staging site?  It’s like if you had an identical twin you hated and your surgeon could practice all operations on him first before working on you, so everyone sees how it will turn out.

That’s kind of gruesome but you get the point.  Updates can and do sometimes go wrong and best to test things out first.  If you do get stuck during an update, don’t panic, just delete that pesky .maintenance file.  Good luck!

Here’s also the rundown on how to do this trick also from the nice folks at kinsta, with some additional helpful advice.

So generally, once you have a privacy policy (which so many of us don’t, but oughta), you just make it its own page and call it a day. But you need a way for your visitors to find it. There are considered to be two different methods – browsewrap and clickwrap. From the irrepressible folks at Dash Farrow:

Browse-wrap Agreements

A Browse-wrap agreement is one where the terms of an agreement are located on a website, but are often connected to the main web page of the product by a hyperlink to another web page that contains the contracts terms and conditions. Normally there is no affirmative manifestation of assent necessary to agree with the terms located on the linked web page. The customer must also affirmatively click the hyperlink to even access and become aware of the terms of the agreement.

Clickwrap Agreements

By contrast a Clickwrap Agreement is one where the website requires the customer or user to affirmatively review the terms of an agreement through a series of pop-up windows that ask for the customers to click a button showing that they agree to the conditions. Under a Clickwrap Agreement the website puts the terms of the agreement directly in front of the user and requires them to show that they affirmatively accept the terms by clicking a button.

They go on to say, by going the clickwrap way you are doing more to have your visitor or customer actively assent to your privacy policy for their information by forcing them to agree to it, and therefore are more in compliance with the law.

What that means is that you probably should have

• a separate page with your privacy policy on it
• link on your footer to that page (which would usually therefore be visible on every page of your site)
• a check box on any contact form or CTA pop-up form that is required before your visitor can submit the form (ie, they can’t give you their information until they’ve clicked the box saying they agree to your privacy policy and/or terms of use)

What are you doing for your site’s privacy policy?  How have you found the best way to handle this?  And…how soon do you think the GDPR will come to our shores?  I think 3 years.

There is of course lots of info on the GDPR on the internet, and filling up your inbox.  If you’re like me, you’re a little (see: a lot) intimidated by this new law.  It seems so serious!  And I’m not a criminal – I’m not that tricky!  But rest assured, it’s not actually meant to be that difficult or intimidating, especially if you are on the right side of things.

For most very simple brochure sites, or even smaller e-commerce sites, you need to update your privacy policy and terms of use (if, like me, you didn’t have one until today, that’s okay.  I won’t judge you.).  And you need to add two opt-in check boxes to your site, which for most folks is best done on their trusty old contact form.  Your visitors need to explicitly give you permission to use and keep their information.  Yes, I know they are filling out the contact form willingly, so you can, you know, contact them.  But ours is not to reason why, ours is to update and opt in or die.

So, first thing – here is a good place to get some boilerplate Privacy Policy stuff.  And…hold on while I get a privacy policy…