Skip to main content
Known Participant
January 13, 2021
Question

Fix a broken Rob Cole Plugin

  • January 13, 2021
  • 5 replies
  • 1049 views

Hi,

An update to LR finally broke Rob Cole's awesome Treesync Plugin. It looks for a folder called Filename Templates in the LR folder, doesn't find it and fails. It still works if you don't try file renaming though. I've stuck up a bounty on Bountify to fix it as I wouldn't know where to begin:  https://bountify.co/fix-an-adobe-lightroom-plugin, but if anyone here knows how to fix it or what broke it, pls share how and I'll post that too to speed up the process. Alternatively the bounty is there.

This topic has been closed for replies.

5 replies

sebmsgAuthor
Known Participant
August 2, 2023

Hi John - I'm back doing LR and realised I didn't reply again. Sorry 😞

2023-08-02 22:12:21 com.robcole.TreeSyncPublisher ERROR ****** ERROR #1: TreeSync Publisher export terminated prematurely due to an error - [string "Export.lua"]:1115: You must restart Lightroom in order to use selected filenaming preset

johnrellis
Legend
January 14, 2021

Is there an error message? What does it say exactly?

 

[Use the blue reply button under the first post to ensure replies sort properly.]

sebmsgAuthor
Known Participant
August 2, 2023

If it helps this is a chunk of code with the item. Replying to you as it's been a while... function Export:getDestBaseName( props, photo, cache )
if props == nil then
app:callingError( "need export params" )
end
local srcBase = LrPathUtils.removeExtension( LrPathUtils.leafName( lrMeta:getRaw( photo, 'path', cache ) ) )
local basename
if not props.LR_renamingTokensOn then -- universal:
basename = srcBase
else -- rename
self:_assurePresetCache( props, photo )
if not self.filenamePreset then
self.filenamePreset = self:_getVerifiedPreset( props.LR_tokens )
if not self.filenamePreset then
app:error( "You must restart Lightroom in order to use selected filenaming preset" )
end
else
--Debug.pause( self.filenamePreset.name )
end
if self.filenamePreset then
--Debug.lognpp( props )
--Debug.showLogFile()
local s
if self.seqNum == nil then
self.seqNum = props.LR_initialSequenceNumber or 1
else
self.seqNum = self.seqNum + 1
end
if not self.filenamePreset.id then
app:error( "how's there a preset with no ID? named '^1'", self.filenamePreset.name )
end
s, basename = LrTasks.pcall( photo.getNameViaPreset, photo, self.filenamePreset.id, props.LR_tokenCustomString or "", self.seqNum )
if s then
if basename then
if #basename > 0 then

 

johnrellis
Legend
August 2, 2023

I poked around a bit inside the plugin's source code. It has a fair bit of code for groveling around in Lightroom's presets. That code assumes the old locations of preset folders prior to the big change in presets in LR 7.2 (2018), which happened several years after Rob passed away.  It's more than a 10-minute change, I'm afraid, to bring it up-to-date.

DdeGannes
Community Expert
Community Expert
January 14, 2021

The author of the plugin passed away around 2015?? Do you think Adobe can resurrect him?

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.0.1, PS 27.0; ) Camera Oly OM-D E-M1.
sebmsgAuthor
Known Participant
January 14, 2021

No - but someone can update the code.

GoldingD
Legend
January 14, 2021

Some third party plugins started failing at v10.0, Check for an update.

 

johnrellis
Legend
January 13, 2021

I think LR still uses the "Filename Templates" folder for storing renaming templates, and its location hasn't changed.  It's in the "Lightroom" folder you get to when you do Preferences > Presets > Show All Other Lightroom Presetes. 

 

Are you getting an error message or something else referring to this folder? 

 

[Use the blue reply button under the first post to ensure replies sort properly.]

sebmsgAuthor
Known Participant
January 14, 2021

Hi John,


The plugin looks inside the Program Files Lightroom folder, but LR is saving inside appdata. Any ideas how to move the LR folder? Otherwise thanks for the tips - have updated the Bountify with that factor.