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.
Pages: 1
I updated to the new version 1.03 today, or so I tought. After following the instructions to the teeth several times over my Backlight design version still reads 1.02. Anyone else seeing this or am I the only one? Any suggestions??
Offline
Good evening,
For me it's the same thing!
Philippe
Offline
I come again to reinstall, and then everything was wonderfully run.
I am version 1.0.3
Great !
Philippe
Offline
Still version 102 for me......
Have gone trough the whole process again, downloaded the update and put everything where it should go according to the instructions, but to no avail.
Offline
Hi Roger, can you please provide me with a Backlight admin login and FTP access via the email link under my picture? I'll try to work out what's gone wrong.
Offline
Maybe there's a misundertanding about the update instructions... They read as follows:
Replace the following files and directories:
backlight/admin/
backlight/designer/
backlight/framework/
backlight/publisher/
backlight/modules/module-pages/
backlight/modules/okapi-core/
backlight/modules/standard-album/
backlight/modules/standard-album-set/
backlight/modules/standard-page/
When I compare the corresponding 1.02 and 1.03 folders, I see that files that were present in my 1.02 installation are no longer there in version 1.03.
Does replace mean that all existing files in the above listed folders should be deleted before copying the new files in these folder?
Last edited by Samoreen (2016-07-13 18:17:19)
Patrick
Offline
Hi Patrick, replace means what it says. Technically deleting the old directory and re-uploading the new directory.
However, copying the new directory over the old one should work just as well. The only files removed from 1.0.2 were redundant files that have never been needed. It doesn't matter if they are still there.
Where exactly are you seeing 1.0.2?
Offline
Maybe there's a misundertanding about the update instructions...
Does replace mean that all existing files in the above listed folders should be deleted before copying the new files in these folder?
Yes. That's it. The files present in version 1.02 and not present in version 1.03 are causing this issue.
So the update instructions should mention that the whole contents of the target folders should be deleted before copying the new files. The term "replace" is misleading.
Patrick
Offline
However, copying the new directory over the old one should work just as well. The only files removed from 1.0.2 were redundant files that have never been needed. It doesn't matter if they are still there.
Ben,
Apparently, this is not the case. When I first installed the update, I did as you say: I copied the files from the new version folders to the old one. 1.02 was still appearing everywhere the product version is displayed. In the Dashboard in the first place.
Then, I used a comparison tool (Beyond Compare - a very useful product) and I mirrored the new folders to the old ones (which means that these "old and unnecessary files" were deleted). And bingo, when I relaunched Backlight, I had again the notification message about the database update but this time, the correct version number was displayed.
Last edited by Samoreen (2016-07-13 18:44:59)
Patrick
Offline
Hi Patrick,
With all due respect, 'replace' is not misleading. You had an old directory. You're replacing it with a new one. Whether your FTP client does as much when dragging over a directory, or whether you need to manually delete the directory doesn't change the meaning of 'replace'.
I am very curious about what may be going on here. None of the files in 1.0.2 that were removed should have any affect on versioning or (skipping) the database upgrade process.
I use FileMerge extensively to review every changed file for every release. This should be functionally equivalent to FileMerge.
I have just tested the upgrade process in two ways:
1. Starting with a 1.0.2 installation
2. Deleting admin, designer, framework and publisher
3. Copying admin, designer, framework and publisher from 1.0.3 to backlight/
1. Starting with a 1.0.2 installation
2. Copying admin, designer, framework and publisher over the directories already in backlight/
The second method left the 'removed' files on the server.
Both upgrades behaved exactly the same, with database upgrades automatically happening upon logging in.
Now, none of this is very helpful in working out why your site (and it appears, others' sites as well) didn't upgrade the database. Can you help with the following:
* Did you upgrade from the Backlight zip file or from the Backlight+Pages zip file?
* What FTP software did you use?
Offline
Now, none of this is very helpful in working out why your site (and it appears, others' sites as well) didn't upgrade the database. Can you help with the following:
* Did you upgrade from the Backlight zip file or from the Backlight+Pages zip file?
* What FTP software did you use?
1. During the first update attempt, the database has been updated. I got the notification message when going to the Backlight Dashboard. But the Dashboard still indicated 1.02. After removing the old files, the database was updated again but this time I got the correct version number.
2. I used the Backlight + Pages zip file.
3. Since I'm using a NAS as a test server, I have access to the Backlight folders directly. I'm not using any FTP client.
Patrick
Offline
Hi Roger, can you please do me a favour and provide me with FTP access via the Email link under my picture? I would love to be able to work out just what's going wrong with this 1.0.2 issue.
Offline
Hello everyone,
If I may, I'll explain how I updated.
First I updated from Backlight + page with Transmit as ftp software.
The first time I wanted to update, I drag and drop to replace the existing files, and I'm still left with the old version 1.0.2
I redo exactly the same operation later without first deleting files just by replacing them, and it worked flawlessly!
Philippe
Offline
May I humbly suggest what I do. I ALWAYS delete the file on the server side - then I FTP the new updated file. I use FileZilla and both the source side (my computer) and the server side are available to see.
As such, the carryover of versions numbers etc. never is a problem.
Just a suggestion.
Last edited by gwlco (2016-07-13 21:59:39)
Offline
Yes, I also use FileZilla and was having problems updating from 1.0.2 to 1.0.3. In FileZilla I'd been using 'Overwite' method of replacing the files. Did the whole job twice and still didn't work. Then I thought lets delete the 'Corrrect' files in FileZilla and replace each one individually. Well it worked immediately when I logged back into Backlight. Then it was a simple matter of 'clearing cache' and loading the new TTG Publisher plug-in Lightroom. But I learnt one thing in FileZilla. Overwrite does not mean Replace. I reckon it should... but it doesn't and suspect the same thing is happening with other FTP apps and hence causing all these update problems. Any everything is now working beautifully. Thank you TTG team:-)
Rgds Cliff
Offline
Overwrite does not mean Replace. I reckon it should... but it doesn't and suspect the same thing is happening with other FTP apps and hence causing all these update problems.
I doubt it is an FTP issue. I had the problem although I didn't use a FTP client : I'm testing my site on a NAS and I have direct access to folders. So I'm merely using a file synchronizer to update (Beyond Compare). And I'm pretty sure that the files were replaced (overwritten) during the first attempts. The problem was fixed only after deleting the files from 1.02 not present in 1.03.
Patrick
Offline
I would love to figure this out, but as is often the case, replication is the most difficult step. I haven't been able to see this problem on my side.
Offline
Pages: 1