Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Great find.
    Many thanks

    Hope I’m talking about the same thing here – I have a problem with a WordPress Multisite setup – sharing the 1 database.
    The problem occurs when I switch on the plugin’s Enable Hide Backend feature.
    With this feature on I can’t login into the dashboard on any of my ‘child’ sites – only the master site.
    Looking at the .htaccess file with the feature enabled – gave me and idea to why this may be the case…? Here’s the file (domain name and key have been changed):

    # BEGIN Better WP Security
    <IfModule mod_rewrite.c>
    RewriteEngine On
    
    RewriteRule ^login/?$ /wp-login.php?magickey [R,L]
    
    RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in_.*$
    RewriteRule ^admin/?$ /wp-login.php?magickey&redirect_to=/wp-admin/ [R,L]
    
    RewriteRule ^admin/?$ /wp-admin/?magickey [R,L]
    
    RewriteRule ^register/?$ /wp-login.php?magickey&action=register [R,L]
    
    RewriteCond %{SCRIPT_FILENAME} !^(.*)admin-ajax\.php
    RewriteCond %{HTTP_REFERER} !^(.*)mydomain.com/wp-admin
    RewriteCond %{HTTP_REFERER} !^(.*)mydomain.com/wp-login\.php
    RewriteCond %{HTTP_REFERER} !^(.*)mydomain.com/login
    RewriteCond %{HTTP_REFERER} !^(.*)mydomain.com/admin
    RewriteCond %{HTTP_REFERER} !^(.*)mydomain.com/register
    RewriteCond %{QUERY_STRING} !^magickey
    RewriteCond %{QUERY_STRING} !^action=logout
    RewriteCond %{QUERY_STRING} !^action=rp
    RewriteCond %{QUERY_STRING} !^action=register
    RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in_.*$
    RewriteRule ^.*wp-admin/?|^.*wp-login\.php not_found [L]
    
    RewriteCond %{QUERY_STRING} ^loggedout=true
    RewriteRule ^.*$ /wp-login.php?magickey [R,L]
    </IfModule>
    
    # END Better WP Security

    Would the RewriteCond lines that all refer to the ‘master’ domain be a possible reason for not being able to login to the ‘child’ domains? None of the child domain folders have htaccess files in them of their own so would it not read the master htaccess?

    I could be barking up the wrong tree completely here..

    Thread Starter thehobbo

    (@thehobbo)

    I find the comment ‘use a non-inline WYSIWYG editor’ really unhelpful. I want an inline editor.
    The javascript error was specific only to a particular paid theme – certainly don’t expect all themes to work out the box nor support for specific themes.
    Z-index issues are present on most themes in one way or another.
    For example with theme Twenty Eleven 1.3 there’s a z-index issue when the you edit a featured image on a page. The inline toolbar floats behind the image as it’s z-index is 102 and the theme sets the image’s at 9999.
    Plus – on any theme – the tooltips on the toolbar are behind the toolbar.

    Thread Starter thehobbo

    (@thehobbo)

    Aesqe

    I’m using WP v3.2.1 and v1.6.5.6.

    Is there a reason you only assign the rel tag when link-to is set to file? Seems an odd decision.

    I’m currently getting around it using jquery which seems dirty:

    $('.gallery a').each(function () {
        this.rel = 'set';
    })

    Thanks

    Thread Starter thehobbo

    (@thehobbo)

    Thanks for the replies.
    I assumed all posts would be retrieved if no numberposts value given.
    Seems odd that by querying with &numberposts= with no value returns all…

Viewing 5 replies - 1 through 5 (of 5 total)