How to make wordpress blog completely invisible to public [Not Private] -

-

i want close wordpress blog have public , keep myself.

i know can set private shows uggly log-in page , dont want people trying access (using random usernames/pass etc) or think still open members accounts or that.

i blog point " server not found " public , when logged in admin able see posts , backend aswell frontend.

how can make possible?

my suggestion following:

function is_login_page() {     return in_array( $globals['pagenow'], array( 'wp-login.php', 'wp-register.php' ) ); }  function wpse_make_blog_private() {     if ( ! is_user_logged_in() && ! is_admin() && ! is_login_page() ) {          global $wp_query;         $wp_query->set_404();     } } add_action( 'wp', 'wpse_make_blog_private' );

it show 404 on pages still allow login. logged in users see site normal.

on request show broken site add following code functions.php. aware instead of code above.

function is_login_page() {     return in_array( $globals['pagenow'], array( 'wp-login.php', 'wp-register.php' ) ); }  function wpse_make_blog_private() {     if ( ! is_user_logged_in() && ! is_admin() && ! is_login_page() ) {          die();     } } add_action( 'wp', 'wpse_make_blog_private' );

you have option of using wp_die instead add error message minimal styling. see: https://codex.wordpress.org/function_reference/wp_die


Comments

Post a Comment

Popular posts from this blog

php - Magento - Deleted Base url key -

-
i working on cleaning url: http://mydomain.com/shop/shop/deals i going through settings in configuration tab in admin panel on magento , change secure , unsecure base urls remove first base url "shop" web page read: http://mydomain.com/shop/deals so changed unsecure base urls mydomain.com/shop mydomain.com , secure 12.345.67.89/shop 12.345.67.89. wrong thing do. i cannot reload page or admin console. how access these files through ftp , change correctly there?? when make changes in admin panel changes made in database not in file. have make changes in database. 1.go database , select core_config_data table under table find web/unsecure/base_url , web/secure/base_url . make changes here. don't forget clear cache in var/cache folder
Read more

javascript - Tooltipster plugin not firing jquery function when button or any click even occur -

-
i want use tooltipster plugin click element in body show tooltip , want have close button inside tooltip close it. however use jquery click() function handle won't fired. tried solution in post. worked when tooltip triggered hover event. tooltipster plugin not firing jquery function when link in in tooltip clicked the original solution using hover in jsfiddle trigger: 'hover', instead using click show tooltip trigger: 'click', http://jsfiddle.net/bcqyl/7/ it won't fire click event in jquery block. can captured normal javascript function only. checked should code in tooltipster plugin locked , captured "click()" event inside tips when in click trigger mode. i tried other event onchange event of radio button fired when using code in original solution @evan right. tooltip doesn't exist in dom , can't bind/delegate action (even if go way $(document) after domready). if you're after close button inside of too...
Read more

java - WrongTypeOfReturnValue exception thrown when unit testing using mockito -

-
my test list<person> mylist; @test public void testisvalidperson() { mylist = new arraylist<person>(); mylist.add(new person("tom")); when(persondao.get(person)).thenreturn(mylist); when((persondao.get(person)).isempty()).thenreturn(false);//------exception thrown boolean result = service.isvalid("tom"); assertfalse(result); } method tested: public boolean isvalid(string person){ persondao = new persondao(); person personobj = new person(person); return (persondao.get(person).isempty())?false : true; } exception thrown: org.mockito.exceptions.misusing.wrongtypeofreturnvalue: boolean cannot returned get() get() should return list *** if you're unsure why you're getting above error read on. due nature of syntax above problem might occur because: 1. exception *might* occur in wrongly written multi-threaded tests. please refer mockito faq on limitations of concurrency testing. 2. sp...
Read more