Backlight 1.1 issue with arrows displaying now as boxes

dlangan · 2016-11-16 02:56:45

Hi there,

i've just searched the forums & don't see this issue posted.

I just upgraded to version backlight 1.1 & all the little arrows that existed on my webpages & in the admin panels have changed to little boxes (using Chrome). I'm guessing this isn't deliberate. Am I missing a font file or something?

I just checked Firefox & the appearance is worse - I think it's that missing image symbol.

Problem can be seen here http://www.deirdrelangan.com/TTG-TEST/about/ (beside Galleries)

Cheers
Deirdre

rod barbee · 2016-11-16 03:25:30

see this: http://community.theturninggate.net/vie … hp?id=6817

dlangan · 2016-11-16 20:04:50

Thanks Rod.

I'm not (yet) using redirection so the only thing that changed in my environment since it was working was the upgrade from 1.05 to backlight 1.1.

Regardless, I followed your advice & copied & pasted that code into my .htaccess file in my root www.deirdrelangan.com directory but it hasn't made any difference. Still, no arrows, just boxes.

I'm surprised that I'm the only one with this issue as I followed the installation instructions to a T!

All the best,
Deirdre

charlie.choc · 2016-11-16 21:49:39

I had the same problem for a while on my home page but it would go away when I cleared the template cache. It worked fine on every other page except my blog, but I resolved that by installing font awesome in Wordpress.

Matthew · 2016-11-16 22:39:36

Hi Deirdre,

I'm seeing some rather strange errors in your console log which indicate that your font files are not loading:

Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.woff2?v=4.7.0
(index):1 OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
(index):1 Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.woff?v=4.7.0
(index):1 OTS parsing error: incorrect file size in WOFF header
(index):1 Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.ttf?v=4.7.0
(index):1 OTS parsing error: FFTM: table overruns end of file
(index):1 Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.woff2?v=4.7.0
(index):1 OTS parsing error: Failed to convert WOFF 2.0 font to SFNT
(index):1 Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.woff?v=4.7.0
(index):1 OTS parsing error: incorrect file size in WOFF header
(index):1 Failed to decode downloaded font: http://www.deirdrelangan.com/backlight/modules/okapi-core/static/fonts/fontawesome-webfont.ttf?v=4.7.0
(index):1 OTS parsing error: FFTM: table overruns end of file

Honestly, I've never seen this error before and I'm not entirely sure what it's about. I Google, though, and I found a fellow saying this:

I just had the same issue – but with Font Awesome, which is a really well known font. Turned out this was caused by a problem with FTP. The file was uploaded as text (ASCII) instead of binary, which corrupted the file. I simply changed my FTP software to binary, re-uploaded the font files, and then it all worked.

So this might be an upload issue with your FTP client. Based on this, I would suggest that you check the transfer settings in your FTP client.

dlangan · 2016-11-16 23:10:08

Brilliant! Thanks a million Matthew!

I reloaded /home/backlight/modules/okapi-core/static/fonts as binary files & it's now looking good!

Much appreciated,
Deirdre

Matthew · 2016-11-16 23:12:09

Glad to hear!

Samoreen · 2016-11-20 22:23:35

rod barbee wrote:

see this: http://community.theturninggate.net/vie … hp?id=6817

Hi,

The .htaccess file installed when I started with BL already contains such code

# ------------------------------------------------------------------------------
# | Web fonts access |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts
...

Adding the code shown in the page pointed to by the above link while maintaining the existing code is certainly not a good idea (I tried) : after doing that, the Lightroom publisher plugin no longer works (all actions trigger an error - the plugin is no longer able to communicate with the web site).

I'm not familiar with the syntax used in .htaccess files so I'm wondering whether the existing code should be removed before adding the code suggested by the page mentioned above. Or is the mentioned post outdated ? Are these two pieces of code conflicting ?

Thanks.

==== Current contents of my .htaccess file ====== (this is actually the .htaccess file contained in the BL + Pages package)

# ------------------------------------------------------------------------------
# | Web fonts access |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts

<IfModule mod_headers.c>
<FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine On

############################################################################
# Edit this section for servers using FastCGI

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line
RewriteBase /

RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line and remove # from the line after)
RewriteRule ^.*$ - [E=BASE:%2]
#RewriteRule ^(.*)$ - [E=BASE:]

