WordPress.org

Ready to get started?Download WordPress

Forums

Ultimate Coming Soon Page
[resolved] Does not work when WP is in a subfolder (13 posts)

  1. eaglejohn
    Member
    Posted 1 year ago #

    I've installed WordPress in a subfolder called 'wp'. When I'm logged in, I'm seeing the 'coming soon' page instead of the regular website pages. I'm having this issue on several servers, so I guess it's a plugin bug?

    http://wordpress.org/extend/plugins/ultimate-coming-soon-page/

  2. John Turner
    Member
    Plugin Author

    Posted 1 year ago #

    Hi,

    Yes it does work in a sub folder. Make sure you have you site url correctly set under settings and htaccess set up correctly. http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    A misconfigured subfolder install can make the WordPress function is_user_logged_in return false. http://codex.wordpress.org/Function_Reference/is_user_logged_in

    This is the function the plugin uses to either show the site or the coming soon page.

  3. eaglejohn
    Member
    Posted 1 year ago #

    I think I set everything correctly

    My WP-settings:
    WordPress Address (URL): http://www.domain.com/wp
    Site Address (URL): http://www.domain.com

    index.php in root folder:
    require('./wp/wp-blog-header.php');

    index.php in /wp folder:
    require('./wp-blog-header.php');

    .htaccess file in root folder:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
    
    php_value memory_limit 128M

    .htaccess file in /wp folder:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress
    
    php_value memory_limit 128M

    Any suggestions?

  4. John Turner
    Member
    Plugin Author

    Posted 1 year ago #

    Add the line:

    var_dump(is_user_logged_in());

    to the file inc/config.php on line number 58.

    This should output true when you are logged in and false when not. If it returns false when you are logged in then something is still not configured properly.

  5. eaglejohn
    Member
    Posted 1 year ago #

    After adding the code on line 58 the output bool(false) is displayed when logged in and logged out. Like you say there's probably something not configured properly, but I can't figure out what... :/

  6. John Turner
    Member
    Plugin Author

    Posted 1 year ago #

    Sorry, I'm not sure what it is. I've seen someone else with this issue and I can't remember how they solved it :(

  7. paulsanduleac
    Member
    Posted 1 year ago #

    Same issue here, any fix?

  8. paulsanduleac
    Member
    Posted 1 year ago #

    For me it started working after I refreshed my permalinks.

  9. lnv77
    Member
    Posted 1 year ago #

    Hi, has anybody got this working yet? I've tried refreshing the permalinks to no avail. I have the same directory setup as the first poster. Any help would be superb!

  10. John Turner
    Member
    Plugin Author

    Posted 1 year ago #

    If you have a subfolder install, make sure you have follow these instruction.

    http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    Otherwise post a more detailed description of your issuer.

  11. lnv77
    Member
    Posted 1 year ago #

    Hi John, I followed those instructions exactly and it worked fine. The problem is that even though I am logged in I still see the Coming Soon page instead of the actual site. What do you think? Thanks.

  12. John Turner
    Member
    Plugin Author

    Posted 1 year ago #

    This mean then that the WordPress function is_user_logged_in() is not working properly
    http://codex.wordpress.org/Function_Reference/is_user_logged_in

    This is caused by a mis-configure WordPress or another plugin breaking it.

  13. lnv77
    Member
    Posted 1 year ago #

    Thanks John, I deleted the other 2 plugins I had running and it worked. Cheers.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.