The Bad News: The core open source base of Wordpress does make quite a few assumptions about being run on a single server (wp-content, user uploads and media library to name a few)
The Good News: Pretty much all cloud providers (including Azure) have abstractions that allow you to work around these design limitations.
Fundamentally, you'll be addressing ...
This has unknowingly came to my attention as it slipped my mind, PHP 5.4 have already reach EOL and the last security support was stopped on the 14th of September 2015.
According to official documentation, PHP 5.5 will finally reach its EOL on the 10 of July 2016 (Active support has already been stopped but this version will still get ...
Re-install a new copy of wordpress and then put in the credentials to your database in the new install.
If you install wordpress and try to load the domain with no database attached, it will start the site creation wizard. Just enter the correct database credentials (username, database name, password, and location) and it will load for you instead of ...
There's a pretty good step by step on moving WordPress in the Codex. It is what I follow when changing domains.
Moving the files is pretty straight-forward. It is the hard-coded references in the database that are tricky. However, serialized search and replace will take care of all database changes. I've used the Velvet Blues plugin in the past, but ...
I'm probably overcomplicating things.
Right now, you are.
As I have no traffic as of now I don't really need to do this, but
.... I don't know what to choose as I don't
understand what these services really do, other than it's supposed to
be "better" to host externally...
Then why bother with a CDN right now and all of the image hosting options ...
You should not need the .git directory but I would not delete it.
It contains the version control for your site, and is thus an incredibly valuable resource should you need a developer to fix or upgrade your site in the future.
It also shows you a full history of the development of your site. This will save future developers time, and anything that saves ...
While this might be not the easiest task for a beginner, it is very well possible – with a little help from some plugins.
In a similar scenario I would usually install WordPress under a subdomain. When everything is looking ok to launch, I would recommend to first (always!) make a backup of everything. You can then change the base url (domain) either ...
I utilize the awesome plugin Duplicator to complete this exact procedure on a regular basis.
The plugin is fully supported and there are great FAQ available here:
The plugin will create a .zip backup of both your database and files and an installer .php that you ...
Wordpress can be a resource hog if you don't use caching. W3 Total Cache could help you a lot with MySQL, Object and Page Caching. You should also install PHP-APC and use it with the plugin. It can do wonders.
WordPress is very clearly engineered for being placed into web-accessible folder.
While attempt to move it from web folder could be made, it would be very challenging, especially for admin area which uses direct non-routed URLs to PHP files.
To run WordPress we recommend your host supports:
PHP version 5.6 or greater
MySQL version 5.5 or greater
Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security ...
Assuming your domain is mydomain.org. Instead of installing WordPress under a different domain (wordpress.mydomain.org) you could install WordPress on your local machine (using XAMPP MAMP or a virtual box) and resolving the original domain to your local computer by editing your systems host file and add the following line:
You basically have two options:
Use any of the available File Manager plugins for WordPress. Just Google them, literally that phrase I just used.
Implement a custom PHP code in your theme or custom plugin which will utilize any of the PHP functions for manipulating the files. For example, check these:
file_get_contents() - For reading files
You will have a few things to consider (later on the answer), I suggest the following steps:
Backup your Files and Database
This is pretty self-explanatory. You are going to do a lot of Data Manipulation, so be sure your original is safe.
Transfer your files
The fastest way to do this is to have a hoster where you can import directories from another server. ...
From a quick look at wpengines headers it looks like there may be some info you can check.
Your best bet is to get access to an account and dump out $_SERVER to see what's in there. For example it looks like $_SERVER['SERVER_NAME'] = 'WP Engine/4.0'. or perhaps $_SERVER['HTTP_HOST'].
As per the comments below it also seems the wp-config.php on wpengine ...
You need to update the new URL in the WordPress Address (URL) and Site Address (URL) in General settings. Some of your media may be pointing your old site or may not be available in that case you need to install a plugin named Search and Replace and you need to replace the every occurrence of the old URL with the new one.
All the answers here don't take into account an actual, functioning Wordpress environment, but use arguments about end-of-life/support (that is, age). Who cares? What one really wants is stability and functionality. Therefore, one should use the latest version that an entire Wordpress system (with desired themes and plugins) will support. Latest because PHP ...
WordPress will run on a toaster these days, it really doesn't have high requirements. Just make sure it's a Linux server, any comapny worth anything will have PHP and mySQL up to date enough for WordPress.
What your're going to have to struggle with is different companies offering different packages and then not being fully honest. A mid range package on ...
Anchor will setup apache or nginx for me - but which should I choose?!
Based on your concerns, I'd recommend Nginx -> Apache stack.
Please let me explain. By default, Nginx can only process static content, such as images, CSS and JS files. Nginx passes PHP requests to PHP-FPM or to other servers such as Apache. Nginx can still cache dynamic content via ...
If you are not moving to a different domain name, the file path shouldn't really matter.
Try these first:
Made a copy of your original backup bd
Open the new copy and search/replace example.com/ to example.com/blog/
This should get you going no matter what server setup you have.
If it doesn't, and you already have a fresh install on the right place, ...
Backups: Sounds like you need two types. 1. Versioning (eg use Git or SVN) and 2. Failsafe backup - some good plugins for this, or use a cron job to backup the WP files and database
Sounds like there's two needs here as well. 1. An environment to easily scale WP and 2. A host that you can easily scale with. Personally I use WordPress in multisite mode with ...
Short answer: No, WordPress doesn't care about pastebin in particular and doesn't do any sort of filtering like you're describing.
Long answer: Your host is doing it.
Step 1: Ask your host if they have mod_security enabled and what their filtering rules are.
Step 2: Try pasting the same link via a comment or something. If it's being blocked on any POST ...
What you are looking for is called "CDN" or "Content Delivery Network".
Here is a WIKI! definition if you are not familiar.
There are plenty of good tutorials out there that will show you how to carry this out using Wordpress.
Here is one you can have a look at.
You can follow the Wordpress docs and leave Wordpress in a directory but have it appear to be in root. See http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install
This will correctly change the location in the database. This might be the best way to go if the host requires Wordpress to be in a subfolder for ...
The same WordPress Codex has a page for backing up your database with phpmyadmin; see http://codex.wordpress.org/Backing_Up_Your_Database
You must export and import the database itself - and not do a posts export from the dashboard - to retain all settings, image URLs, etc.
Either use phpmyadmin in your host control panel, or you can use it as a plugin ...
Really good question, I have not actually tested this out yet, however in the past, with the way Python and even Java work, they were able to really deliver superior performance because they able to split the application's processing and memory needs across their cluster. This came with some limitations of not being able to use every library out there, ...
I highly recommend Amazon AWS. You can continue to use WP Super Cache with Amazon S3 (for storage of your static files such as images etc).
For high traffic scenarios, you can set up auto scaling rules of EC2 server instances to set up new servers as needed (and cut them when not needed).
This is the best tute I've found on installing WP on EC2:
I am assuming that you have both the Linux site and the (old) Windows site using the same database, and I am also assuming that the Linux server is operating currently on a numeric IP only until the migration. If that is the case, you do not want to alter the database at all-- not until you are ready for a proper migration. To test the Linux server using the ...