Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Many thanks Matt,
I have now removed the sitemap and will explore the creation of a new one more carefully.
Thanks Matt,
Ben had done a shed load of stuff associated with my transfer from dev(test) to live and everything was working fine. With me creating the sitemap.xml file this morning, funny things happened to an otherwise well behaved site so I assumed that the last thing to change caused the problem.
I have edited out most of the sitemap.xml file down to 15 pages. I still get the BL error -something went wrong - on the Exhibitions page from the Google assigned index as per the screen shot.
As Ben had already run the fix outlined in the blog, I did not connect that with the issue.
Hi Matt,
Before I uploaded a sitemap the menu was behaving OK. Since then after clicking the Edgelands link as in the screenshot I see the little rectangles instead of chevrons.
If I click Exhibitions I get the BL something went wrong but if I click on the blue More results, the Exhibitions page opens OK.
Please excuse my ignorance as I have not (consciously) bothered with sitemaps before.
Hi chaps,
I've been quiet for a week whilst my new BL live site has settled in and I've made minor edits to it. This morning after prompting by Google Search Console, I created a sitemap.xml file (via xml-sitemaps.com - it got guillotined at 500 pages) and uploaded it to the root of my live site. More or less immediately I got a better listing but when I clicked on one of the indexed pages - Edgelands, I noticed a font issue in the menu on the galleries page. Navigating the menu from there was OK.
When I clicked on the Exhibitions page I get a BL error - Something went wrong - unable to find info.php.
When I click on the More results from openpoint.co.uk, the page is listed and navigation to the Exhibition page works OK.
I suspect that I need to ensure that the url for info.php needs to be near the top of the sitemap.xml file.
What might cause the font issue in the menu for the Edgelands page that does not appear when navigating the site normally?
By the way the search criteria I entered in Google was Tom Owens Photographer
Hi Ben,
They have gone away with me replacing the .htaccess file. I added the php_flag register_globals off to the bottom of the BL .htaccess file but I don't know what the original file was doing previously especially with the /blog/ entry. Everything seemed to work in CEn so I don't know when it was created or what it actually did. Presumably something important.
Another thing that Rod pointed out that I had to do was re-upload the uploaded images used in pages. I've also reset the menus to URLs apart from the Privacy Policy that I had to leave as a Page link.
The Google Analytics ID is working but not apparently for the Blog. Presumably that is something that will get sorted when the WP plugin arrives?
If you want me to recreate the 404s then I would have to put the original .htaccess file back in place of the BL one.
Let me know.
I'm off to London shortly so will drop off the radar.
404 errors seem to be resolved now. If you spot any stupid stuff please let me know.
Thanks
Hi Daniel,
Do you mean rename the top level .htaccess as .htaccess_root and have both a copy of .htaccess from the test area sitting together with .htaccess_root under http://tomowens.openpoint.co.uk?
This is thin ice for me.
UPDATE
Ive replace the .htaccess with the one from /test and added the switch to gain access to the SQLite module. I have tested a blog entry and also tested navigation back and forth from the galleries pages to other pages without a 404. I'll now test setting the pages back to URLs
Still suffering from 404 errors. Any suggestions as to the .htaccess versions at #24 above? I have noticed that if I try and navigate to the Home, About, Exhibitions, Contact pages having been on a gallery page I always get an error 404.
Hi Rod,
I have finally got this to work. What I had done first time around was strip the code in GA and paste it into the field in BL.
I deleted the entry in BL and saved the change.
I then typed in the code and saved it then cleared the cache and hey presto the script appeared.
The moral of the story appears to be type in the code.
Yes Rod,
Yes Rod, just that field as I don't use Webmaster Tools. copied from the GA site and pasted it in.
Hi Rod
I don't see that here.
<!doctype html>
<html dir="ltr" lang="en">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="HandheldFriendly" content="True" />
<meta name="MobileOptimized" content="320" />
<meta name="viewport" content="width=device-width, maximum-scale=1.0, minimum-scale=1.0, initial-scale=1.0, user-scalable=no" />
<meta name="template-version" content="50" />
<title>photography by tom owens</title>
<!-- Open Graph Protocol **************************** -->
<!-- http://developers.facebook.com/tools/debug -->
<link rel="image_src" href="" />
<meta property="og:description" content="" />
<meta property="og:image" content="" />
<meta property="og:image:width" content="" />
<meta property="og:image:height" content="" />
<meta property="og:site_name" content="photography by tom owens" />
<meta property="og:type" content="website" />
<meta property="og:title" content="Home" />
<meta property="og:url" content="http://tomowens.openpoint.co.uk/" />
<!-- https://dev.twitter.com/docs/cards/preview -->
<meta name="twitter:card" value="summary" />
<meta name="twitter:creator" value="@tomowensphoto" />
<meta name="twitter:description" value="" />
<meta name="twitter:image" value="" />
<meta name="twitter:image:src" value="" />
<meta name="twitter:site" value="@tomowensphoto" />
<meta name="twitter:title" value="Home" />
<meta name="twitter:url" value="http://tomowens.openpoint.co.uk/" />
<!-- /Open Graph Protocol **************************** -->
<link rel="canonical" href="http://tomowens.openpoint.co.uk/" />
<link rel="stylesheet" type="text/css" media="all" href="index.php?template=6&extension=css&name=style" />
<link rel="stylesheet" type="text/css" media="all" href="http://tomowens.openpoint.co.uk/backlight/modules/okapi-core/static/css/fonts.css" />
<link rel="stylesheet" type="text/css" media="all" href="http://tomowens.openpoint.co.uk/backlight/modules/okapi-core/static/css/font-awesome.min.css" />
<link rel="stylesheet" href="http://tomowens.openpoint.co.uk/backlight/custom/css/custom-copyright.css" />
</head>
Well ignore the ID as I saw where to post that but where does the code go?
Ignore that request. I've just cleaned my glasses!
In CE4 there was an option to paste in the tracking code when setting up a page. I have rooted around but possibly I'm looking in the wrong places for the same feature in pages for Backlight?
Any pointers as to where to paste the GA code snippet?
I took the leap of faith and with Ben's help this is working albeit not 100% as yet as there are a few irregular 404 errors but paging back and forth on the menu seems to clear them.
http://tomowens.openpoint.co.uk/?page=home
There is no going back now and I am so grateful for the relative ease with which Backlight allows me to create/update/review and rework than ever before in CEn.
There is nothing fancy in what I have done and I suppose that is a tad boring really but by recreating what I had before, it gave me a benchmark to test against. As more features get added I'll experiment but I do prefer simple and clean looking pages and Backlight delivers this easily and the speed with which I can experiment is light years ahead of clunking around in LR. LR is the workhorse of my processing so just having to use the Publisher has enabled me to think about being able to make hassle free changes going forward.
Thanks for all the extra support so far.
Regards,
TomO
Spoke too soon. Intermittent 404 errors now even with Page links.
Regards,
TomO
Now this shows my ignorance of these things.
One of my initial problems when BL first came out was accessing the SQLite from the link. I had to place a line in .htaccess to sort that out. There are many .htaccess files cascading down the tree so I made that edit in the root of tomowens.openpoint.co.uk and I was able to access the database to delete orphans in v101. I can see that the .htaccess sitting at the top level of my test directory structure is very much larger
This is what is in the .htaccess at the top level of tomwens.openpoint.co.uk
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
php_flag register_globals off
This is what is in the top level of /test
<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>
Which one should have the php_flag register_globals off line in it and what about the content in the small one anyway? This is a danger zone for me.
Regards,
TomO
Ben had to go in to the back end and copy stuff for me. I 'll check that out but in the meantime I have got the other pages to open by changing from URL to page in the menu set. Galleries, Search and Blog are all URL setting that I have left as such. The rest have been changed from URL to Page.
Does this suggest anything?
Regards,
TomO
I thought this was working on the iPhone and iPad but the cached pages were still pointing at the /test/ sub-domain
Error 404 in Firefox and Safari for every page listed above.
Regards,
TomO
That is good news Daniel. I'll keep at it here.
Regards,
TomO
Progress Ben.
Permissions/ownership changed by ISP. Galleries pages now working.
Having problems with Error 404 clicking on
Home
About/Privacy Policy
Exhibitions
Contact
Search and Blog menu items are OK. Have tried clearing cache.
Getting there. Any ideas for the 404's?
Regards,
TomO
Thanks Ben. Have replied and also written to ISP instructing them to add owner permissions. I really appreciate your help as always. I'll let you know when something happens. The ISP is not nearly so quick as you chaps.
Regards
TomO
Fine Ben, please proceed. I have to get on video confs for a while to sort out other work stuff so I will not be on the webserver.
Let me know via email what you had to do and if there is anything I ought to have done in my migration.
Many thanks,
TomO
Hi Ben,
I do not have SSH access.
I downloaded the test environment to my local machine via FTP and then uploaded the files and directories to tomowens.openpoint.co.uk via FTP. I'm hoping your Plan B will work.
Regards,
TomO