############################################################################

RewriteRule ^(.*)$ - [E=QS:mod_rewrite=on]

RewriteRule ^([^\/.]*)-single.php$ %{ENV:BASE}single.php?%{ENV:QS}&id=$1 [QSA,L]

RewriteRule ^([^\/.]*).css$ %{ENV:BASE}index.php?%{ENV:QS}&extension=css&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).js$ %{ENV:BASE}index.php?%{ENV:QS}&extension=js&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).gif$ %{ENV:BASE}index.php?%{ENV:QS}&extension=gif&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).png$ %{ENV:BASE}index.php?%{ENV:QS}&extension=png&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).jpg$ %{ENV:BASE}index.php?%{ENV:QS}&extension=jpg&name=$1 [QSA,L]

#RewriteCond %{QUERY_STRING} !mod_rewrite=on
#RewriteRule ^index.php$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^mobile.php$ %{ENV:BASE}mobile.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]

RewriteRule ^$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.*)$ %{ENV:BASE}index.php?%{ENV:QS}&page=$1 [QSA,L]

</IfModule>

dlangan · 2016-11-22 19:24:32

Hi there,

I'm now also experiencing problems with this .htaccess code. I added it as instructed & my new website & pages all look good but I'm now getting emails from clients complaining that they can't access their original web links.

After a bit of testing I've discovered that by restoring my original .htaccess file, I can now access my clients' weblinks. However, it's now broken a couple of my new website pages.

Here's my original .htaccess file (which breaks a couple of my new website pages):
Options -Indexes
AddHandler fcgid-script .php
FCGIWrapper "/dh/cgi-system/php56.cgi" .php

And here's my new .htaccess file (which breaks old client .htm weblinks)
Options -Indexes
AddHandler fcgid-script .php
FCGIWrapper "/dh/cgi-system/php56.cgi" .php

# ------------------------------------------------------------------------------
# | Web fonts access |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts

<IfModule mod_headers.c>
<FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine On

############################################################################
# Edit this section for servers using FastCGI

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line
RewriteBase /

RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$

# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line and remove # from the line after)
RewriteRule ^.*$ - [E=BASE:%2]
#RewriteRule ^(.*)$ - [E=BASE:]

############################################################################

RewriteRule ^(.*)$ - [E=QS:mod_rewrite=on]

RewriteRule ^([^\/.]*)-single.php$ %{ENV:BASE}single.php?%{ENV:QS}&id=$1 [QSA,L]

RewriteRule ^([^\/.]*).css$ %{ENV:BASE}index.php?%{ENV:QS}&extension=css&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).js$ %{ENV:BASE}index.php?%{ENV:QS}&extension=js&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).gif$ %{ENV:BASE}index.php?%{ENV:QS}&extension=gif&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).png$ %{ENV:BASE}index.php?%{ENV:QS}&extension=png&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).jpg$ %{ENV:BASE}index.php?%{ENV:QS}&extension=jpg&name=$1 [QSA,L]

#RewriteCond %{QUERY_STRING} !mod_rewrite=on
#RewriteRule ^index.php$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^mobile.php$ %{ENV:BASE}mobile.php?%{ENV:QS} [QSA,L]

RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]

RewriteRule ^$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.*)$ %{ENV:BASE}index.php?%{ENV:QS}&page=$1 [QSA,L]

</IfModule>

Any help much appreciated!
Deirdre

dlangan · 2016-11-22 19:40:08

Hi Patrick,

My original BL installation didn't include the .htaccess code as you describe it came with. However, I replaced my .htaccess code with your existing .htaccess file (what you describe came with BL originally) & now my conflicting problems (described above) with .htaccess has been fixed.

So, to answer your question, I'd suggest you ignore the mentioned post link which looks to be outdated & stick with what you've got (the .htaccess code that came with your installation of BL).

All the best,
Deirdre

Samoreen · 2016-11-22 19:47:51

dlangan wrote:

Hi Patrick,
My original BL installation didn't include the .htaccess code as you describe it came with...

Hi Deirdre,

I checked the latest download package and the .htaccess code I'm using is exactly the same as the one in the package.

So, I also think that the link posted above by Rod is outdated and should be ignored. If someone could confirm...

Regards.

rod barbee · 2016-11-22 23:00:13

