After seeing your clarification in the original question: Every page inside the subsite you’re trying to “hide” would need to be set so that only users with the permission level of “Admin” can see the page. Anyone will be able to see that the page exists. Users are not logged in or are logged in … Read more
When you submit a plugin to WordPress.org, you need to put everything in a zip file that you must put on your server. After validate it, you receive a mail with the new svn link for the validated plugin. Readme.txt link all images to à folder called assets where banner, screenshots, logo take place. For … Read more
Not quite the solution I was expecting, but I found another plugin that handles Service Worker much better and adds the features I needed, though I have to list posts manually rather than programmatically. The better plugin is Above The Fold Optimization (ignore the 1 star reviews, it’s one of those plugins where if you … Read more
I think you should check for some other platform. WordPress is made to be live all the time : ) But if you are really keen in doing it in WordPress I can suggest a hard way of doing it. You can use the JSON-REST-API for WordPress and jQuery Mobile to build a mobile app … Read more
Your easiest route is probably to use a plugin like Restricted Site Access (disclaimer: written by my boss) to redirect a user who isn’t logged in elsewhere, like the network home or something else. There are a few other similar plugins out there. Another option would be to take the code you say you’d put … Read more
Try this in wp-config.php: define( ‘WP_HTTP_BLOCK_EXTERNAL’, true );
You should install any program – for example MAMP – that allows you to use Apache and MySQL. Then go to wordpress.org and download the latest copy of WordPress. Install it and upload your theme in the wp-content/themes folder.
I’m in the same boat, and I’m still figuring out what the best “approach” should be. It is not necessary to cache any of the WordPress core files (/wp-includes, /wp-admin, etc). You will have to cache some files that live in your theme. Stuff like the css, js, and any image resources you use in … Read more
I have found the answer… well to my situation anyway. It was something related to multisite. Removing the following from wp-config.php got it to work for me. Removed define(‘WP_ALLOW_MULTISITE’, true); define( ‘MULTISITE’, true ); define( ‘SUBDOMAIN_INSTALL’, false ); $base=”https://wordpress.stackexchange.com/”; define( ‘DOMAIN_CURRENT_SITE’, ‘www.mywebsite.co.uk’ ); define( ‘PATH_CURRENT_SITE’, “https://wordpress.stackexchange.com/” ); define( ‘SITE_ID_CURRENT_SITE’, 1 ); define( ‘BLOG_ID_CURRENT_SITE’, 1 ); … Read more
It totally depends on the types of changes being made. If you’re modifying a theme or a plugin, depending on what the changes are, you can likely build them locally or on a remote dev server, then push them to production with ease. That works for a user or two, with more users you need … Read more