Forum Replies Created

Viewing 15 replies - 61 through 75 (of 212 total)
  • Hey ChetanBuddh,

    There is no way someone can help with so little info. There could be something wrong with your setup, but I’m 99,99% sure it is not a bug in WordPress.

    I’d suggest that you try to deactivate plugins, switch to the default theme and try again. If it still doesn’t work, then at least you already know it’s not caused by a plugin or theme.

    Hey filmguy_157,

    CNAME works in the same way as a wildcard. In fact, a wildcard could be a CNAME. But if your wildcard works correctly, you indeed do not need a CNAME. If your wildcard works correctly then you should be able to reach sub.domain.com.

    I’ve no clue what could be wrong with the domain mapping though.
    Did you add an A record with the IP of the server in the DNS of domain2.com?

    This would have the following data (may be different depending of registrar):

    • Type: A
    • Name: domain2.com or @
    • Value: IPv4 of your server (received from host)
    • TTL: the same as the rest should do

    When you just changed your DNS, it can take a while tot propagate. You can check that with online tools like WhatsMyDNS.net.

    I hope this helps, GL!

    Hey luggie,

    It’s hard to have a clue with so little information. Perhaps a link to the sites could make it easier to help.

    I would guess it’s something wrong in your database, but since you say “some sites”, do you mean all sites in one multisite?

    If it’s your database perhaps this plugin will be able to repair it. Or you can try with WordPress’ built in functionality, WP_ALLOW_REPAIR, or through phpMyAdmin.

    It could be something else too though, but that is probably where I would start to look.

    GL with it!

    Hey amoest,

    I’ve no experience with these plugins, but it probably means they are not compatible. Considering the post date, the networkwide menu may also be a little outdated. Perhaps you could try a different plugin, f.ex. Multisite Shared Menu.

    I never tried that one either though, but if it’s not compatible and if you’re lucky, perhaps the author will be willing to change that.

    I hope this helps. GL with it!

    Hi tschmid4,

    You can have a .htaccess file in every directory. I can’t say I understand the structure of your site, but the ones that are present already are used by Akismet. You can simply leave these where they are.

    To enable multisite you need to make a change to the .htaccess file in the root of your WordPress installation. That is where you also find your wp-config.php, as well as the folders wp-admin, wp-content and wp-includes.

    If there is no .htaccess in your root, you probably did not enable pretty permalinks yet. This is recommended.

    If you did, or you can’t and you still do not have an .htaccess file you can create one yourself with the following content. This is for a single installation:

    # 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

    In case you have trouble creating such file (without a filename) you can give it a name, f.ex. a.htaccess, and rename after you upload it through FTP.

    When you activate multisite WordPress will present you with new content for this .htaccess file. You can paste this between # BEGIN WordPress and #END WordPress.

    More information about this can be found in the Codex and here is a good read for a more in depth introduction to .htaccess. Beware though, not everything written there will suite your install. Always keep a backup when you replace this file.

    I hope this helps. GL with it!

    Thread Starter Axel13

    (@axel13)

    I didn’t repair the tables yet, but the last backup logs don’t have this warning. I do have a database error too regularly though. Restarting the server solves it. Still need to dig into this. I’ll look into innodb. TY!

    Thread Starter Axel13

    (@axel13)

    While not all problems are resolved, I will mark this thread as resolved, because it’s too chaotic.

    The current conclusion is that Simple Firewall is not entirely compatible with multisite yet:

    • User management causes problems and can best be turned off.
    • It’s not possible to change the login URL and it doesn’t help to use a different plugin for this.
    • 2FA can be used, but requires authentications for all sites seperately
    • When ‘Report Email’ is left empty reports are sent to the site admins, not to the network admin.

    Sounds like quite a promising plugin, @jasonhendriks. I’m looking forward to try it out.

    I probably should try it before giving feedback, so I apologize in case I drop the ball, but I tend to think the suggestion by @webnashr would not work well for many multisites. It would be nice to be able to enable it network wide, so all email is sent through the network setting, unless a subsite wants to use a different email. It would then also be good if the subsites can add their own settings, without seeing the default settings.

    E.g. I have one site where visitors can make a reservation. The confirmation email would preferably be sent by an email address from the corresponding domain. Another site only sends email when someone f.ex. resets a password. For this site it would be good enough to use the network settings.

    Either way, thank you for your dedication to make it awesome. That’s a joy.

    Hey Mariana & Wallace,

    It’s best to start a new topic when you run into a problem.
    This makes the follow up easier, one issue at a time and this way the person starting a topic can indicate that it is resolved.

    That said, I’ll be short. If you need more help, please start a new topic. You can do so at the end of every category.


    Mariana,

    1. Access your site through FTP, f.ex. with FileZilla, or through cPanel’s file manager.
    2. You can find the file wp-config.php in the root of your WordPress directory.
    3. Download it and open it in a text editor, f.ex. Notepad (not an office program).
    4. Scroll down untill where you see: /* That’s all, stop editing! Happy blogging. */
    5. Before that, add this:
    define( 'WP_MEMORY_LIMIT', '96M' );
    6. Save and upload back to the WordPress root, replacing the other one.

    In case the problem would occur again, you can increase ’96M’.
    More info can be found here.


    Wallace,

    The code in your .htaccess file is not correct for multisite. If that is the code you got after allowing multisite, that is weird and there may be something else that needs to be solved first.

    You could try to replace it though, but which code to add depends on your setup: subdomain or subfolder. You have chosen this upon activating and you can find/pick the correct .htaccess code here.

    If that does not work, replace it with the initial .htaccess code again, remove “define( ‘WP_ALLOW_MULTISITE’, true );” from wp-config.php to set your site back to a single install and find out what needs to be solved first, or what you may have overlooked.

    F.ex. Did you deactivate your plugins before you made the switch?

    I hope that helps.
    Good luck!

    Yes, multisite is surely a good option.

    2 more considerations though:

    – As far as I know it is not possible to limit bandwidth on multisite. I never looked for it though, so I could be wrong.

    – Some plugins are not compatible with multisite. However, these are a minority and the good ones already are, or are working on it. The only thing I’m still missing is two-factor authentication, but I did not try all the options yet.

    Apart from that I can’t think of a reason not to use multisite. I personally love it.

    Grtz!

    Hey nostradame37,
    Here you go.
    GL with it!

    Hey Max,

    I think multisite would work well for this, but it depends on what hosting you wish to use. If you think of f.ex. VPS, multisite could be perfect, else you can use something like iControlWP.

    GL with it!

    You can use the same theme and plugins, but adding the same content to every site is not obvious. You could try through RSS if you use posts, but it’s still different. If you want 4 copies of the same site, it would probably be easier to make one site and point the 4 domains to it, f.ex. with this plugin. This allows to set a different site title and tagline.

    If you want anything else to be different you could try to change it in your theme (> make a child theme if you use a 3rd party theme) with an if statement.

    I think something like this could work:

    $domain = $_SERVER['HTTP_HOST'];
    if($domain == "your1stdomain.tld" ) {
        *your 1st item goes here*
    }
    else if($domain == "your2nddomain.tld" ) {
        *your 2nd item goes here*
    }
    else if($domain == "your3rddomain.tld" ) {
        *your 3rd item goes here*
    }
    else if($domain == "your4thdomain.tld" ) {
        *your 4th item goes here*
    }

    However, from an SEO perspective it is very bad practice to have different sites with the same content. If you do that you should make sure to add a canonical URL to every page and post. You could do this with Yoast SEO.

    I hope that makes sense.
    GL with it!

    Thread Starter Axel13

    (@axel13)

    I turned off 2FA, yet still got logged out when trying to get to the admin of another site. The error message was:

    You do not currently have a WordPress Simple Firewall user session.
    Please login again.

    This solves when turning off user management.

    I then turned 2FA back on to see if that would perhaps solve the problem, but that’s not it. The symptoms remain the same.

    Thread Starter Axel13

    (@axel13)

    Found some more inspiration: testing “Two-Factor Login Authentication By IP Address”…

    It’s an improvement, but it is still necessary to authenticate for every site separately, with dynamic IP’s that is far from practical and when clicking the auth link, I end up on the sub site’s login screen, where login fails: a message appears saying smth like “login was successful and you will be redirected…”, but it redirects back to the login screen (without error message – tried on Chrome).

    After logging in on the main site, however – here comes the improvement – I can reach the site I authenticated for.

Viewing 15 replies - 61 through 75 (of 212 total)