Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter magicmat

    (@magicmat)

    This is solved now, thanks

    Thread Starter magicmat

    (@magicmat)

    Thanks All!

    Thread Starter magicmat

    (@magicmat)

    Yeah, that’s great…although it did show it had permissions, but wasn’t showing. But great to get a breakdown of the permissions code.

    Any ideas why that occurred in Dec and Jan, but not before? Is it likely to reoccur?

    Thread Starter magicmat

    (@magicmat)

    Its now working! Thank you so much for your help….the 755 seems to have done the trick! Much appreciated!!!

    Thread Starter magicmat

    (@magicmat)

    I think December’s are working now if you check. It’s possible that WordPress couldn’t create your 2014/01 directory when it tried earlier this month. I’d try creating the 2014/01 directory and setting its permissions to 755.

    Sorry, my mistake, December WAS working, its only January that hasn’t. The directory is there on the FTP, and the images are viewable from there.

    Thread Starter magicmat

    (@magicmat)

    Thanks….the file now reads:

    # compress text, HTML, JavaScript, CSS, and XML
    AddOutputFilterByType DEFLATE text/plain
    AddOutputFilterByType DEFLATE text/html
    AddOutputFilterByType DEFLATE text/xml
    AddOutputFilterByType DEFLATE text/css
    AddOutputFilterByType DEFLATE application/xml
    AddOutputFilterByType DEFLATE application/xhtml+xml
    AddOutputFilterByType DEFLATE application/rss+xml
    AddOutputFilterByType DEFLATE application/javascript
    AddOutputFilterByType DEFLATE application/x-javascript

    # remove browser bugs
    BrowserMatch ^Mozilla/4 gzip-only-text/html
    BrowserMatch ^Mozilla/4\.0[678] no-gzip
    BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
    Header append Vary User-Agent

    # directory browsing
    Options All -Indexes

    ## EXPIRES CACHING ##

    ExpiresActive On
    ExpiresByType image/jpg “access plus 1 year”
    ExpiresByType image/jpeg “access plus 1 year”
    ExpiresByType image/gif “access plus 1 year”
    ExpiresByType image/png “access plus 1 year”
    ExpiresByType text/css “access plus 1 month”
    ExpiresByType application/pdf “access plus 1 month”
    ExpiresByType text/x-javascript “access plus 1 month”
    ExpiresByType application/x-shockwave-flash “access plus 1 month”
    ExpiresByType image/x-icon “access plus 1 year”
    ExpiresDefault “access plus 2 days”

    ## EXPIRES CACHING ##

    # 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

    Is that ok?!

    Thread Starter magicmat

    (@magicmat)

    Hmm, tried that, but nothing…do I need to give it any time?

    Thread Starter magicmat

    (@magicmat)

    Found it, thanks. So, all folders show write and read permissions with ticks. The only slightly odd thing is that Januarys and Decembers folders have a permissions code of 744, all of the others (that work) are 755. Should I change these?

    Thread Starter magicmat

    (@magicmat)

    WPRanger – Ive installed the plugin, how do I look at the results? Sorry…like I said…NOOB!

    Thread Starter magicmat

    (@magicmat)

    Hardeep, this is what it currently reads:

    # 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
    
    # compress text, HTML, JavaScript, CSS, and XML
    AddOutputFilterByType DEFLATE text/plain
    AddOutputFilterByType DEFLATE text/html
    AddOutputFilterByType DEFLATE text/xml
    AddOutputFilterByType DEFLATE text/css
    AddOutputFilterByType DEFLATE application/xml
    AddOutputFilterByType DEFLATE application/xhtml+xml
    AddOutputFilterByType DEFLATE application/rss+xml
    AddOutputFilterByType DEFLATE application/javascript
    AddOutputFilterByType DEFLATE application/x-javascript
    
    # remove browser bugs
    BrowserMatch ^Mozilla/4 gzip-only-text/html
    BrowserMatch ^Mozilla/4\.0[678] no-gzip
    BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
    Header append Vary User-Agent
    
    ## EXPIRES CACHING ##
    
    ExpiresActive On
    ExpiresByType image/jpg "access plus 1 year"
    ExpiresByType image/jpeg "access plus 1 year"
    ExpiresByType image/gif "access plus 1 year"
    ExpiresByType image/png "access plus 1 year"
    ExpiresByType text/css "access plus 1 month"
    ExpiresByType application/pdf "access plus 1 month"
    ExpiresByType text/x-javascript "access plus 1 month"
    ExpiresByType application/x-shockwave-flash "access plus 1 month"
    ExpiresByType image/x-icon "access plus 1 year"
    ExpiresDefault "access plus 2 days"
    
    ## EXPIRES CACHING ##

    Should I add your code?

    Thread Starter magicmat

    (@magicmat)

    This would suggest that hotlinking IS allowed, as would the fact that the other images are working:

    (Odd, URL not displaying)
    “Hotlinking”
    (also called “hot linking”, “leeching”, and “bandwidth theft”) is when a web page of one website owner is direct linking to the images or other multimedia files on the web host of another website owner (usually without permission, thus stealing bandwidth).

    When you have created an image or a multimedia file you usually want to protect it and control the use of it. You may not want people downloading your files and putting them on their own websites with little or no credit to yourself. Hotlinking is when other people use your files directly from your site, meaning that each time the file is viewed through their site, you lose bandwidth. This means that you could end up paying for the bandwidth.

    For all 123-reg.co.uk hosting customers there is an easy solution. We have the Rewrite Engine activated, which you can set up to analyse any incoming requests for files and deal with them appropriately.

    Using this facility is very easy. You simply need to create an .htaccess file, then add the following code:

    Thread Starter magicmat

    (@magicmat)

    But all other images ARE displaying correctly – would this still suggest its an anti-hotlinking issue?

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