Anytime xDebug examines PHP files, it will create log entries if its configuration specifies a log file location. I found that log entries were created when Valet was starting up but not when pages were loaded in the browser.
The remote_log and remote_log_level settings are commented-out with semicolons because my configuration is now working. A log level value of 10 will grow the log file to hundreds of megabytes in just a few hours of loading pages.
Do not try to prettify the ext-xdebug.ini file by putting spaces around the equals signs. My breakthrough to a working debugger occurred shortly after I removed spaces from ext-xdebug.ini, updated Valet, and restarted my computer.
Contents of VS .code-workspace file
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"name": "Listen for XDebug",
"name": "Launch currently open script",
The runtimeExecutable value points to the PHP executable installed by homebrew. The pathMappings value points to the place where this website lives on my computer.
Stop and restart the debugger in VS Code everytime you change the workspace file or the web server is restarted.
I got a new Macbook, and restored my old Intel processor back up to it. That means there are two versions of homebrew on my computer now, and I got into a situation where phpInfo() calls on web pages returned a different version of PHP than php -v in terminal. This fixed that, but I do not know why:
Migrate Specific Posts or Attachments With a Third WordPress Install
Duplicate the Site and Delete Posts That Won’t Move
The Built-in Tools > Export Feature Preserves Post IDs
An easy way to move WordPress content from one site to another is with the built-in XML import and export scripts located under the Tools menu. This tool does not allow users to export only specific posts, attachments, or other content. If you want Posts and Media, you get them all. Here is how I worked around this limitation to migrate 700 specific attachments among thousands.
Use a Third WordPress Install
I duplicated the site to a third, throwaway instance of WordPress using exfil, deleted the attachments I was not interested in (so only the attachments I wanted to move remained), and exported all Media with Tools > Export.
The Hard Part is Deleting All The Posts That Won’t Move
Deleting a few thousand attachments from WordPress is not fast using PHP. Like me, you might imagine writing a small loop with a call to wp_delete_attachment() inside. This is painful, and I do not recommend. (My local Laravel Valet development environment skid to a stop, and after many valet restart to rescue my local server, I decided to move on.)
I probably could have used a database query like DELETE FROM wp_posts WHERE ID NOT IN ( 32281, 32279, ... ), but I opted for the assistance of wp-cli, the WordPress Command Line Interface. This giant command to delete attachments by providing all of their IDs works great and finishes in under one minute:
The --force argument skips Trash and permanently deletes.
What Gave Birth to That Hideous Command
I wrote a bit of PHP to find the post IDs of attachments I wanted to migrate, and used the exclude argument in a get_posts() call to find the post IDs of all other attachments in the site. Then, I built the above wp-cli command in a string, and wrote it to a text file.
After deleting all the posts that should not be migrated, I was then ready to run Tools > Export for Media. The resulting XML file only contains attachments that remain after the massive deletion. The file also has URLs containing .test domains for my local environment, so I replaced those with the production domain. These URL changes mean the attachments will be pulled from the production site, not my local copy that’s only accessible from on my computer.
Provide the XML file to the WordPress importer at Tools > Import. Some servers will kill PHP processes that run longer than a specific amount of time. It’s OK to re-run the Import until it finishes. Because post IDs are preserved, no duplicate posts will result from running an XML import more than once.
I have written and released a bash script that extracts WordPress websites and updates their local copies in my computer. It’s called exfil, it’s free and open-source, and lives on Github at https://github.com/csalzano/exfil/.
I switched to Laravel Valet for local WordPress development on my Macbook in December 2019. I love it. I presented at January’s WordPress Lancaster meetup about how and why I made the move.
This week, I’ve written some code that protects uploads to the WordPress Media Library. (Did you know that anyone can view uploads if they find the URLs? The Media Library uses only security by obscurity.) To code my solution, I’m using an .htaccess file to protect a subfolder in wp-content/uploads.
There is No .htaccess in Nginx
.htaccess files do not work in Laravel Valet because it uses the nginx web server instead of Apache. (And, Valet does not use a reverse proxy to allow Apache features to work while running the faster nginx.) nginx does not allow its configuration to be changed on-the-fly, and that’s one reason it’s faster than Apache.
To replicate the protected folder mechanism, I learned how to block access to a directory inside an nginx configuration file, but that introduced a new challenge: Where is the nginx configuration file? Most resources will identify usr/local/etc/nginx/nginx.conf as the configuration file, and while that’s correct, changing it and restarting Valet did not change the behavior of the folder.
Nginx Config File Location for Laravel Valet
Each site you create inside Valet gets its own configuration file at this location: ~/.config/valet/Nginx/sitename.test This is the file you should edit.
Restart Valet to Allow Configuration Changes to be Loaded
Nginx needs to be restarted in order for configuration changes to take effect, and I found it easy to use this command inside Terminal: valet restart
I recently bought my first mechanical keyboard. The COVID-19 pandemic means I’m switching between my Macbook and a Windows machine throughout the week at the same desk, and while I was comfortable typing on the Macbook, this HP Spectre keyboard and I do not get along. The differences in shortcuts for copy and paste alone were causing me to make enough mistakes to know it was time to invest in a peripheral keyboard.
Alas, I’ve made the leap to a mechanical keyboard, a Durgod K320 in space grey with Cherry Silent Red switches (120$ shipped). Typically, I’m the kind of guy who buys whatever Wirecutter recommends, but their suggestions for mechanical keyboards are bad ones.
Features you Should Demand of a Mechanical Keyboard
the ability to remap any key
multiple profiles of key mappings
Wirecutter recommends the Varmilo VA87M and the Leopold FC750R. I couldn’t determine if these keyboards include software that makes it easy to remap keys while shopping. The Leopold’s keycaps don’t have legends for the multimedia controls of the function keys, so users will have to memorize the alternate roles of F5 through F12, print their own legend, or change the keycaps. I can’t support these accessibility shortcomings.
Durgod Zeus Engine Only Runs on Windows
The keyboard I bought has companion software to customize the key map and save multiple profiles. That software is called Durgod Zeus Engine, and it only runs on Windows. That might be a showstopper for some, but not I. The current version of Zeus Engine is 220.127.116.11, and it is much better easier to use compared to when I first bought this keyboard.
The changes I’ve made to make this keyboard macOS friendly are as follows:
Swap Left Ctrl and Left Windows keys (macOS’ command defaults to the Left Windows key instead of Alt, which is weird and why freedom to customize is important.)
As of this writing, it is not possible to delete a meta value using the WordPress REST API. Post meta updates must be communicated while inserting and updating post objects, and the only way to “remove” meta fields is to write blank values over their current values.
I wrote a free and open-source plugin to provide granular control over post and term meta fields. It lives on Github. The plugin is called Manipulate Meta with the WP API, and it extends the REST API to allow one request to retrieve, update, or delete a meta field independently from a post or term object.
The instructions are located in the repo’s README.md.
Are you getting this error from Azure SQL Server? Login failed on ServerName.database.windows.net.DatabaseName Please verify that the shards are accessible and that the credential information affiliated with external data source ExternalDataSourceName is correct.
When I ran into this error while migrating a SQL Server instance to Azure and designing External Tables, it was because the user I specified as the IDENTITY during DATABASE SCOPED CREDENTIAL creation had a different password that the LOGIN of the same name in the Master database.
Say we create a user in the Master database like this:
CREATE LOGIN ExternalTableAdministrator WITH PASSWORD = '[email protected][I7L$~5j5UL';
Later, when creating a database-scoped credential (and specifying this user as the identity), make sure to use the same password:
CREATE DATABASE SCOPED CREDENTIAL [ExternalTableCred]
WITH IDENTITY = 'ExternalTableAdministrator',
SECRET = 'Nr[email protected][I7L$~5j5UL';
This post was written the first day I encountered this error on Azure SQL Server because I could not find any web page that contained this error message.
If you’re getting the error, Computed columns are not supported with external tables for sharded data. while trying to create External Tables, remove the computed column definitions. Treat computed columns like normal columns and provide a data type. Read this: https://stackoverflow.com/a/43382300/338432
This week, I’m altering functions and stored procedures in a SQL Server 2008 database so that it can be migrated to Azure. The Data Migration Assistant does a great job of generating reports identifying MigrationBlockers, but one type of error was vague enough to confuse me for a few minutes. Here’s an example of that error:
"Title": "One or more objects contain statements that are not supported in Azure SQL Database ",
"Impact": "While assessing the schema on the source database, one or more syntax issues were found. Syntax issues on the source database indicate that some objects contain syntax that is unsupported in Azure SQL Database.",
"ImpactDetail": "Function: [dbo].[GalleryXML] contains a statement that is not supported on Microsoft Azure SQL Database v12. The specific error is: Incorrect syntax near AS.",
"Recommendation": "Note that some of these syntax issues may be reported in more detail as separate issues in this assessment. Review the list of objects and issues reported, fix the syntax errors, and re-run assessment before migrating this database.",
The error text, “Incorrect syntax near AS,” was just not a strong clue as to what was wrong with this function. The purpose of the function is to create structured XML that can be de-serialized into an instance of an object in C#. I use PATH Mode to accomplish this, and it is one of my favorite maneuvers when operating in SQL Server/.Net. Here is an abbreviated version of the query to help you understand the required changes to continue using this method in an Azure database:
--Subquery for photos
WHERE GalleryID = GalleryTbl.ID
FOR XML PATH('GalleryPhoto'), TYPE
) AS Photos
WHERE GalleryTbl.ID = @ID
FOR XML PATH('Gallery'), TYPE
The syntax that Azure doesn’t support is “AS Photos.” Here is the solution:
--Subquery for photos
WHERE GalleryID = GalleryTbl.ID
FOR XML PATH('GalleryPhoto'), root ('Photos'), TYPE
WHERE GalleryTbl.ID = @ID
FOR XML PATH('Gallery'), TYPE