Title: SitePush Author: Mark Rowatt Anderson Published: Hulyo 5, 2012 Last modified: Setyembre 9, 2013 --- Maghanap ng mga plugin Ang plugin na ito ay **hindi pa nasusubukan sa pinakabagong 3 major release ng WordPress**. Maaaring hindi na ito minamantine o sinusuportahan at maaaring may mga isyu sa compatibility kapag ginamit sa mas bagong bersyon ng WordPress. ![](https://s.w.org/plugins/geopattern-icon/sitepush.svg) # SitePush Ni [Mark Rowatt Anderson](https://profiles.wordpress.org/markauk/) [I-download](https://downloads.wordpress.org/plugin/sitepush.0.4.2.zip) * [Mga Detalye](https://tl.wordpress.org/plugins/sitepush/#description) * [Mga Review](https://tl.wordpress.org/plugins/sitepush/#reviews) * [Pag-install](https://tl.wordpress.org/plugins/sitepush/#installation) * [Development](https://tl.wordpress.org/plugins/sitepush/#developers) [Suporta](https://wordpress.org/support/plugin/sitepush/) ## Deskripsyon SitePush is a WordPress plugin which allows you to have multiple versions of your WordPress site, so you can edit, develop, test without any risk to your main, live site. It’s great for developers, designers and editors… anyone who wants to be able to test changes to a site before it is visible to the world. For example:- 1. you can **easily move content between sites**. For example, make extensive edits on a private staging site, and then push changes all at once to your live site. Or, easily pull copy of your live database into your development site so you are developing against the latest content. 2. **test new themes and plugins**, and only push them to your live site once they are configured and working as you want. 3. upgrade WordPress, themes and plugins on a private site so you can **test that nothing breaks before upgrading your live site**. Sure you take backups before any upgrades (right?), but it’s a pain doing a full backup and an even bigger pain restoring from a backup. 4. easily make small (and big!) code changes on your development site, **test and easily push new code to a live site**. Great for dealing with clients who want “ just one more thing”. Although SitePush installation is a bit more involved than a typical plugin, once set up it runs with minimal effort and can be easily used by non-tech authors & editors. Site admins can easily configure SitePush so that non-admins can only push content (i.e. posts/pages, comments and uploads) and to a restricted set of sites. **Please read the _Installation_ instructions before you install SitePush – it’s not a normal download and activate type of plugin installation** #### Support SitePush is under active development and I will do my best to provide fixes to problems. The latest general releases are always available through the WordPress Plugins Directory. Development code is [hosted on GitHub](https://github.com/rowatt/sitepush/tree/develop), so you may find more frequent releases there. For general questions, please post on the WordPress forums with the tag sitepush. For bug reports or if you wish to suggest patches or fixes, please go to the [SitePush GitHub repository](https://github.com/rowatt/sitepush). If you have any problems with SitePush, it would be helpful if you could add ``` define('SITEPUSH_DEBUG',TRUE); ``` to your wp-config.php file, and include the output which will now be displayed at the top of the SitePush options screen. **Disclaimer** Although SitePush has been well tested and is used on production web sites, it moves files and database content between sites which could break things. Use of SitePush is at your own risk! Please make sure you have adequate backups and if you do find any problems please report them. #### Roadmap There are a number of areas which could be improved. Currently on the roadmap:- * improve push undo * add support for pushing between sites on different servers Please let me know how you would like to see SitePush evolve. ### Server Setup #### How to setup SitePush in a multiple vhost environment You can run your separate versions of a site in a single vhost, or in separate vhosts. While running them all in a single vhost can be little easier to set up on some web hosts, it does not work well if different sites need any different configuration in your .htaccess file – for example if you are using a caching plugin. If you are able to set up separate vhosts (or subdomains as some hosts call them) I recommend you do it that way. Let’s say you want to have three versions of your site – live, test, and dev. Set up a vhost for each site. Where they all sit on your server will depend on your hosting setup, but let’s say they are at:- ``` /var/www/vhosts/live/httpdocs /var/www/vhosts/test/httpdocs /var/www/vhosts/dev/httpdocs ``` You will need to create a directory to hold all the config files. If at all possible, this directory should not be web accessible. For example, it might be at:- ``` /var/www/sitepush/config ``` You will also probably want to create a directory for any backups SitePush makes, such as:- ``` /var/www/sitepush/backups ``` Finally, you will need to create a database for each of your sites. Consult the [WordPress installation instructions](https://codex.wordpress.org/Installing_WordPress) and your web host for how to do this. Download WordPress and unzip it into one of your sites. I normally keep WordPress in its own subdirectory, for example:- ``` /var/www/vhosts/live/httpdocs/wordpress ``` That way, the root directory stays clean, and if I install anything else outside of WordPress, there won’t be any confusion of which files belong where. You need to make a couple of changes for this setup to work – see [WordPress documentation](https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory) for more details. Note that for multisite installs, though, you will need to install WordPress in the root directory. I do, however, put my wp-config.php file in the root directory (WordPress is smart enough to find it). Next you will need to create the SitePush config files and put them in the config directory you created above. See [the SitePush installation instructions](https://wordpress.org/extend/plugins/sitepush/installation) for what needs to go in your sites config file and your database config file (I usually call them sites.ini.php and dbs.ini.php). Now, copy the files from the site you just set up to your other sites, for example:- ``` cd /var/www/vhosts cp -r live/httpdocs dev/httpdocs ``` To save a bit of disk space (at the expense of possibly messing things up between sites), you can also symlink the uploads directory between sites so there is only one copy of any media files uploaded. For example:- ``` cd /var/www/vhosts/dev/httpdocs/wordpress/wp-content rmdir uploads ln -s ../../../../live/httpdocs/wordpress/wp-content/uploads uploads ``` The exact paths will depend on your setup. Finally, log into your live site, install, activate and configure SitePush, and now you are set up to easily move files and content between 3 versions of your site! #### How to setup SitePush in a single vhost You can run your separate versions of a site in a single vhost, or in separate vhosts. Depending on your web host, running them all in a single vhost can be bit easier to set up, though it does mean you need to share one .htaccess file across all versions of your site, and won’t work for WordPress Multisite setups. If you are able to set up separate vhosts (or subdomains as some hosts call them) I recommend you do it that way, but if not, these instructions show how you can have multiple version so of your site on one vhost. Let’s say you want to have three versions of your site – live, test, and dev. First make sure that you can set up domain aliases on your host – so that multiple domains point to the same files. For example, you might set up:- ``` live.example.com test.example.com dev.example.com ``` If your host allows wildcard domain setups, so for example anything.example.com would point to your files, that would also work Set up a subdirectory for each site. Where they all sit on your server will depend on your hosting setup, but let’s say they are at:- ``` /var/www/httpdocs/live /var/www/httpdocs/test /var/www/httpdocs/dev ``` You will need to create a directory to hold all the config files. If at all possible, this directory should not be web accessible. For example, it might be at:- ``` /var/www/sitepush/config ``` You will also probably want to create a directory for any backups SitePush makes, such as:- ``` /var/www/sitepush/backups ``` Download WordPress and unzip it into one of the directories for your sites. For example:- ``` /var/www/httpdocs/live ``` Follow the [instructions](https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory) for more installing WordPress in a subdirectory. You should also now create a database for each of your sites. Consult the [WordPress installation instructions](https://codex.wordpress.org/Installing_WordPress) and your web host for how to do this. Complete any other required configuration (WordPress setup, plugin installs etc) and make sure that your site is now working properly. Don’t forget to install SitePush! Next you need to create the SitePush config files and put them in the config directory you created above. See here readme.txt or [the SitePush installation instructions](https://wordpress.org/extend/plugins/sitepush/installation) for what needs to go in your sites config file and your database config file (I usually call them sites.ini.php and dbs.ini.php). Now, copy the files from the site you just set up to your other sites, for example:- ``` cd /var/www/httpdocs cp -r live dev cp -r live test ``` To save a bit of disk space (at the expense of possibly messing things up between sites), you can also symlink the uploads directory between sites so there is only one copy of any media files uploaded. For example:- ``` cd /var/www/httpdocs/dev/wp-content rmdir uploads ln -s ../../live/wp-content/uploads uploads ``` The exact paths will depend on your setup. Next you need to make some changes to your wp-config.php file so that it will point to the correct site files and database depending on what domain name was used. The exact details will vary depending on your setup, but you will want something like this, which should be inserted immediately above the line `/* That's all, stop editing! Happy blogging. */`:- ``` switch ( $_SERVER['SERVER_NAME'] ) { case 'test.example.com': $site_dir='test'; define('DB_NAME', 'database_name_here'); define('DB_USER', 'username_here'); define('DB_PASSWORD', 'password_here'); break; case 'dev.example.com': define('DB_NAME', 'database_name_here'); define('DB_USER', 'username_here'); define('DB_PASSWORD', 'password_here'); $site_dir='dev'; break; case 'www.example.com': case 'live.example.com': default: define('DB_NAME', 'database_name_here'); define('DB_USER', 'username_here'); define('DB_PASSWORD', 'password_here'); $site_dir='live'; break; } ``` Insert whatever constant definitions are specific to a site in that section, and delete or comment them out from their original location in wp-config. Lastly, you need to edit the last line of wp-config so it reads:- ``` require("./{$site_dir}/wp-blog-header.php"); ``` You can now log into your live site, activate and configure SitePush. Once that is done, you can push everything to your other sites and you should now be able to access all three versions of your site. You are now set up to easily move files and content between 3 versions of your site! ## Mga Screenshot * [[ * Push screen for non-admins. Site admin can configure what non-admins can push, so they can’t push anything too dangerous. * [[ * Push screen as seen by admins. Admins can push any set of files or DB tables. * [[ * Push screen for a multisite installation as seen by admins. In this case, the admin has defined some custom table groups for Gravity Forms. * [[ * Main options screen. ## Pag-install #### Summary of installation steps 1. check that your setup meets the requirements in the section below 2. set up different versions of your site on your server 3. download and unzip the plugin in your plugins directory and activate the plugin 4. create and upload the config files which hold details of your sites and databases. See _Config file_ sections below for more details. 5. go to the SitePush settings page (immediately below Dashboard), and fill in settings as required. There is further help and explanation in the plugin. Details for each step are covered in the sections below. #### Requirements SitePush uses shell commands to do some of its stuff, so there is more chance of things going wrong than with most plugins. Please check that your set up meets these requirements, and even if it does, please test your setup thoroughly before pushing to a live site. SitePush is currently well tested on:- * Linux * MacOS X (MAMP) SitePush should work on Windows systems, but with the following caveats:- * backup of files will not work * clearing of arbitrary cache files will not work (caches[] option in sites config) * it is not as well tested on Windows systems If you would like to help make SitePush work better on Windows systems please let me know. **SitePush will not work in whole or in part**:- * if your host has PHP safe mode enabled * if your host does not allow PHP to execute shell commands * to push files between sites on different servers. Currently, SitePush must have filesystem access to all sites it pushes files to. Your databases can, however, be on different servers as long as they are accessible by the site your are pushing from. It has experimental support for Multisite installs:- * it will not run if you have WP_ALLOW_MULTISITE or MULTISITE defined as TRUE in your wp-config file unless you also define SITEPUSH_ALLOW_MULTISITE to TRUE in your wp-config file. In addition to WordPress (3.3 or greater), PHP (5.2.4 or greater) and mySQL (5.0 or greater) your server must have the following installed:- * mysql and mysqldump command line utilities (tested on mysql version 5.5, it should work on versions above 5.0) * tar (any version should be fine, required for file backups) #### Setup different versions of your site Different versions of your site must be on the same server (filesystem). You can setup different versions either in separate vhosts (normally recommended) or all in one vhost (won’t work for multisite installs and may not work if you are using caching plugins). For full details of how to do this, see the instructions for each method in the _Server Setup_ section. #### Download and install SitePush plugin Download and install SitePush on one version of your site as per normal. #### Update wp-config.php In most cases you will need to update the wp-config.php file for each site you are pushing to. Because you are likely running different versions of sites at different URLs, you need to tell WordPress to override the `WordPress Address` and `Site Address` options. To do this, add definitions for the `WP_HOME` and `WP_SITEURL` constants in your wp-config.php file. For more information about this please see the [WordPress codex](https://codex.wordpress.org/Editing_wp-config.php#WordPress_address_.28URL.29). #### Sites config file In addition to configuring SitePush’s settings page, you will also need to create and some settings files as described in this and the following sections. If at all possible upload these files outside of your web root so they are not accessible from a web browser. If that is not possible, make sure the file names end in ‘.php’ and that you include the first line from the sample files. The sites config file contains information about all the sites you wish to push/ pull between. It looks like this:- ``` ; -*- conf -*- [all] wp_dir = /wp wp_content_dir = /wp/wp-content cache = no caches[] = /caches/timthumb caches[] = /caches/something_else [live] label = Live Site domains[] = live.example.com domains[] = live.example.co.uk web_path = /var/www/vhosts/mysite-live db = live live = yes [dev] label = Dev Site domain = dev.example.com web_path = /var/www/vhosts/mysite-dev db = dev live = no ``` Each section represents parameters for a web site, with the exception of _[all]_– parameters in this section apply to all sites. Required parameters are as follows:- * **[sitename]** = a unique name for this site. It’s only used internally (or as label if you don’t supply the label parameter), and can be anything you like. * **web_path** = the full filesystem path to the web root for the site (not the root of the WordPress install if you have WordPress in a subdirectory). * **domain** = the domain this site is at. If the site uses more than one domain, use the domains[] parameter for each domain instead. Optional if domains[] parameters supplied. * **domains[]** (optional if domain parameter supplied) = if your site can be accessed via multiple domains (e.g. example.com, example.co.uk) then list each domain with the domains[] parameter. Make sure you include the _[]_. * **db** = the SitePush label of the database this site uses, as defined in your databases config file (see below). The following parameters are optional:- * **label** = label for your site used in menus, error messages etc. The label doesn’t have to be unique, but it will be rather confusing if it’s not. * **wp_dir** = the path from your webroot to this sites WordPress install. You shouldn’t need to set this unless * **wp_content_dir** = the path from your webroot to the site’s wp-content directory. You shouldn’t need to set this. * **wp_plugin_dir** = the path from your webroot to the site’s plugins directory. You shouldn’t need to set this. * **live** = is this a live/production site (_yes_), or not (_no_). SitePush will show some warnings when you select a live site to push to, can prevent users logging into live sites and can activate/deactivate specific plugins on live sites. Defaults to no. * **default** = if set to yes, SitePush will use settings for this site if it can’t figure out what config to use for a site. This should be set at most for one site. Defaults to no. * **cache** = is caching turned on for this site (yes or no). If you have set _WP\ _CACHE_ to TRUE in your wp-config for this site, you should set this to yes. Defaults to no. * **caches[]** = if your site has any cache directories which should be cleared when you update the site, enter the full filesystem path to those directories here, and SitePush will empty those directories whenever you push if the _Clear cache on destination_ option is set when you push. * **admin_only** = if only admins should be able to push to/pull from this site, then set to _yes_. Defaults to no. * **source_only** = if set to yes, non-admins will not be able to push to this site. Defaults to no. * **destination_only** = if set to yes, non-admins will not be able to push from this site. Defaults to no. Don’t include a trailing slash on any paths. #### Databases config file The databases config file contains information about your sites’ databases. ``` ; -*- conf -*- ; Do not remove the above line, it is all that prevents this file from being downloaded. [all] prefix = wp_ [live] name = live_database user = db_user pw = live_db_password [dev] name = dev_database user = db_user pw = dev_db_password ``` Each section represents parameters for a WordPress database, with the exception of _[all]_ – parameters in this section apply to all sites. Required parameters are as follows:- * **[dblabel]** = a unique label for this database. This label is used for the _db_ parameter in the sites config file. * **name** = the name of the database (same as _DB\_NAME_ in wp-config). * **user** = the user name for accessing the database (same as _DB\_USER_ in wp- config). * **pw** = the database password (same as _DB\_PASSWORD_ in wp-config). The following parameters are optional:- * **host** = the database host. Defaults to DB_HOST. **NOTE** All databases you are pushing to/from must use the same prefix. #### Domain map config file If you are running a Multisite installation, you will also need to create a domain map file so that SitePush knows which domains apply to which sites. The file should have as many sections as you have SitePush sites defined in your sites config file, and each section should contain one entry for each blog in your multisite setup. If your multisite installation is set up as a subdomain install, then you should list the full domains for each site, for example:- ``` ; -*- conf -*- ; Do not remove the above line, it is all that prevents this file from being downloaded. [live] 1 = site1.example.com 2 = site2.example.com 3 = site3.example.com [dev] 1 = dev1.example.com 2 = dev2.example.com 3 = dev3.example.com ``` * **[sitename]** = the name you have given this site. It should be exactly the same as _[sitename]_ in your sites config file. * **blogid = domain** = define the primary domain for each blogid in your network. If you are using a sub-directory set up, then the domain would be the same for each blog, but you still need to enter it for each one. If, on the other hand, your installation is set up as a subdirectory install, then the domains in each section will be the same, for example:- ``` ; -*- conf -*- ; Do not remove the above line, it is all that prevents this file from being downloaded. [live] 1 = live.example.com 2 = live.example.com 3 = live.example.com [dev] 1 = dev.example.com 2 = dev.example.com 3 = dev.example.com ``` ** do not include the subdirectory path for each site ** If you do not configure this correctly, you will not be able to access blogs where you have pushed multisite tables (or if you pushed the whole database) and may have problems accessing individual blogs where you pushed options for that blog. If this does happen, you will need to manually edit the wp_blogs, wp_site, wp_sitemeta and options tables, or restore from a backup. #### Other Important Notes for Multisite Setups 1. Support for Multisite is experimental and to enable it you will need to define SITEPUSH_ALLOW_MULTISITE as TRUE in wp-config. There may be some rough edges and note that SitePush has not been thoroughly tested on Multisite configurations, so make sure you have appropriate backups. 2. SitePush settings for each blog are independent, so you will need to configure each blog separately. Each blog will probably need its own sites config file (as domains and/or subdirectories will be different for each blog), but can and should share a common database config file. The domain map config file should also be common amongst all sites. 3. SitePush uses the term _site_ to distinguish between different versions of a site– e.g. live, staging, development. A SitePush site is not the same as a Multisite site (which is actually a network of blogs). A standard Multisite setup normally only has one site but many blogs (so really it should be called a Multiblog setup…). 4. If you have a large Multisite network, you should probably avoid pushing all tables… if it takes too long the script may time out and you may be left with an incomplete database. 5. In Multisite setups, only Super Admins can administer SitePush. ## FAQ Can I push between sites running different versions of WordPress? Pushing files between sites running different versions of WordPress should not be a problem. Pushing databases between sites running different versions of WordPress is not recommended. However, as long as there are no structural changes to the database which would cause backward compatibility problems, then it should work fine. The first time you go to wp-admin after a push, WordPress will probably tell you it needs to update the database. SitePush complains that it can’t find mysql/mysqldump/rsync Make sure you enter the complete absolute path to the actual file binary/executable, not just the directory it is in. For example:- * `C:/wamp/bin/mysql/mysql5.6.12/bin/mysql.exe` * `/Applications/MAMP/Library/bin/mysql` * `/usr/bin/mysql` Note – these paths are just examples, they may be different on your system. Does SitePush have to be running on sites I push to? SitePush should normally be installed and running on all sites you are pushing to and from. SitePush can push files and database tables to a site even if that site is not running SitePush, however, some important aspects of SitePush require that it is running on sites you push to. If SitePush is not running on a site, the following will not work:- * fix site urls * preventing login to live sites * clearing cache after a push * activating/deactivating plugins If you don’t want SitePush to show in wp-admin for a particular site, define `SITEPUSH_HIDE` to true in the wp-config.php file for that site. SitePush isn’t updating my database after a push This is by design – SitePush avoids making any changes to the database unless absolutely necessary. Currently the only changes made are on multisite installs where the database needs to be updated to ensure each site has the correct URL. Note that the _Fix site URLs_ option does not actually make any changes to the database– if activated it replaces incorrect URLs as they are output to the screen. Can I use SitePush to move my site to a new server, or to backup my installation? In theory you probably could, but it’s likely more effort than it’s worth – SitePush is designed to make it really easy to repeatedly move database and files between sites, not for a one off move or automated backup. If you are looking for a plugin to do this, you could use something like [WordPress Move](https://wordpress.org/extend/plugins/wordpress-move/) or [WP Remote](https://wordpress.org/extend/plugins/wpremote/) or [BackupWordPress](https://wordpress.org/extend/plugins/backupwordpress/). How do I use SitePush on my Multisite installation Support for Multisite is experimental. You can enable it by defining SITEPUSH_ALLOW_MULTISITE as TRUE in wp-config. SitePush should work OK with Multisite setups, but there may be a few rough edges and it has not been thoroughly tested, so make sure you have appropriate backups. How do I push custom tables created by another plugin? You can add groups of custom tables to be pushed in the “Custom DB table groups” option on the main settings screen. SitePush times out before pushes complete By default, SitePush will run for up to 10 minutes to push. If your push is taking longer than that, you are either trying to push a very large database, a lot of large files or something is wrong. [Repairing and optimizing your database](http://dev.mysql.com/doc/refman/5.5/en/mysqlcheck.html) can help. Also, some web hosts have proxy servers with their own timeouts – if they time out in less than 10 minutes, there’s nothing SitePush can do to lengthen the timeout. If you do have problems with timeouts, you can also try pushing things separately. ## Mga Review Wala pang reviews para sa plugin na ito. ## Mga Contributor at Developer Ang “SitePush” ay open source software. Ang mga sumusunod na tao ay nag-ambag sa plugin na ito. Mga Contributor * [ Mark Rowatt Anderson ](https://profiles.wordpress.org/markauk/) [Isalin ang “SitePush” sa iyong wika.](https://translate.wordpress.org/projects/wp-plugins/sitepush) ### Interesado sa development? [Tingnan ang code](https://plugins.trac.wordpress.org/browser/sitepush/), i-check ang [SVN repository](https://plugins.svn.wordpress.org/sitepush/), o mag-subscribe sa [development log](https://plugins.trac.wordpress.org/log/sitepush/) sa pamamagitan ng [RSS](https://plugins.trac.wordpress.org/log/sitepush/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.4.2 (2013-09-09) * Allow pushing between two databases with same name if the databases are on different hosts. (props wethanet) * Fix bug preventing push if database configs have different names from site configs. * Add admin option to hide specific push options for all users. Useful for preventing accidental pushing of, say, comments tables if you never want them pushed. * Add action hooks so you can run custom code before and after pushing. Note that these hooks only run from the site you are pushing from. See classes/class-sitepush- plugin.php for more info. * Don’t allow SitePush to be added to the list of plugins to deactivate. * Fix PHP Notice. #### 0.4.1 (2012-11-13) * Bugfixes relating to URL replacement when pushing multisite installs. * Improvements to URL replacement, SitePush now replaces URLs in widgets, nav_menus and any URL passed through clean_url(). #### 0.4 (2012-09-06) * SitePush no longer depends on rsync to push files. If you don’t have rsync on your server, SitePush will copy files using PHP. * You can now define custom groups of database tables to push, allowing any custom tables created by plugins to be pushed without pushing the whole database. * Added debug mode which lists information about your environment at the top of the options screen. Add define(‘SITEPUSH_DEBUG’,TRUE); to your wp-config.php file to enable debug mode. * Detect various problems with hosting setups and add more helpful error messages. * Various bug fixes. #### 0.3 (2012-07-06) * Initial public alpha release. ## Meta * Bersyon **0.4.2** * Huling na-update **13 taon ang nakalipas** * Mga aktibong installation **20+** * Bersyon ng WordPress ** 3.3.1 o mas bago ** * Sinubukan hanggang **3.6.1** * Wika * [English (US)](https://wordpress.org/plugins/sitepush/) * Mga Tag * [deployment](https://tl.wordpress.org/plugins/tags/deployment/)[development](https://tl.wordpress.org/plugins/tags/development/) [migrate](https://tl.wordpress.org/plugins/tags/migrate/)[migration](https://tl.wordpress.org/plugins/tags/migration/) [move](https://tl.wordpress.org/plugins/tags/move/) * [Advanced View](https://tl.wordpress.org/plugins/sitepush/advanced/) ## Mga Rating 4.7 out of 5 stars. * [ 14 5-star reviews ](https://wordpress.org/support/plugin/sitepush/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/sitepush/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/sitepush/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/sitepush/reviews/?filter=2) * [ 1 1-star review ](https://wordpress.org/support/plugin/sitepush/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/sitepush/reviews/#new-post) [Tingnan lahat ng review](https://wordpress.org/support/plugin/sitepush/reviews/) ## Mga Contributor * [ Mark Rowatt Anderson ](https://profiles.wordpress.org/markauk/) ## Suporta May gusto kang sabihin? Kailangan ng tulong? [Tingnan ang support forum](https://wordpress.org/support/plugin/sitepush/)