WooCommerce defaults to a 48 hour expiration time for all user’s carts. After this time, a user’s cart is deleted and the user will have to restock their basket with the same items before continuing to shop.
The default expiry time can be changed by using the wc_session_expiring and wc_session_expiration filters in your site’s functions.php. This is fine if your expiry time is at 12 hour intervals as the WordPress cron system only runs the session clean up twice daily and you also have to consider if you really want to hardcode cart expiry in your website’s code?
There is a plugin that takes care of all of these problems
Gives you control of the cart expiration time directly from the WooCommerce system settings page
It changes the WooCommerce session clean up to an hourly period to allow cart expiration times of greater or less than 12 hour intervals
It is fully supported on multisite installations of WordPress and WooCommerce
WP Migrate is a great tool well worth the slightly steep investment. The time and effort saved from a one click deployment huge. WP Migrate CLI takes this to another level with the ability to push an entire deployment from the command line.
If you’re running MAMP locally wp-cli may be using a different version of PHP than MAMP resulting in DB errors such as
Angulartics2 is a great package for vendor agnostic tracking in Angular apps. When using the package with Google Analytics, page view tracking is wired up automatically using the Angular routing module.
The angulartics2 documentation does not include information on how to send page views using the module however it is pretty simple to do, just inject the Angulartics2 and Angular common Location modules into your module’s constructor like so:
import { Angulartics2 } from 'angulartics2';
import {Location} from '@angular/common';
constructor(
private location: Location,
public angulartics2: Angulartics2,
)
and you can now track page views manually using the following method:
When attempting to run any of my VMWare Fusion virtual machines on mac macOS (OS X) I was getting the “/dev/vmmon not found, display cannot be initialized, internal error” error every time I try and start a virtual machine.
I tried reinstalling, upgrading and downgrading VMWare Fusion all to no avail.
The Fix for the dev/vmmon not found error
The problem is caused by having both VirtualBox and VMWare fusion installed on the same machine. Run the Sun provided uninstallation script, mirrored here to uninstall VirtualBox. This allows you to run your VMWare Fusion Virtual Machines without the “/dev/vmmon not found…” error.
Reinstalling VirtualBox after this install doesn’t seem to cause this error again, though a reboot might change things there in which case I will update this post.
In Ionic 2, the selection and thus copying of text is disabled by default. Enabling selecting and copying of content inside an Ionic 2 app is pretty simple. Here’s how
Now you can add the “selectable” class to individual elements in the app or to ionic elements using the ngClass attribute. This will allow your users to select and copy text from within your Ionic 2 app ?
As far as I am aware Ionic 2 does not yet have any decent logging options. But as Ionic 2 uses AngularJS 2, we can make use of the angular2-logger module
Angular2-logger is a Log4j inspired logger for Angular 2 apps allowing you to set your desired log level (OFF, WARN, ERROR, LOG, DEBUG etc)
I’ve found it best to implement the angular2-logger as a provider in Ionic 2 apps and inject it into your classes rather than instantiating a new instance of the logger for each component in your app.
Once you have the npm module installed, create a LoggerService provider in your app with the following ionic command:
ionic g provider LoggerService
then add the following code to the generated logger-service.ts file
I’m working on a project that will be using WordPress’s REST API to feed JSON data to a mobile app. We only want authenticated users to be able to query the REST API.
Out of the box, the REST API exposes all public content by GET request without any authentication requirements.
We’re using Enrique Chavez‘s JWT Authentication for WP REST API to allow us to authenticate users and get an authentication token. We have made a modification to the JWT auth plugin to expose the “validate_token” method by adding the following code to line 143 of the class-jwt-auth.php file.
This gives us access to the validate_token method elsewhere in WordPress.
We then hook into the REST API’s “rest_pre_dispatch” hook to require the presence of a valid token before exposing any API data with this custom filter in our theme’s functions.php file.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.I understand
