Česlav Przywara

Hi, this exact problem has been fixed in version 4.0.7, but you had to resave your firewall rules for the fix to take effect – like you just did 😉

Cheers,
Česlav

Hi Joe,

Well, you can always edit the .htaccess file yourself to make it do whatever you want it 😉

If you have “hot links prevention” switched on for the root domain, .htaccess file in the root directory should contain the following snippet:

#AIOWPS_PREVENT_IMAGE_HOTLINKS_START
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} \.(gif|jpe?g?|png)$ [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.joere\.com [NC]
RewriteRule \.(gif|jpe?g?|png)$ - [F,NC,L]
</IfModule>
#AIOWPS_PREVENT_IMAGE_HOTLINKS_END

You should add one more line with HTTP_REFERER check for each of your addon domains, let me give you example for http://www.kenasplund.com/ :

RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.kenasplund\.com [NC]

But as I said, it’s not flexible solution. As soon as you make any changes to firewall settings via back-end and save them, your manual modifications will be lost.

Alternatively, you could disable image hot linking prevention and paste the manually crafted snippet via Custom Rules tab, but I just discovered there’s a bug that breaks the pasted code, if the custom rule contains any “\” (backslashes) – as in this case.

I’m not affiliated with the devs of this plugin, but I use it in every WP project I maintain, so I’m doing my best to help the devs with keeping up the good work 🙂

Cheers!
Česlav

Hello Joe,

Thanks for the detailed explanation!

If you activate image hotlinking prevention on the root domain and visit http://www.joere.com/kenasplund/ – are the images blocked as well?

If they are not blocked then I think I understand the cause of the problem and one possible solution to it would be to serve http://www.joere.com domain from a subfolder as well – I don’t know if your webhosting allows for such setup?

A bit of technical background: image hotlinking prevention uses mod_rewrite rules in .htaccess file. Any rules from such file are applied to all subdirectories as well, so in your case also to websites with another domains. Since the subdirectory domain does not match the root domain, the images are blocked – remember, you want to prevent image hotlinking, so it all works as advertised 😉 Unfortunately, I’m not aware of any simple way how to fix the .htaccess rules to support your setup and allow mixing of multiple domains. Serving the http://www.joere.com domain from subdirectory is the only solution I can think of. In such case, the .htaccess file will not affect other subdirectories (domains).

The problem with redirected domains has the same root. The rules in .htaccess file are tied to the http://www.ophmusic.com, so http://www.oneparthuman.net is treated as an unrelated domain and images are blocked. Here, my suggestion would be to do a true redirect using 301 status code (see an example how to achieve it via .htaccess). Another reason for such solution is to not feed Google with duplicate content.

As for the navigation buttons problem, the URL of the button image file must contain something that triggers bad query string or advanced character filter rule. One common problem is that filenames with “@” in them are blocked by advanced character filter. Anyway, if you apply my suggestion above (moving the site to subdirectory), the problem will resolve itself for the same reason (.htaccess rules would not be applied accross subdirectories).

If you cannot move http://www.joere.com to a subfolder, your only option is to ask your webhoster if there is a way to prevent applying rules from .htaccess files from parent directories in any directory that is acting as root directory for a separate (addon) domain. Actually, this is a very reasonable request…

Cheers,
Česlav

Hi alcon,

5G and 6G firewall rules are verbatim copy of .htaccess firewall rules compiled by Jeff Starr (see his posts about 5G and 6G for more technical background). Jeff itself is not associated with All in One WP Security & Firewall plugin, he just made his set of rules available to anyone, so they have been included in the plugin.

6G is meant to be updated version of 5G, but it is completely fine to use 5G instead of 6G, if you have troubles using the latter. However, it would be interesting to know, what rule is causing the problem at your website, so feel free to post a link to your website or a link to an image that has been blocked by 6G firewall.

Cheers,
Česlav

Hi joschi,

You should check the second argument ($sync) in function hooked up to the filter:

// copy selected post metas for polylang plugin
add_filter('pll_copy_post_metas', 'copy_post_metas', 10, 2);
function copy_post_metas($metas, $sync) {
  if ( $sync ) {
    // If syncing, ignore custom meta.
    return $metas;
  }
  else {
    // Otherwise (when creating new translation) copy custom meta.
    return array_merge(
      $metas,
      array(
        'konzertdaten_konzertdatum',
        'konzertdaten_konzertdatum_archiv'
      )
    );
  }
}

Hope that helps,
Česlav

Hi,

CPT name should be translated via __() function directly in the code that registers the CPT.

CPT slug translation is not offered by Polylang, you can try using Translate URL Rewrite Slugs plugin, although it is a bit out-dated (see the Issues and Pull Requests for more information).

Cheers,
Česlav

Hi Matt,

I’m glad I could help, but this is neither support forum for Divi theme nor for other plugins than Polylang 😉

Greetings,
Česlav

@marayapiraya I don’t know if you’re using Divi theme as mtyldesley? If not, provide more information on your theme/plugins or provide a link to pages where the problem occur.

Cheers,
Česlav