Searching for posts or pages in the WordPress admin by default only includes titles and body content. If you want to search by custom fields in the WP Admin Edit Posts / Pages page then you can install this plugin or script.
I’ve been testing a massive migration from a proprietary CMS to WordPress (using my WordPress C# client). After about 20 different tests my post IDs in the WordPress MySQL database got out of control. I’d create 3,000 posts in one swoop and turn around and delete them while testing. This made my IDs something like 31,341 after day. This isn’t a huge deal but it’s annoying to me.
Note: If you already have created posts / pages and attached them to categories and then change the post id then they will no longer be related properly.
A quick google search will likely lead you to How to reset AUTO_INCREMENT in MySQL on Stackoverflow. However this won’t work if you are running on the InnoDB engine.
In my case I could just mass delete all the post with a SQL statement. If you have content and run the following commands bad stuff will happen.
I’d only use this if you don’t care about dropping all your posts!
While it’s not ideal (I prefer NGINX), sometimes you do need to run a WordPress site on a Windows Server running IIS. Here are a few common problems and solutions for running WordPress on IIS. I don’t go through a full installation tutorial – the famous 5 minute install should get you rolling same as if you were on another OS.
This post is to address three common issues you’ll run into after you install WordPress on IIS – 1) Permissions, 2) Updates, 3) Permalinks.
Note: These particular instructions & screenshots are from a Windows Server 2013 web server running IIS8. These instructions should work on most IIS sites and Azure VMs however may be in a different spot.
WordPress Permissions on IIS
A common problem after installing WordPress on IIS is file permissions. At first you won’t be able to upload pictures and then you will run into an issue changing the permalink structure or updating the wp-config file inside the dashboard. This due to file permissions and for the website to be able to write updates to itself on the server. This can be a rabbit hole fumbling around on permissions for every directory. While that may be fun for you, here’s a swift and simple way to globally update permissions in a safe manner on your WP site.
- Right click on your WordPress site in IIS “Sites” folder and select “Edit Permissions”
- Click “Security” tab
- Click “Edit” button to Edit Permissions for the site
- Click “Add…” button to add the user you want to grant permissions, in this case “Authenticated Users”
- Grant “Authenticated Users” Modify permissions
TL;DR – Grant “Authenticated Users” Modify permissions on your WordPress site in IIS
WordPress Updates on IIS
Now once you have your fancy WordPress install running on IIS and got your permissions applied so you can update the site … you’ll want to install a theme or plugin or run WordPress updates from inside the WordPress dashboard. Not so fast – you need to make a quick tweak on IIS to get WordPress updates and installs to work from the Dashboard.
- Go to the WordPress site’s Application Pool in IIS
- Right-click on the Application Pool and select “Advanced Settings”
- Scroll down under “Process Model” and select “Identity”. It will be set to “Application Pool Identity” by default and you want to change that
- Click on “Application Pool Identity” and select “Local System” as the Built-in account.
- Save and recycle the app pool
TL;DR – You need to run the WordPress site’s Application Pool under the LocalSystem Identity
WordPress Permalinks on IIS
WordPress makes a great CMS for many reasons and pretty SEO-friendly permalinks are one of the reasons. In the WordPress admin dashboard you can set your own URL permalink structure. This is cool. But it doesn’t work quite right running on IIS. You’ve already solved a couple initial problems you’d likely have tried which grants WordPress permissions to update the .htaccess file. Well guess what – IIS does not care about that file and your permalinks won’t work and you won’t be sure why. Well, now you will be. Anyway, you just need to drop a web.config file in the root of your WordPress site on IIS.
TL;DR – you need to setup a web.config file in the root of your WordPress site on IIS. The gist is available below.