That is a pretty old post, well before changes were made to the .htaccess file for subsequent updates. I'll let Matt decide if the post needs to stay there though.

dlangan · 2016-11-22 23:18:39

O dear,

For some strange reason it looked like that worked but now it isn't working!

Can someone help me please?

This link for example will no longer work: http://www.deirdrelangan.com/ClientArea … /2016/0722

and this is my .htaccess file located in :www.deirdrelangan.com/
Options -Indexes
AddHandler fcgid-script .php
FCGIWrapper "/dh/cgi-system/php56.cgi" .php
# ------------------------------------------------------------------------------
# | Web fonts access |
# ------------------------------------------------------------------------------
# Allow access from all domains for web fonts
<IfModule mod_headers.c>
<FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
############################################################################
# Edit this section for servers using FastCGI
# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line
RewriteBase /
RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$
# For FastCGI (or seeing the error message 'No input file specified.':
# add # to the start of the next line and remove # from the line after)
RewriteRule ^.*$ - [E=BASE:%2]
#RewriteRule ^(.*)$ - [E=BASE:]
############################################################################

RewriteRule ^(.*)$ - [E=QS:mod_rewrite=on]
RewriteRule ^([^\/.]*)-single.php$ %{ENV:BASE}single.php?%{ENV:QS}&id=$1 [QSA,L]
RewriteRule ^([^\/.]*).css$ %{ENV:BASE}index.php?%{ENV:QS}&extension=css&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).js$ %{ENV:BASE}index.php?%{ENV:QS}&extension=js&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).gif$ %{ENV:BASE}index.php?%{ENV:QS}&extension=gif&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).png$ %{ENV:BASE}index.php?%{ENV:QS}&extension=png&name=$1 [QSA,L]
RewriteRule ^([^\/.]*).jpg$ %{ENV:BASE}index.php?%{ENV:QS}&extension=jpg&name=$1 [QSA,L]
#RewriteCond %{QUERY_STRING} !mod_rewrite=on
#RewriteRule ^index.php$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]
RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^mobile.php$ %{ENV:BASE}mobile.php?%{ENV:QS} [QSA,L]
RewriteCond %{QUERY_STRING} !mod_rewrite=on
RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]

RewriteRule ^$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ %{ENV:BASE}index.php?%{ENV:QS}&page=$1 [QSA,L]
</IfModule>

Many thanks,
Deirdre

dlangan · 2016-11-22 23:20:11

btw - the error given is 'Paradox 404! Page does not exist!

rod barbee · 2016-11-22 23:27:04

