├── LICENSE
├── README.md
├── backup
├── converted
│ └── index.html
├── index.html
└── old
│ └── index.html
├── docs
├── index.html
├── style.css
└── wpmove.png
├── lang
└── wpmove.pot
├── libs
├── functions-database-backup.php
├── functions-file-backup.php
└── js
│ ├── jquery.jstree.js
│ └── themes
│ └── default
│ ├── d.png
│ ├── file.png
│ ├── style.css
│ └── throbber.gif
├── readme.txt
├── uninstall.php
└── wordpress-move.php
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 2, June 1991
3 |
4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
6 | Everyone is permitted to copy and distribute verbatim copies
7 | of this license document, but changing it is not allowed.
8 |
9 | Preamble
10 |
11 | The licenses for most software are designed to take away your
12 | freedom to share and change it. By contrast, the GNU General Public
13 | License is intended to guarantee your freedom to share and change free
14 | software--to make sure the software is free for all its users. This
15 | General Public License applies to most of the Free Software
16 | Foundation's software and to any other program whose authors commit to
17 | using it. (Some other Free Software Foundation software is covered by
18 | the GNU Lesser General Public License instead.) You can apply it to
19 | your programs, too.
20 |
21 | When we speak of free software, we are referring to freedom, not
22 | price. Our General Public Licenses are designed to make sure that you
23 | have the freedom to distribute copies of free software (and charge for
24 | this service if you wish), that you receive source code or can get it
25 | if you want it, that you can change the software or use pieces of it
26 | in new free programs; and that you know you can do these things.
27 |
28 | To protect your rights, we need to make restrictions that forbid
29 | anyone to deny you these rights or to ask you to surrender the rights.
30 | These restrictions translate to certain responsibilities for you if you
31 | distribute copies of the software, or if you modify it.
32 |
33 | For example, if you distribute copies of such a program, whether
34 | gratis or for a fee, you must give the recipients all the rights that
35 | you have. You must make sure that they, too, receive or can get the
36 | source code. And you must show them these terms so they know their
37 | rights.
38 |
39 | We protect your rights with two steps: (1) copyright the software, and
40 | (2) offer you this license which gives you legal permission to copy,
41 | distribute and/or modify the software.
42 |
43 | Also, for each author's protection and ours, we want to make certain
44 | that everyone understands that there is no warranty for this free
45 | software. If the software is modified by someone else and passed on, we
46 | want its recipients to know that what they have is not the original, so
47 | that any problems introduced by others will not reflect on the original
48 | authors' reputations.
49 |
50 | Finally, any free program is threatened constantly by software
51 | patents. We wish to avoid the danger that redistributors of a free
52 | program will individually obtain patent licenses, in effect making the
53 | program proprietary. To prevent this, we have made it clear that any
54 | patent must be licensed for everyone's free use or not licensed at all.
55 |
56 | The precise terms and conditions for copying, distribution and
57 | modification follow.
58 |
59 | GNU GENERAL PUBLIC LICENSE
60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
61 |
62 | 0. This License applies to any program or other work which contains
63 | a notice placed by the copyright holder saying it may be distributed
64 | under the terms of this General Public License. The "Program", below,
65 | refers to any such program or work, and a "work based on the Program"
66 | means either the Program or any derivative work under copyright law:
67 | that is to say, a work containing the Program or a portion of it,
68 | either verbatim or with modifications and/or translated into another
69 | language. (Hereinafter, translation is included without limitation in
70 | the term "modification".) Each licensee is addressed as "you".
71 |
72 | Activities other than copying, distribution and modification are not
73 | covered by this License; they are outside its scope. The act of
74 | running the Program is not restricted, and the output from the Program
75 | is covered only if its contents constitute a work based on the
76 | Program (independent of having been made by running the Program).
77 | Whether that is true depends on what the Program does.
78 |
79 | 1. You may copy and distribute verbatim copies of the Program's
80 | source code as you receive it, in any medium, provided that you
81 | conspicuously and appropriately publish on each copy an appropriate
82 | copyright notice and disclaimer of warranty; keep intact all the
83 | notices that refer to this License and to the absence of any warranty;
84 | and give any other recipients of the Program a copy of this License
85 | along with the Program.
86 |
87 | You may charge a fee for the physical act of transferring a copy, and
88 | you may at your option offer warranty protection in exchange for a fee.
89 |
90 | 2. You may modify your copy or copies of the Program or any portion
91 | of it, thus forming a work based on the Program, and copy and
92 | distribute such modifications or work under the terms of Section 1
93 | above, provided that you also meet all of these conditions:
94 |
95 | a) You must cause the modified files to carry prominent notices
96 | stating that you changed the files and the date of any change.
97 |
98 | b) You must cause any work that you distribute or publish, that in
99 | whole or in part contains or is derived from the Program or any
100 | part thereof, to be licensed as a whole at no charge to all third
101 | parties under the terms of this License.
102 |
103 | c) If the modified program normally reads commands interactively
104 | when run, you must cause it, when started running for such
105 | interactive use in the most ordinary way, to print or display an
106 | announcement including an appropriate copyright notice and a
107 | notice that there is no warranty (or else, saying that you provide
108 | a warranty) and that users may redistribute the program under
109 | these conditions, and telling the user how to view a copy of this
110 | License. (Exception: if the Program itself is interactive but
111 | does not normally print such an announcement, your work based on
112 | the Program is not required to print an announcement.)
113 |
114 | These requirements apply to the modified work as a whole. If
115 | identifiable sections of that work are not derived from the Program,
116 | and can be reasonably considered independent and separate works in
117 | themselves, then this License, and its terms, do not apply to those
118 | sections when you distribute them as separate works. But when you
119 | distribute the same sections as part of a whole which is a work based
120 | on the Program, the distribution of the whole must be on the terms of
121 | this License, whose permissions for other licensees extend to the
122 | entire whole, and thus to each and every part regardless of who wrote it.
123 |
124 | Thus, it is not the intent of this section to claim rights or contest
125 | your rights to work written entirely by you; rather, the intent is to
126 | exercise the right to control the distribution of derivative or
127 | collective works based on the Program.
128 |
129 | In addition, mere aggregation of another work not based on the Program
130 | with the Program (or with a work based on the Program) on a volume of
131 | a storage or distribution medium does not bring the other work under
132 | the scope of this License.
133 |
134 | 3. You may copy and distribute the Program (or a work based on it,
135 | under Section 2) in object code or executable form under the terms of
136 | Sections 1 and 2 above provided that you also do one of the following:
137 |
138 | a) Accompany it with the complete corresponding machine-readable
139 | source code, which must be distributed under the terms of Sections
140 | 1 and 2 above on a medium customarily used for software interchange; or,
141 |
142 | b) Accompany it with a written offer, valid for at least three
143 | years, to give any third party, for a charge no more than your
144 | cost of physically performing source distribution, a complete
145 | machine-readable copy of the corresponding source code, to be
146 | distributed under the terms of Sections 1 and 2 above on a medium
147 | customarily used for software interchange; or,
148 |
149 | c) Accompany it with the information you received as to the offer
150 | to distribute corresponding source code. (This alternative is
151 | allowed only for noncommercial distribution and only if you
152 | received the program in object code or executable form with such
153 | an offer, in accord with Subsection b above.)
154 |
155 | The source code for a work means the preferred form of the work for
156 | making modifications to it. For an executable work, complete source
157 | code means all the source code for all modules it contains, plus any
158 | associated interface definition files, plus the scripts used to
159 | control compilation and installation of the executable. However, as a
160 | special exception, the source code distributed need not include
161 | anything that is normally distributed (in either source or binary
162 | form) with the major components (compiler, kernel, and so on) of the
163 | operating system on which the executable runs, unless that component
164 | itself accompanies the executable.
165 |
166 | If distribution of executable or object code is made by offering
167 | access to copy from a designated place, then offering equivalent
168 | access to copy the source code from the same place counts as
169 | distribution of the source code, even though third parties are not
170 | compelled to copy the source along with the object code.
171 |
172 | 4. You may not copy, modify, sublicense, or distribute the Program
173 | except as expressly provided under this License. Any attempt
174 | otherwise to copy, modify, sublicense or distribute the Program is
175 | void, and will automatically terminate your rights under this License.
176 | However, parties who have received copies, or rights, from you under
177 | this License will not have their licenses terminated so long as such
178 | parties remain in full compliance.
179 |
180 | 5. You are not required to accept this License, since you have not
181 | signed it. However, nothing else grants you permission to modify or
182 | distribute the Program or its derivative works. These actions are
183 | prohibited by law if you do not accept this License. Therefore, by
184 | modifying or distributing the Program (or any work based on the
185 | Program), you indicate your acceptance of this License to do so, and
186 | all its terms and conditions for copying, distributing or modifying
187 | the Program or works based on it.
188 |
189 | 6. Each time you redistribute the Program (or any work based on the
190 | Program), the recipient automatically receives a license from the
191 | original licensor to copy, distribute or modify the Program subject to
192 | these terms and conditions. You may not impose any further
193 | restrictions on the recipients' exercise of the rights granted herein.
194 | You are not responsible for enforcing compliance by third parties to
195 | this License.
196 |
197 | 7. If, as a consequence of a court judgment or allegation of patent
198 | infringement or for any other reason (not limited to patent issues),
199 | conditions are imposed on you (whether by court order, agreement or
200 | otherwise) that contradict the conditions of this License, they do not
201 | excuse you from the conditions of this License. If you cannot
202 | distribute so as to satisfy simultaneously your obligations under this
203 | License and any other pertinent obligations, then as a consequence you
204 | may not distribute the Program at all. For example, if a patent
205 | license would not permit royalty-free redistribution of the Program by
206 | all those who receive copies directly or indirectly through you, then
207 | the only way you could satisfy both it and this License would be to
208 | refrain entirely from distribution of the Program.
209 |
210 | If any portion of this section is held invalid or unenforceable under
211 | any particular circumstance, the balance of the section is intended to
212 | apply and the section as a whole is intended to apply in other
213 | circumstances.
214 |
215 | It is not the purpose of this section to induce you to infringe any
216 | patents or other property right claims or to contest validity of any
217 | such claims; this section has the sole purpose of protecting the
218 | integrity of the free software distribution system, which is
219 | implemented by public license practices. Many people have made
220 | generous contributions to the wide range of software distributed
221 | through that system in reliance on consistent application of that
222 | system; it is up to the author/donor to decide if he or she is willing
223 | to distribute software through any other system and a licensee cannot
224 | impose that choice.
225 |
226 | This section is intended to make thoroughly clear what is believed to
227 | be a consequence of the rest of this License.
228 |
229 | 8. If the distribution and/or use of the Program is restricted in
230 | certain countries either by patents or by copyrighted interfaces, the
231 | original copyright holder who places the Program under this License
232 | may add an explicit geographical distribution limitation excluding
233 | those countries, so that distribution is permitted only in or among
234 | countries not thus excluded. In such case, this License incorporates
235 | the limitation as if written in the body of this License.
236 |
237 | 9. The Free Software Foundation may publish revised and/or new versions
238 | of the General Public License from time to time. Such new versions will
239 | be similar in spirit to the present version, but may differ in detail to
240 | address new problems or concerns.
241 |
242 | Each version is given a distinguishing version number. If the Program
243 | specifies a version number of this License which applies to it and "any
244 | later version", you have the option of following the terms and conditions
245 | either of that version or of any later version published by the Free
246 | Software Foundation. If the Program does not specify a version number of
247 | this License, you may choose any version ever published by the Free Software
248 | Foundation.
249 |
250 | 10. If you wish to incorporate parts of the Program into other free
251 | programs whose distribution conditions are different, write to the author
252 | to ask for permission. For software which is copyrighted by the Free
253 | Software Foundation, write to the Free Software Foundation; we sometimes
254 | make exceptions for this. Our decision will be guided by the two goals
255 | of preserving the free status of all derivatives of our free software and
256 | of promoting the sharing and reuse of software generally.
257 |
258 | NO WARRANTY
259 |
260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
268 | REPAIR OR CORRECTION.
269 |
270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
278 | POSSIBILITY OF SUCH DAMAGES.
279 |
280 | END OF TERMS AND CONDITIONS
281 |
282 | How to Apply These Terms to Your New Programs
283 |
284 | If you develop a new program, and you want it to be of the greatest
285 | possible use to the public, the best way to achieve this is to make it
286 | free software which everyone can redistribute and change under these terms.
287 |
288 | To do so, attach the following notices to the program. It is safest
289 | to attach them to the start of each source file to most effectively
290 | convey the exclusion of warranty; and each file should have at least
291 | the "copyright" line and a pointer to where the full notice is found.
292 |
293 | {{description}}
294 | Copyright (C) {{year}} {{fullname}}
295 |
296 | This program is free software; you can redistribute it and/or modify
297 | it under the terms of the GNU General Public License as published by
298 | the Free Software Foundation; either version 2 of the License, or
299 | (at your option) any later version.
300 |
301 | This program is distributed in the hope that it will be useful,
302 | but WITHOUT ANY WARRANTY; without even the implied warranty of
303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
304 | GNU General Public License for more details.
305 |
306 | You should have received a copy of the GNU General Public License along
307 | with this program; if not, write to the Free Software Foundation, Inc.,
308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
309 |
310 | Also add information on how to contact you by electronic and paper mail.
311 |
312 | If the program is interactive, make it output a short notice like this
313 | when it starts in an interactive mode:
314 |
315 | Gnomovision version 69, Copyright (C) year name of author
316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
317 | This is free software, and you are welcome to redistribute it
318 | under certain conditions; type `show c' for details.
319 |
320 | The hypothetical commands `show w' and `show c' should show the appropriate
321 | parts of the General Public License. Of course, the commands you use may
322 | be called something other than `show w' and `show c'; they could even be
323 | mouse-clicks or menu items--whatever suits your program.
324 |
325 | You should also get your employer (if you work as a programmer) or your
326 | school, if any, to sign a "copyright disclaimer" for the program, if
327 | necessary. Here is a sample; alter the names:
328 |
329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program
330 | `Gnomovision' (which makes passes at compilers) written by James Hacker.
331 |
332 | {signature of Ty Coon}, 1 April 1989
333 | Ty Coon, President of Vice
334 |
335 | This General Public License does not permit incorporating your program into
336 | proprietary programs. If your program is a subroutine library, you may
337 | consider it more useful to permit linking proprietary applications with the
338 | library. If this is what you want to do, use the GNU Lesser General
339 | Public License instead of this License.
340 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | WordPress Move
2 | ==========
3 |
4 | WordPress Move enables you to back up your installation to restore to at any time, change the domain name in use and migrate your installation to another server.
5 |
6 | Description
7 | ---------
8 |
9 | WordPress Move is a migration assistant for WordPress that is capable of changing the domain name in use and/or migrating your installation to another server either as is or based on your choices. In addition to these, you can use WordPress Move to transfer your database or create backups of your installation. For further information on using the plugin, please refer to the documentation provided with the plugin.
10 |
11 | **Disclaimer:** Even though this plugin is heavily tested, please use it at your own risk and do not forget to back up your files beforehand.
12 |
13 | Installation
14 | ---------
15 |
16 | **1.** Upload `wordpress-move` to the `/wp-content/plugins/` directory
17 |
18 | **2.** Activate the plugin through the 'Plugins' menu in WordPress
19 |
20 | **3.** Configure the plugin through the WordPress Move page under the 'Settings' menu
21 |
22 | **4.** Start using the tools added under the 'Tools' menu
23 |
24 |
25 | Frequently Asked Questions
26 | ----------------------
27 |
28 | **I am getting the "Could not activate the plugin because it generated a fatal error." error when I try to activate the plugin. Why?**
29 |
30 | WordPress Move needs php_sockets extension to be enabled, in order to work properly. If you are getting this error message, please enable php_sockets extension and restart your web server. Once you successfully enable the extension, you will be able to activate the plugin.
31 |
32 | **Do I need to install WordPress and WordPress Move on the new server as well, if I want to use WordPress Move for migration purposes?**
33 |
34 | Yes you do.
35 |
36 | **Is it possible to both migrate to another server and change the domain name?**
37 |
38 | Yes. You can choose whether you want to change your domain name or not on the migration screen. Note that it does not change the domain name used by the current installation, it just replaces instances of the old domain name with the new one on the fly while creating a database backup for migration.
39 |
40 | **Can I use WordPress Move to create backups of my installation?**
41 |
42 | Yes, you can. Click either "Create a Database Backup" button or "Create a Full Backup" button to create a backup. Your backup files will be stored under the backup directory. You can use Complete Migration mode whenever you want to use those files to revert to a former state of your installation.
43 |
44 | **Can I use WordPress Move to transfer my database backup only?**
45 |
46 | Yes, you can. All you need to do is selecting the Advanced Migration during the migration type selection page and not selecting any files when the file tree is displayed. Once you click the Start Migration button, the plugin will create a backup of your database only and transfer it to your new server. When you run WordPress Move on your new server in Complete Migration mode, the plugin will import the database backup created by your old WordPress installation.
47 |
48 | **Does WordPress Move take care of changing the whole domain name changing process?**
49 |
50 | No, it does not. WordPress Move just replaces instances of your old domain name in your database with the new domain name you provide. It is still your responsibility to point your domain name to the name servers used by your hosting company and make necessary configurations on the control panel provided by your hosting company. Before starting this process, please request assistance from your hosting company as some companies' systems erase all your data without creating backups when you change your domain name. Also, do not forget that it is always a good idea to have a backup of your files and the database before starting operations like these.
51 |
52 | **Plugin fails to create backup files because it says my backup directory is not writable. How can I fix this?**
53 |
54 | As the warning suggests, you need to make the backup directory writable by the plugin. Permission settings vary from server to server so there is no specific value to set the directory permissions to. The easiest way to fix this problem yourself is using an FTP client to alter permission settings of the backup directory until plugin successfully creates backup files. You may also prefer requesting assistance from your hosting company.
55 |
56 | **I am a pre-1.2 user, what will happen to the FTP Password that is already stored in my database?**
57 |
58 | Visiting the WordPress Move Settings page any time after updating the plugin will remove it from the database permanently.
59 |
60 | **Can I use the database backup files that WordPress Move generates with phpMyAdmin?**
61 |
62 | You can convert a database backup file using the Convert option in the Backup Manager to use it outside the plugin. So, yes, you can use the *converted* database backup files with phpMyAdmin or any other script.
63 |
64 | Changelog
65 | --------
66 |
67 | **1.3.2**
68 |
69 | * Fixed the bug causing problems with other plugins such as Gravity Forms.
70 |
71 | **1.3.1**
72 |
73 | * Fixed several bugs.
74 |
75 | * Improved the performance of the plugin in complex tasks.
76 |
77 | * It is now possible to download a backup file by clicking on its name.
78 |
79 | * If the Safe Mode is disabled, operations will not be interrupted by the maximum execution time error anymore.
80 |
81 | **1.3**
82 |
83 | * Explanation for Change Domain Name is rephrased.
84 |
85 | * Simple and Advanced Migration methods are merged.
86 |
87 | * Meta boxes are added to the migration page.
88 |
89 | * A database backup converter is integrated to convert WordPress-Move-only database backup files to generic SQL files.
90 |
91 | * Backup files to use for restoration can now be selected right on the Restore page.
92 |
93 | * Messages are now displayed in real-time on migration and restoration pages.
94 |
95 | * Empty HTML files are added to backup directories to prevent them being listed by people trying to access the directory via their browsers.
96 |
97 |
98 | **1.2**
99 |
100 | * FTP Passwords are no longer stored in the database, for security reasons. Visit the WordPress Move Settings page after updating the plugin to remove it from the database permanently.
101 |
102 | * It is now possible to create either a full backup or a database backup, using Backup Manager.
103 |
104 | * Fixed another PHP Catchable Fatal Error some people encounter.
105 |
106 | * Plugin is now really able to check whether importing the database backup was successful or not.
107 |
108 | * Explanations on the Migration Assistant page are replaced with more clear ones.
109 |
110 | * Added meta boxes to the Migration Assistant.
111 |
112 |
113 | **1.1.1**
114 |
115 | * Transients are no longer included in database backups to reduce the database backup files' sizes.
116 |
117 | * Backup files created before changing the domain name are now being stored under the old backup directory for a possible future need.
118 |
119 | * Fixed the PHP Catchable Fatal Error some people encounter.
120 |
121 | * Added meta boxes to the settings page.
122 |
123 |
124 | **1.1**
125 |
126 | * Added "Backup Now" functionality to Backup Manager.
127 |
128 | * Added the capability of migrating and changing the domain name at the same time.
129 |
130 |
131 | **1.0**
132 |
133 | * Initial release.
134 |
135 | Upgrade Notice
136 | ------------
137 |
138 | **1.3.2**
139 |
140 | The bug that was causing problems with other plugins has been fixed. Previous releases were omitting NULL fields and causing data loss as a result.
141 |
142 | **1.3.1**
143 |
144 | Performance has been improved and several bugs have been fixed. Also, if the Safe Mode is disabled, operations will not be interrupted by the maximum execution time error anymore.
145 |
146 | **1.3**
147 |
148 | Simple and Advanced Migration methods are merged and a database backup converter is integrated into the Backup Manager.
149 |
150 | **1.2**
151 |
152 | FTP Passwords are no longer stored in the database, for security reasons. It is now possible to create either a full backup or a database backup, using Backup Manager. Explanations on the Migration Assistant page are replaced with more clear ones.
153 |
154 | **1.1.1**
155 |
156 | Database backup files will be smaller now as transients will not be included in database backup files. Backup files created before changing the domain name are now being stored under the old backup directory for a possible future need. A small bug is fixed and meta boxes are added to the settings page of the plugin.
157 |
158 | **1.1**
159 |
160 | You can now create a full backup of your installation using the Backup Now button on the Backup Manager page. Also, migrating and changing the domain name at the same time is now supported.
161 |
162 | **1.0**
163 |
164 | Initial release.
165 |
--------------------------------------------------------------------------------
/backup/converted/index.html:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/backup/converted/index.html
--------------------------------------------------------------------------------
/backup/index.html:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/backup/index.html
--------------------------------------------------------------------------------
/backup/old/index.html:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/backup/old/index.html
--------------------------------------------------------------------------------
/docs/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 | WordPress Move Documentation
4 |
5 |
6 |
7 |
8 |
This documentation is was written to help new WordPress Move users start using the plugin faster and more efficiently. Even though the plugin is designed to be as straightforward as possible, it may still be confusing for new users. It is highly recommended that you read this documentation before using the plugin. You can find the list of topics covered in this documentation below.
Installing WordPress Move is no different than other plugins. You can either download the plugin from WordPress Plugin Directory and install it manually or use the search feature on the Install Plugin page.
29 |
There are actually two different types of manual installations. For both of them, first you need to download the plugin in .zip format from WordPress Plugin Directory. Then you can follow one of the manual installation methods explained below.
30 |
The first way is using the Upload tab on the Install Plugin page. To begin, please navigate to Administration Panel → Plugins → Add New → Upload to upload the .zip file you have just downloaded. Once you select the file to upload from your computer and click the Install Now button, WordPress will automatically install the plugin for you.
31 |
The second way is uploading the contents of the .zip file you have just downloaded to /wp-content/plugins/ directory using your FTP client. Do not forget that you need to upload the directory inside the .zip file not the .zip file itself. For further instructions on uploading files using your FTP client, please refer to the documentation of your FTP client.
32 |
The easiest way to install the plugin, however, is using the Search feature on the Install Plugin page. To begin, please navigate to Administration Panel → Plugins → Add New where you can search for the plugin by typing WordPress Move to the textbox and clicking the Search Plugins button. Then, on the search results page, please click the Install Now link displayed under the name of the plugin to begin installing the plugin.
33 |
After following one of these three methods, please navigate to Administration Panel → Plugins → Installed Plugins page and activate the plugin using the Activate link display right under the name of the plugin. Once you see the Plugin activated. notification at the top, you are ready to start using the plugin.
34 |
Configuration
35 |
Once you activated WordPress Move, it added 3 pages to your Administration Panel: Migration Assistant, Backup Manager and WordPress Move. First two are located under the Tools menu while the last one is located under the Settings menu. To configure the plugin, you need to navigate to WordPress Move page under the Settings menu. Before diving into configuring the plugin, please note that configuration is only necessary if you are planning to use the plugin to migrate to another server. In other words, you do not need any configuration if you are only going to use the plugin to change the domain name of your existing installation. or complete the migration started from another server. Also, if you are planning to use the plugin to migrate your existing installation to another server, first you need to install WordPress and WordPress Move on the remote server as well before continuing.
36 |
If you have successfully completed installing WordPress and WordPress Move on the remote server, please navigate to WordPress Move Settings page, where you will see eight settings under three titles.
37 |
38 |
First set of settings are used to connect to the server you want to migrate to. Most probably you are already familiar with the first four settings but if you are not, it might be a good idea to request some assistance from your hosting company to obtain these details. Once you obtain them, please fill in these settings. Now, to fill in the next setting, Remote Backup Path, you need to know the exact path to the directory you have WordPress installed on the remote server. The easiest way to learn this is using an FTP client to connect the server and navigating to the directory where WordPress is installed. Once you get there, copy the path and paste it to the Remote Backup Path setting field on the settings page of the plugin. Then, append the following to that path: /wp-content/plugins/wordpress-move/backup/. The reason why this is not automatically appended by the plugin is to give power users the ability to change the backup directory with two small alterations (the other is changing the WPMOVE_BACKUP_DIR constant on wordpress-move.php file). The last setting in this set is the Passive Mode setting. If you do not know what to set, please leave it as is and toggle if you experience issues with connecting to the remote server.
39 |
The second set of settings is Database Backup Settings which consists of only one setting that defines the chunk size of the database backup that will be created, in megabytes. Please type 0 to create the database backup as a single file.
40 |
The third set of settings is File Backup Settings which consists of only one setting that defines the size of files to compress per filesystem backup chunk, in megabytes. Please type 0 to create the filesystem backup as a single file.
41 |
42 |
Now you are ready to start the migration by going to the Migration Assistant page under the Tools menu.
43 |
Using The Plugin
44 |
Using the plugin is fairly simple. If you want to change your domain name, start migrating to another server or complete the migration you have already started from another server, you need to navigate to Migration Assistant page under the tools menu. However, if you want to manage the backup files under the backup directory, you need to navigate to Backup Manager page under the tools menu.
45 |
Migration Assistant
46 |
Migration Assistant welcomes you with three different actions you may want to perform: Change Domain Name, Start Migration and Restore. If you wish to only change the domain name of your current installation, you should click the Change Domain Name link. If you wish to migrate to another server, you should click the Start Migration link. Once again, do not forget that you need to configure the plugin by going to WordPress Move page under the Settings menu before starting the migration. And finally, if you wish to complete the migration process started from another server, click the Complete Migration link.
47 |
Change Domain Name
48 |
Changing the domain name that your current installation operates on is quite easy. Just type in the new domain name you want to use instead of the current domain name and click the Change button. Plugin will immediately change all instances of your old domain name in the database with your new domain name. WordPress Move also backups your database before starting the operation so if something goes wrong, it rolls back all the changes made. Of course, rolling back may also fail under some circumstances so creating a backup of your database manually beforehand is always a good idea. WordPress Move actually saves the backup file it creates beforehand to the old backup directory in case something goes wrong either during the domain name changing procedure or afterwards. Note that database backup files WordPress Move creates are not like normal database backup files, so you will need a working instance of WordPress Move on that server to be able to restore using those backup files. Still, creating a backup file yourself is highly encouraged. Do not forget that WordPress Move only replaces instances of your old domain name in the database with your new domain name and does not make any further configurations needed to make your domain work on your host. Please refer to the question in the FAQ section for some additional information about this.
49 |
Migrate
50 |
Migration page displays all the files under your WordPress installation directory and asks you which files to backup. Once you click the Start Migration button, it creates the backup of your database and the files (in chunks if you set a Chunk Size on the settings page of the plugin) you selected, and uploads them to the remote server. If you do not select any files, only a backup of your database will be uploaded to the server you want to migrate to. Also, the option to change the domain name that will be used on your new server is provided as well. It only changes the domain name that will be used by the installation in the receiving end. When starting the migration succeeds, you can run WordPress Move on the remote server in Complete Migration mode to complete the migration process.
51 |
Restore
52 |
Restore option basically imports database backups and extracts filesystem backups, created and uploaded by WordPress Move on the server you want to migrate from. When you navigate to Restore page, it lists all the backup files inside the main backup directory aka Current Backups that you can choose from to complete the migration. Do not forget that this process does not create a backup of your existing installation so if something goes wrong, it will not be possible to rollback the changes. It is your responsibility to backup your files and the database before clicking the Complete Migration button. If there are no files listed on the Complete Migration page, please make sure you started the migration successfully using WordPress Move on the server you are migrating from.
53 |
Backup Manager
54 |
Backup Manager is the place to organize the backup files either created by the plugin on the same server, or uploaded by the server you are migrating from. If this is the server you want to migrate from, you can delete backup files after the Migration Assistant completes uploading them to the remote server. If you do not want to delete them, you can Archive them which basically means moving them to a sub-directory called old. You can always Unarchive the files you Archived using the Backup Manager. Files listed under Current Backups are the files that will be used by the Complete Migration mode so you can either delete or achive the files you do not want Complete Migration to use. Files listed under the Old Backups section are not used for anything so you can safely Archive the backup files you do not want to use but also do not want to delete.
55 |
Since version 1.3, there is also Converted Database Backups section where which lists the database backup files that can be used outside the WordPress Move. As you might have noticed, database backups generated by WordPress Move have a different structure than normal database backup files which is the reason why you cannot use them outside the WordPress Move. To use database backup file outside the WordPress Move, simply find it in either Current Backups or Old Backups section, select the checkbox on the left, select the Convert option from the dropdown and click the Apply button. This will convert the files you have selected into generic SQL files that you can use outside the plugin. This feature is particularly useful if the plugin fails to migrate your installation properly or if you need to use the database backup file outside the plugin.
56 |
If you wish to download a backup file, you can click on its name. That way, if the plugin fails send your files to the server on the receiving end, you can easily download your backup files and upload them to the /wp-content/plugins/wordpress-move/backup/ directory on your new server. Once you finish uploading them, you can use the Restore method to finalize the migration operation.
57 |
Frequently Asked Questions
58 |
59 |
I am getting the "Could not activate the plugin because it generated a fatal error." error when I try to activate the plugin. Why?
60 | WordPress Move needs php_sockets extension to be enabled, in order to work properly. If you are getting this error message, please enable php_sockets extension and restart your web server. Once you successfully enable the extension, you will be able to activate the plugin.
61 |
Do I need to install WordPress and WordPress Move on the new server as well, if I want to use WordPress Move for migration purposes?
62 | Yes you do.
63 |
Is it possible to both migrate to another server and change the domain name?
64 | Yes. You can choose whether you want to change your domain name or not on the migration screen. Note that it does not change the domain name used by the current installation, it just replaces instances of the old domain name with the new one on the fly while creating a database backup for migration.
65 |
Can I use WordPress Move to create backups of my installation?
66 | Yes, you can. Click either Create a Database Backup button or Create a Full Backup button to create a backup. Your backup files will be stored under the backup directory. You can use Complete Migration mode whenever you want to use those files to revert to a former state of your installation.
67 |
Can I use WordPress Move to transfer my database backup only?
68 | Yes, you can. All you need to do is selecting the Advanced Migration during the migration type selection page and not selecting any files when the file tree is displayed. Once you click the Start Migration button, the plugin will create a backup of your database only and transfer it to your new server. When you run WordPress Move on your new server in Complete Migration mode, the plugin will import the database backup created by your old WordPress installation.
69 |
Does WordPress Move take care of changing the whole domain name changing process?
70 | No, it does not. WordPress Move just replaces instances of your old domain name in your database with the new domain name you provide. It is still your responsibility to point your domain name to the name servers used by your hosting company and make necessary configurations on the control panel provided by your hosting company. Before starting this process, please request assistance from your hosting company as some companies' systems erase all your data without creating backups when you change your domain name. Also, do not forget that it is always a good idea to have a backup of your files and the database before starting operations like these.
71 |
Plugin fails to create backup files because it says my backup directory is not writable. How can I fix this?
72 | As the warning suggests, you need to make the backup directory writable by the plugin. Permission settings vary from server to server so there is no specific value to set the directory permissions to. The easiest way to fix this problem yourself is using an FTP client to alter permission settings of the backup directory until plugin successfully creates backup files. You may also prefer requesting assistance from your hosting company.
73 |
I am a pre-1.2 user, what will happen to the FTP Password that is already stored in my database?
74 | Visiting the WordPress Move Settings page any time after updating the plugin will remove it from the database permanently.
75 |
Can I use the database backup files that WordPress Move generates with phpMyAdmin?
76 | You can convert a database backup file using the Convert option in the Backup Manager to use it outside the plugin. So, yes, you can use the converted database backup files with phpMyAdmin or any other script.
").append(o)}if(i==-1||!i){this.get_container().children("ul").empty().append(o.children()).find("li, a").filter(function(){return !this.firstChild||!this.firstChild.tagName||this.firstChild.tagName!=="INS"}).prepend(" ").end().filter("a").children("ins:first-child").not(".jstree-icon").addClass("jstree-icon")}else{i.children("a.jstree-loading").removeClass("jstree-loading");i.append(o).children("ul").find("li, a").filter(function(){return !this.firstChild||!this.firstChild.tagName||this.firstChild.tagName!=="INS"}).prepend(" ").end().filter("a").children("ins:first-child").not(".jstree-icon").addClass("jstree-icon");i.removeData("jstree_is_loading")}this.clean_node(i);if(e){e.call(this)}}else{if(i&&i!==-1){i.children("a.jstree-loading").removeClass("jstree-loading");i.removeData("jstree_is_loading");if(h.correct_state){this.correct_state(i);if(e){e.call(this)}}}else{if(h.correct_state){this.get_container().children("ul").empty();if(e){e.call(this)}}}}};h.ajax.context=this;h.ajax.error=f;h.ajax.success=j;if(!h.ajax.dataType){h.ajax.dataType="html"}if(d.isFunction(h.ajax.url)){h.ajax.url=h.ajax.url.call(this,i)}if(d.isFunction(h.ajax.data)){h.ajax.data=h.ajax.data.call(this,i)}d.ajax(h.ajax);break}}}});d.jstree.defaults.plugins.push("html_data")})(jQuery)})();
--------------------------------------------------------------------------------
/libs/js/themes/default/d.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/libs/js/themes/default/d.png
--------------------------------------------------------------------------------
/libs/js/themes/default/file.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/libs/js/themes/default/file.png
--------------------------------------------------------------------------------
/libs/js/themes/default/style.css:
--------------------------------------------------------------------------------
1 | /*
2 | * jsTree default theme 1.0
3 | * Supported features: dots/no-dots, icons/no-icons, focused, loading
4 | * Supported plugins: ui (hovered, clicked), checkbox, contextmenu, search
5 | */
6 |
7 | .jstree-default li,
8 | .jstree-default ins {
9 | background-color:transparent;
10 | background-image: url("d.png");
11 | background-repeat: no-repeat;
12 | }
13 | .jstree-default li {
14 | background-position: -90px 0;
15 | background-repeat: repeat-y;
16 | }
17 | .jstree-default li.jstree-last {
18 | background: transparent;
19 | }
20 | .jstree-default .jstree-open > ins {
21 | background-position: -72px 0;
22 | }
23 | .jstree-default .jstree-closed > ins {
24 | background-position: -54px 0;
25 | }
26 | .jstree-default .jstree-leaf > ins {
27 | background-position: -36px 0;
28 | }
29 |
30 | .jstree-default .jstree-hovered {
31 | background: #e7f4f9;
32 | border: 1px solid #d8f0fa;
33 | padding: 0 2px 0 1px;
34 | }
35 | .jstree-default .jstree-clicked {
36 | background: #beebff;
37 | border: 1px solid #99defd;
38 | padding:0 2px 0 1px;
39 | }
40 | .jstree-default a .jstree-icon {
41 | background-position: -56px -19px;
42 | }
43 | .jstree-default a.jstree-loading .jstree-icon {
44 | background: url("throbber.gif") center center no-repeat !important;
45 | }
46 |
47 | .jstree-default.jstree-focused {
48 | background: #f7f7f7;
49 | }
50 |
51 | .jstree-default .jstree-no-dots li,
52 | .jstree-default .jstree-no-dots .jstree-leaf > ins {
53 | background: transparent;
54 | }
55 | .jstree-default .jstree-no-dots .jstree-open > ins {
56 | background-position: -18px 0;
57 | }
58 | .jstree-default .jstree-no-dots .jstree-closed > ins {
59 | background-position: 0 0;
60 | }
61 |
62 | .jstree-default .jstree-no-icons a .jstree-icon {
63 | display: none;
64 | }
65 |
66 | .jstree-default .jstree-search {
67 | font-style: italic;
68 | }
69 |
70 | .jstree-default .jstree-no-icons .jstree-checkbox {
71 | display: inline-block;
72 | }
73 | .jstree-default .jstree-no-checkboxes .jstree-checkbox {
74 | display: none !important;
75 | }
76 | .jstree-default .jstree-checked > a > .jstree-checkbox {
77 | background-position: -38px -19px;
78 | }
79 | .jstree-default .jstree-unchecked > a > .jstree-checkbox {
80 | background-position: -2px -19px;
81 | }
82 | .jstree-default .jstree-undetermined > a > .jstree-checkbox {
83 | background-position: -20px -19px;
84 | }
85 | .jstree-default .jstree-checked > a > .jstree-checkbox:hover {
86 | background-position: -38px -37px;
87 | }
88 | .jstree-default .jstree-unchecked > a > .jstree-checkbox:hover {
89 | background-position: -2px -37px;
90 | }
91 | .jstree-default .jstree-undetermined > a > .jstree-checkbox:hover {
92 | background-position: -20px -37px;
93 | }
94 |
95 | #vakata-dragged.jstree-default ins {
96 | background: transparent !important;
97 | }
98 | #vakata-dragged.jstree-default .jstree-ok {
99 | background: url("d.png") -2px -53px no-repeat !important;
100 | }
101 | #vakata-dragged.jstree-default .jstree-invalid {
102 | background: url("d.png") -18px -53px no-repeat !important;
103 | }
104 | #jstree-marker.jstree-default {
105 | background: url("d.png") -41px -57px no-repeat !important;
106 | text-indent: -100px;
107 | }
108 |
109 | .jstree-default a.jstree-search {
110 | color: aqua;
111 | }
112 | .jstree-default .jstree-locked a {
113 | color: silver;
114 | cursor: default;
115 | }
116 |
117 | #vakata-contextmenu.jstree-default-context,
118 | #vakata-contextmenu.jstree-default-context li ul {
119 | background: #f0f0f0;
120 | border: 1px solid #979797;
121 | -moz-box-shadow: 1px 1px 2px #999;
122 | -webkit-box-shadow: 1px 1px 2px #999;
123 | box-shadow: 1px 1px 2px #999;
124 | }
125 | #vakata-contextmenu.jstree-default-context li { }
126 | #vakata-contextmenu.jstree-default-context a {
127 | color:black;
128 | }
129 | #vakata-contextmenu.jstree-default-context a:hover,
130 | #vakata-contextmenu.jstree-default-context .vakata-hover > a {
131 | padding: 0 5px;
132 | background: #e8eff7;
133 | border: 1px solid #aecff7;
134 | color: black;
135 | -moz-border-radius: 2px;
136 | -webkit-border-radius: 2px;
137 | border-radius: 2px;
138 | }
139 | #vakata-contextmenu.jstree-default-context li.jstree-contextmenu-disabled a,
140 | #vakata-contextmenu.jstree-default-context li.jstree-contextmenu-disabled a:hover {
141 | color: silver;
142 | background: transparent;
143 | border: 0;
144 | padding: 1px 4px;
145 | }
146 | #vakata-contextmenu.jstree-default-context li.vakata-separator {
147 | background: white;
148 | border-top: 1px solid #e0e0e0;
149 | margin: 0;
150 | }
151 | #vakata-contextmenu.jstree-default-context li ul {
152 | margin-left: -4px;
153 | }
--------------------------------------------------------------------------------
/libs/js/themes/default/throbber.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/merty/wordpress-move/ae8638ce1340cd1b7a20cf297dcfdcff2b9d11bb/libs/js/themes/default/throbber.gif
--------------------------------------------------------------------------------
/readme.txt:
--------------------------------------------------------------------------------
1 | === WordPress Move ===
2 | Contributors: merty
3 | Donate link: http://www.mertyazicioglu.com
4 | Tags: backup, domain, migrate, migration, move, restore
5 | Requires at least: 3.2
6 | Tested up to: 3.4.2
7 | Stable tag: 1.3.2
8 | License: GPLv2 or later
9 | License URI: http://www.gnu.org/licenses/gpl-2.0.html
10 |
11 | Enables you to back up your installation to restore to at any time, change the domain name in use and migrate your installation to another server.
12 |
13 | == Description ==
14 |
15 | WordPress Move is a migration assistant for WordPress that is capable of changing the domain name in use and/or migrating your installation to another server either as is or based on your choices. In addition to these, you can use WordPress Move to transfer your database or create backups of your installation. For further information on using the plugin, please refer to the documentation provided with the plugin.
16 |
17 | **Disclaimer:** Even though this plugin is heavily tested, please use it at your own risk and do not forget to back up your files beforehand.
18 |
19 | == Installation ==
20 |
21 | 1. Upload `wordpress-move` to the `/wp-content/plugins/` directory
22 | 2. Activate the plugin through the 'Plugins' menu in WordPress
23 | 3. Configure the plugin through the WordPress Move page under the 'Settings' menu
24 | 4. Start using the tools added under the 'Tools' menu
25 |
26 | == Frequently Asked Questions ==
27 |
28 | = I am getting the "Could not activate the plugin because it generated a fatal error." error when I try to activate the plugin. Why? =
29 |
30 | WordPress Move needs php_sockets extension to be enabled, in order to work properly. If you are getting this error message, please enable php_sockets extension and restart your web server. Once you successfully enable the extension, you will be able to activate the plugin.
31 |
32 | = Do I need to install WordPress and WordPress Move on the new server as well, if I want to use WordPress Move for migration purposes? =
33 |
34 | Yes you do.
35 |
36 | = Is it possible to both migrate to another server and change the domain name? =
37 |
38 | Yes. You can choose whether you want to change your domain name or not on the migration screen. Note that it does not change the domain name used by the current installation, it just replaces instances of the old domain name with the new one on the fly while creating a database backup for migration.
39 |
40 | = Can I use WordPress Move to create backups of my installation? =
41 |
42 | Yes, you can. Click either "Create a Database Backup" button or "Create a Full Backup" button to create a backup. Your backup files will be stored under the backup directory. You can use Complete Migration mode whenever you want to use those files to revert to a former state of your installation.
43 |
44 | = Can I use WordPress Move to transfer my database backup only? =
45 |
46 | Yes, you can. All you need to do is selecting the Advanced Migration during the migration type selection page and not selecting any files when the file tree is displayed. Once you click the Start Migration button, the plugin will create a backup of your database only and transfer it to your new server. When you run WordPress Move on your new server in Complete Migration mode, the plugin will import the database backup created by your old WordPress installation.
47 |
48 | = Does WordPress Move take care of changing the whole domain name changing process? =
49 |
50 | No, it does not. WordPress Move just replaces instances of your old domain name in your database with the new domain name you provide. It is still your responsibility to point your domain name to the name servers used by your hosting company and make necessary configurations on the control panel provided by your hosting company. Before starting this process, please request assistance from your hosting company as some companies' systems erase all your data without creating backups when you change your domain name. Also, do not forget that it is always a good idea to have a backup of your files and the database before starting operations like these.
51 |
52 | = Plugin fails to create backup files because it says my backup directory is not writable. How can I fix this? =
53 |
54 | As the warning suggests, you need to make the backup directory writable by the plugin. Permission settings vary from server to server so there is no specific value to set the directory permissions to. The easiest way to fix this problem yourself is using an FTP client to alter permission settings of the backup directory until plugin successfully creates backup files. You may also prefer requesting assistance from your hosting company.
55 |
56 | = I am a pre-1.2 user, what will happen to the FTP Password that is already stored in my database? =
57 |
58 | Visiting the WordPress Move Settings page any time after updating the plugin will remove it from the database permanently.
59 |
60 | = Can I use the database backup files that WordPress Move generates with phpMyAdmin?
61 |
62 | You can convert a database backup file using the Convert option in the Backup Manager to use it outside the plugin. So, yes, you can use the *converted* database backup files with phpMyAdmin or any other script.
63 |
64 | == Changelog ==
65 |
66 | = 1.3.2 =
67 | * Fixed the bug causing problems with other plugins such as Gravity Forms.
68 |
69 | = 1.3.1 =
70 | * Fixed several bugs.
71 | * Improved the performance of the plugin in complex tasks.
72 | * It is now possible to download a backup file by clicking on its name.
73 | * If the Safe Mode is disabled, operations will not be interrupted by the maximum execution time error anymore.
74 |
75 | = 1.3 =
76 | * Explanation for Change Domain Name is rephrased.
77 | * Simple and Advanced Migration methods are merged.
78 | * Meta boxes are added to the migration page.
79 | * A database backup converter is integrated to convert WordPress-Move-only database backup files to generic SQL files.
80 | * Backup files to use for restoration can now be selected right on the Restore page.
81 | * Messages are now displayed in real-time on migration and restoration pages.
82 | * Empty HTML files are added to backup directories to prevent them being listed by people trying to access the directory via their browsers.
83 |
84 | = 1.2 =
85 | * FTP Passwords are no longer stored in the database, for security reasons. Visit the WordPress Move Settings page after updating the plugin to remove it from the database permanently.
86 | * It is now possible to create either a full backup or a database backup, using Backup Manager.
87 | * Fixed another PHP Catchable Fatal Error some people encounter.
88 | * Plugin is now really able to check whether importing the database backup was successful or not.
89 | * Explanations on the Migration Assistant page are replaced with more clear ones.
90 | * Added meta boxes to the Migration Assistant.
91 |
92 | = 1.1.1 =
93 | * Transients are no longer included in database backups to reduce the database backup files' sizes.
94 | * Backup files created before changing the domain name are now being stored under the old backup directory for a possible future need.
95 | * Fixed the PHP Catchable Fatal Error some people encounter.
96 | * Added meta boxes to the settings page.
97 |
98 | = 1.1 =
99 | * Added "Backup Now" functionality to Backup Manager.
100 | * Added the capability of migrating and changing the domain name at the same time.
101 |
102 | = 1.0 =
103 | * Initial release.
104 |
105 | == Upgrade Notice ==
106 |
107 | = 1.3.2 =
108 | The bug that was causing problems with other plugins has been fixed. Previous releases were omitting NULL fields and causing data loss as a result.
109 |
110 | = 1.3.1 =
111 | Performance has been improved and several bugs have been fixed. Also, if the Safe Mode is disabled, operations will not be interrupted by the maximum execution time error anymore.
112 |
113 | = 1.3 =
114 | Simple and Advanced Migration methods are merged and a database backup converter is integrated into the Backup Manager.
115 |
116 | = 1.2 =
117 | FTP Passwords are no longer stored in the database, for security reasons. It is now possible to create either a full backup or a database backup, using Backup Manager. Explanations on the Migration Assistant page are replaced with more clear ones.
118 |
119 | = 1.1.1 =
120 | Database backup files will be smaller now as transients will not be included in database backup files. Backup files created before changing the domain name are now being stored under the old backup directory for a possible future need. A small bug is fixed and meta boxes are added to the settings page of the plugin.
121 |
122 | = 1.1 =
123 | You can now create a full backup of your installation using the Backup Now button on the Backup Manager page. Also, migrating and changing the domain name at the same time is now supported.
124 |
125 | = 1.0 =
126 | Initial release.
127 |
--------------------------------------------------------------------------------
/uninstall.php:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/wordpress-move.php:
--------------------------------------------------------------------------------
1 | load_language_file();
69 | }
70 |
71 | /**
72 | * Loads the language file.
73 | *
74 | * @param void
75 | * @return void
76 | */
77 | function load_language_file() {
78 | load_plugin_textdomain( 'WPMove', FALSE, basename( dirname( __FILE__ ) ) . '/lang/' );
79 | }
80 |
81 | /**
82 | * Adds the script to the head for Migration Assistant.
83 | *
84 | * @param void
85 | * @return void
86 | */
87 | function add_migration_assistant_js() {
88 |
89 | ?>
90 |
116 |
152 |
158 | get_admin_options();
189 | }
190 |
191 | /**
192 | * Returns settings of the plugin.
193 | *
194 | * @param void
195 | * @return void
196 | */
197 | function get_admin_options() {
198 |
199 | // Define options and their default values
200 | $wpmove_admin_options = array( 'db_chunk_size' => 0,
201 | 'fs_chunk_size' => 10,
202 | 'ftp_hostname' => '',
203 | 'ftp_port' => 21,
204 | 'ftp_username' => '',
205 | 'ftp_passive_mode' => 1,
206 | 'ftp_remote_path' => '',
207 | );
208 |
209 | // Try retrieving options from the database
210 | $wpmove_options = get_option( $this->admin_options_name );
211 |
212 | // Deletes the FTP Password stored in the database
213 | if ( is_array( $wpmove_options ) && array_key_exists( 'ftp_password', $wpmove_options ) )
214 | unset( $wpmove_options['ftp_password'] );
215 |
216 | // If the option set already exists in the database, reset their values
217 | if ( ! empty( $wpmove_options ) )
218 | foreach ( $wpmove_options as $key => $value )
219 | $wpmove_admin_options[$key] = $value;
220 |
221 | // Update the database
222 | update_option( $this->admin_options_name, $wpmove_admin_options );
223 |
224 | // Return options
225 | return $wpmove_admin_options;
226 | }
227 |
228 | /**
229 | * Generates the settings page of the plugin.
230 | *
231 | * @param void
232 | * @return void
233 | */
234 | function print_settings_page() {
235 |
236 | // Get plugin's settings
237 | $wpmove_options = $this->get_admin_options();
238 |
239 | // If the form is submitted successfully...
240 | if ( $_POST && check_admin_referer( 'wpmove_update_settings' ) ) {
241 |
242 | // If the user was redirected from the migration assistant, redirect him/her back once all necessary fields are filled
243 | if ( isset( $_POST['wpmove_ref'] ) && $_POST['wpmove_ftp_hostname'] !== '' && $_POST['wpmove_ftp_username'] !== '' && $_POST['wpmove_ftp_port'] !== 0 )
244 | echo '';
245 |
246 | // Store the changes made...
247 | $wpmove_options['db_chunk_size'] = intval( $_POST['wpmove_db_chunk_size'] );
248 | $wpmove_options['fs_chunk_size'] = intval( $_POST['wpmove_fs_chunk_size'] );
249 | $wpmove_options['ftp_hostname'] = sanitize_text_field( $_POST['wpmove_ftp_hostname'] );
250 | $wpmove_options['ftp_port'] = intval( $_POST['wpmove_ftp_port'] );
251 | $wpmove_options['ftp_username'] = sanitize_text_field( $_POST['wpmove_ftp_username'] );
252 | $wpmove_options['ftp_passive_mode'] = intval( $_POST['wpmove_ftp_passive_mode'] );
253 | $wpmove_options['ftp_remote_path'] = sanitize_text_field( $_POST['wpmove_ftp_remote_path'] );
254 |
255 | // Update plugin settings
256 | update_option( $this->admin_options_name, $wpmove_options );
257 |
258 | ?>
259 |
260 |
' . __( 'Please fill in FTP Connection Details in order to start the migration process.', 'WPMove' ) . '