Lets imagine you have a 27 Mb database file to upload to your server, such as you might using WP Rewriter in the event that you find yourself uploading a large thesaurus to your server for rewriting your auto-posts.
This large file size would most likely exceed your server settings limitations. If you have a VPS or Dedicated server you can edit your php.ini file, usually located at:
and change line:
…from 2MB to something much larger (ie., 100MB)
You may also have success editing your .htaccess file in your hosting account’s public_html directory by adding the following lines:
php_value upload_max_filesize 100M
php_value post_max_size 100M
The downside to this solution is that it would be necessary to duplicate these same steps for every hosting account individually that you want to use WP Rewriter on.
Alternatively, by editing your php.ini once, that change would be a server wide fix that would cover all sites on your server.
I am Setting up WP Rewriter But Can’t Figure All The File Size Mumbo Jumbo Server Stuff. What Can I Do?
If you don’t have access to your php.ini file or htaccess or just can’t figure it out , there are other thesaurus you can use that are smaller in size but, don’t think of this as a limitation…
If you email me, I can provide you with a handmade thesaurus that will be a great starting place for you. Or, you can find a smaller thesaurus that is 2MB in size or less.
Its up to you to use whichever approach you like best. Larger is not better. Its about quality.
In the past I have mentioned that its all about the quality of your thesaurus database. By quality, I mean, its rarely ideal to swap the word “fast” with “allegreto” even though many thesaurus’ would include that as a synonym.
That means if you want a “higher quality” database in the sense that I’m referring to, you may want to consider deleting words from your database that don’t sound as good in your posts.
But, That’s a LOT of Work!
That’s why some people prefer to start with a small handmade database and work their way up by adding common words to their database.
This typically results in very good results, ie., all swapped words sound quite good in the final post. Others figure as long as they’re cloaking traffic anyway, who really cares about quality? Just swap words out like mad!
Its up to you to decide which school of thought you fall under.
Using a Handmade Approach…
If you do use the handmade approach, I would consider adding several hundred common words and keep in mind that you can add MORE than one word variation per line.
As a last resort, using just a portion of a large thesaurus database (all A’s, for example — but, any random section will do).
The key to successfully rewriting blog posts using WP Rewriter is to rewrite a portion of the content, not ALL of it.
If you have a large database with WP Rewriter settings set to replace 100%, you’d essentially be rewriting all of your text which would likely result in poor quality or largely unreadable posts.
In that case, it may be a better idea to scale rewriter settings back until the rewritten posts still sound pretty good yet the overall article is no longer duplicate.
With a huge database, that might mean rewriting 1% of the post. With a small, handmade database that might mean rewriting 100% of the post.
What database you use is up to you. One thing you can rely on though is that WP Rewriter will do its job by taking any database (based on your server settings) and follow your instructions for rewriting posts.
In the end, you will get outstanding results that will likely loosely parallel the quality of effort you put into customizing your thesaurus database.
What About a Shared Custom Thesaurus For All WP Rewriter Users?
While this would be easy enough to do, I’m more concerned about the wrong people getting their hands on our shared database and implementing counter measures to prevent us from gaining an advantage in the Search Engines. This would create a pretty large footprint.
For now, I think it is better for each person to customize their own database or just use a larger database and take advantage of the random functioning builit-in to WP Rewriter to get unique results each time by setting your custom rewrite frequency to 1% or 3% or whatever you like.
Either of these solutions will work well.