Wordpress expert.
1960 stories
·
0 followers

Switch Laravel Valet from .dev to .test in three easy steps

1 Share

Chrome and Safari began forcing https for the .dev domain because someone apparently thought it was a good idea to register as a public TLD. Laravel Valet only produces self-signed SSL certificates though, so I want to keep my local installations served as http. Guess it's time to switch TLDs!

Oh, and don't try to use .local on a Mac because it conflicts with Bonjour local networking. I discovered this with 30 minutes of wasted effort. .test is the way to go.

First, run:

valet domain test

Switch Valet to using the .test domain, which will also update dnsmasq accordingly. Don't try to edit dnsmasq configuration on your own — there are too many ways to go wrong.

Second, run:

wp package install wp-cli/find-command

Install wp-cli/find-command to find all WordPress installs in your Laravel project directory. It's convenient for running one WP-CLI command against all WordPress installs.

Third, run:

wp find ~/projects --field=wp_path | xargs -I % wp --path=% search-replace '.dev' '.test' --all-tables

Run wp search-replace against all WordPress installs to replace instances of '.dev' with '.test'. ~/projects is my Valet project directory, and --all-tables ensures the procedure is run against all database tables.

Et voila! You've switched Laravel Valet from .dev to .test in three easy steps.

The post Switch Laravel Valet from .dev to .test in three easy steps appeared first on Daniel Bachhuber.

Read the whole story
Share this story
Delete

WordPress 4.9.4 Fixes Critical Auto Update Bug in 4.9.3

1 Share

Hours after WordPress 4.9.3 was released, the WordPress development team followed it up with 4.9.4 to fix a critical bug with the auto update process. The bug generates a fatal PHP error when WordPress attempts to update itself.

This error requires WordPress site owners and administrators to manually update to WordPress 4.9.4 by visiting your Dashboard and clicking the Update Now button on the Updates page. Alternatively, you can update by uploading the files via SFTP or by using WP-CLI.

Dion Hulse, WordPress lead developer, says managed hosts that apply updates automatically for their customers will be able to update sites as they normally do. This may explain why some users have reported that sites running 4.9.3 have automatically updated to 4.9.4 without issue.

The bug stems from an attempt to reduce the number of API calls made when the auto update cron job is run. Unfortunately, the code committed had unintended consequences. “It triggers a fatal error as not all of the dependencies of find_core_auto_update() are met,” Hulse said.

A postmortem will be published once the team determines how to prevent this mistake from happening in the future. “We don’t like bugs in WordPress any more than you do, and we’ll be taking steps to both increase automated coverage of our updates and improve tools to aid in the detection of similar bugs before they become an issue in the future,” Hulse said.

While WordPress 4.9.3 and 4.9.4 do not include any security fixes, it’s important to note that in order to receive automatic security updates in the future, sites using the 4.9 branch must be running at least 4.9.4. Older branches are unaffected.

Read the whole story
Share this story
Delete

WordPress 4.9.3 Released, Fixes 34 Bugs

1 Share

WordPress 4.9.3 is available and fixes 34 bugs. Customizer changesets, the visual editor, widgets, and compatibility for PHP 7.2 highlight this release. You can view all of the changes via the changelog or trac tickets. Most sites will update automatically. However, if you want to trigger the update ahead of time or manually update, visit your Dashboard, click the Updates link, and click Update Now.

Read the whole story
Share this story
Delete

WordPress 4.9.3 Maintenance Release

1 Share

WordPress 4.9.3 is now available.

This maintenance release fixes 34 bugs in 4.9, including fixes for Customizer changesets, widgets, visual editor, and PHP 7.2 compatibility. For a full list of changes, consult the list of tickets and the changelog.

Download WordPress 4.9.3 or visit Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.

Thank you to everyone who contributed to WordPress 4.9.3:

Aaron Jorbin, abdullahramzan, Adam Silverstein, Andrea Fercia, andreiglingeanu, Andrew Ozz, Brandon Payton, Chetan Prajapati, coleh, Darko A7, David Cramer, David Herrera, Dion Hulse, Felix Arntz, Frank Klein, Gary Pendergast, Jb Audras, Jeffrey Paul, lizkarkoski, Marius L. J., mattyrob, Monika Rao, munyagu, ndavison, Nick Momrik, Peter Wilson, Rachel Baker, rishishah, Ryan Paul, Sami Ahmed Siddiqui, Sayed Taqui, Sean Hayes, Sergey Biryukov, Shawn Hooper, Stephen Edgar, Sultan Nasir Uddin, tigertech, and Weston Ruter.

Read the whole story
Share this story
Delete

How To Make Software

1 Share
  1. Use what you have to build something useful
  2. Gather feedback and gradually improve upon it

How Not To Make Software

  1. Spend a year documenting and designing
  2. Document and design your process of documenting and designing
  3. Spend another year trying to come up with pitches and press releases
  4. Start over 23 times
  5. Attempt to use new technology in every aspect of the application
  6. Spend a year in development before showing anybody
  7. Recruit a CFO
  8. Plan a launch party
  9. Launch only to weak response
  10. Find rudimentary bugs
  11. Scrap everything and get started on V2
Read the whole story
Share this story
Delete

WooCommerce 3.3 Removed From Plugin Directory Due to Theme Conflicts

1 Share

Earlier this week, WooCommerce 3.3 was released and among the features was increased theme compatibility. However, soon after release, users of third-party themes reported issues with categories displaying improperly.

Despite it being a minor release that should be fully backwards compatible with previous releases up to 3.0, WooCommerce has removed 3.3 from the plugin directory and replaced it with 3.2.6.

According to a post on the project’s official blog, WooCommerce 3.3.1 will take the place of 3.3 and will include a fix for the category display issue.

The issue affected themes with template overrides from 3.2.x which hadn’t been made compatible with 3.3. In general, we recommend that themes use hooks instead of template overrides. Themes such as Storefront (which does not use template overrides) were compatible at launch.

WooCommerce Blog

If you’ve already updated to WooCommerce 3.3 and your theme is compatible, you don’t need to make any changes. If your theme is not compatible, WooCommerce recommends checking with your theme’s author to see if a compatibility fix has been released.

Users can also wait for the release of 3.3.1, update to the pre-release version of 3.3.1, or use the WP-Rollback plugin and revert back to 3.2.6. WooCommerce developers suggest only going the WP-Rollback route if you’re not comfortable installing pre-release software.

Coen Jacobs, a former member of the WooCommerce development team, commented on Twitter that this was the first time he can remember that a release was reverted.

The development team has tested 3.3.1 with more than 40 different themes and believe it is stable. However, they are exercising caution and thoroughly testing the fixes with more themes. Users can expect to see 3.3.1 officially released the week of February 5th.

Read the whole story
Share this story
Delete
Next Page of Stories