might be something to do with clean urls. Do you know if your host is using Fast CGI?
(You should be able to find out by logging into your host's C-Panel and looking at the php config section)

Anyway, take a look here and then see if editing the section of the .htaccess file concering Fast CGI does anything for you.
http://backlight.theturninggate.net/doc … cess_files

otherwise, you might consider sending an email to Ben with your Backlight login credentials.

dlangan · 2016-11-22 23:56:48

Hi Rod,

Many thanks. From googling the issue it looks like it could be a problem with the rewrite rules not being compatible with my (broken) weblinks which exist in a subdir.

For example my website is www.deirdrelangan.com & BL files/dirs reside there but my client (broken) weblink files are in :
www.deirdrelangan.com/ClientArea/Weddings/2016

Unfortunately I don't know anything about rewrite rules or the syntax required to add code to .htaccess to tell it about my subdirs .....

Last edited by dlangan (2016-11-22 23:57:34)

rod barbee · 2016-11-22 23:58:47

Is ClientArea/ a top-level galleries folder in Backlight?

dlangan · 2016-11-23 00:02:38

Hi Rod,

No, ClientArea is nothing to do with Backlight. This is an old (top level) gallery that preceded BL but I still need my clients to be able to access the links that I emailed to them say 6 months ago.

Any ideas? Emails of broken links are trickling in ....

Thanks,
Deirdre

rod barbee · 2016-11-23 00:25:57

Sorry, I'm no expert on this stuff. Hopefully Ben or Matt will see this soon and be able to help you out with the .htaccess code.

From Googling around, it looks like there are ways to exempt folders from the rewrite rules. Here's one I found:

What you could also do is put a .htaccess file containing
RewriteEngine Off
In the folders you want to exclude from being rewritten (by the rules in a .htaccess file that's higher up in the tree). Simple but effective.

found here: http://stackoverflow.com/questions/1848 … write-rule

dlangan · 2016-11-23 00:39:08

Hi Rod,

Thanks for that. Added a new .htaccess file to my ClientArea & thought that would suffice but it didn't work so just realised I'd have to create a .htaccess in every sub dir. Not feasible. Nor is reissuing URL's to all clients.

Thanks though!

Deirdre

rod barbee · 2016-11-23 01:12:50

Just found this: http://stackoverflow.com/questions/1633 … od-rewrite
It appears to tell any URL that begins with certain characters to ignore rewrite rules.

so you might be able to do this:

RewriteRule ^ClientArea - [L,NC]

But as I said, I'm far from an expert on this (but pretty good a Googling )

Hopefully Ben will have a definitive solution.

dlangan · 2016-11-23 01:40:58

Thanks Rod but no luck!

rod barbee · 2016-11-23 01:44:14

Ah well. Wait for Ben to wake up on the other side of the world.

dlangan · 2016-11-23 01:46:07

Thanks Rod!

dlangan · 2016-11-23 02:22:44

I don't know why I didn't think of it earlier rather than troubleshooting for the entire day when I was really meant to be cleaning my office :-)

As a work around, I deleted my .htaccess file (so that client dirs are working) & then in backlight I modified the menu to fix all broken pages with, for example:
Name=About
Link to=URL
old desc=/about
& workaround desc = http://www.deirdrelangan.com/?page=about

Community @ The Turning Gate

#1 2016-11-16 02:56:45

Backlight 1.1 issue with arrows displaying now as boxes

#2 2016-11-16 03:25:30

Re: Backlight 1.1 issue with arrows displaying now as boxes

#3 2016-11-16 20:04:50

Re: Backlight 1.1 issue with arrows displaying now as boxes

#4 2016-11-16 21:49:39

Re: Backlight 1.1 issue with arrows displaying now as boxes

#5 2016-11-16 22:39:36

Re: Backlight 1.1 issue with arrows displaying now as boxes

#6 2016-11-16 23:10:08

Re: Backlight 1.1 issue with arrows displaying now as boxes

#7 2016-11-16 23:12:09

Re: Backlight 1.1 issue with arrows displaying now as boxes

#8 2016-11-20 22:23:35

Re: Backlight 1.1 issue with arrows displaying now as boxes

#9 2016-11-22 19:24:32

Re: Backlight 1.1 issue with arrows displaying now as boxes

#10 2016-11-22 19:40:08

Re: Backlight 1.1 issue with arrows displaying now as boxes

#11 2016-11-22 19:47:51

Re: Backlight 1.1 issue with arrows displaying now as boxes

#12 2016-11-22 23:00:13

Re: Backlight 1.1 issue with arrows displaying now as boxes

#13 2016-11-22 23:18:39

Re: Backlight 1.1 issue with arrows displaying now as boxes

#14 2016-11-22 23:20:11

Re: Backlight 1.1 issue with arrows displaying now as boxes

#15 2016-11-22 23:27:04

Re: Backlight 1.1 issue with arrows displaying now as boxes

#16 2016-11-22 23:56:48

Re: Backlight 1.1 issue with arrows displaying now as boxes

#17 2016-11-22 23:58:47

Re: Backlight 1.1 issue with arrows displaying now as boxes

#18 2016-11-23 00:02:38

Re: Backlight 1.1 issue with arrows displaying now as boxes

#19 2016-11-23 00:25:57

Re: Backlight 1.1 issue with arrows displaying now as boxes

#20 2016-11-23 00:39:08

Re: Backlight 1.1 issue with arrows displaying now as boxes

#21 2016-11-23 01:12:50

Re: Backlight 1.1 issue with arrows displaying now as boxes

#22 2016-11-23 01:40:58

Re: Backlight 1.1 issue with arrows displaying now as boxes

#23 2016-11-23 01:44:14

Re: Backlight 1.1 issue with arrows displaying now as boxes

#24 2016-11-23 01:46:07

Re: Backlight 1.1 issue with arrows displaying now as boxes

#25 2016-11-23 02:22:44

Re: Backlight 1.1 issue with arrows displaying now as boxes

Board footer