If I understand it correctly, you’re trying to restrict access to your site while you’re building it. So visitors not logged in see some sort of maintenance mode page, while logged in visitors can access the dashboard and see the front-end while they develop? I think your best route is to use a plug in. … Read more
First, change this: include TEMPLATEPATH . ‘/extras/shortcodes.php’; …to this: include ( TEMPLATEPATH . ‘/extras/shortcodes.php’ ); Second, change TEMPLATEPATH to get_template_directory(): include ( get_template_directory() . ‘/extras/shortcodes.php’ ); (The TEMPLATEPATH and STYLESHEETPATH globals are going away eventually.) Third, make sure you namespace your function names properly. Function names “alertBox()” and “infoBox()” are far too generic. Beyond that, … Read more
If you are running Nginx, it is easier to implement a similar scenario with an isolated server running Nginx alone. In Nginx, the HttpUpstreamModule can be configured to divert the traffic to a completely different domain running on a different server. For example, if your site is yoursite.com, it is easy to divert the visitors … Read more
Check for a .maintenance file (if so, delete it) in your wp root and also check your .htaccess file
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