Additional Actions for importing verses into Microsoft Word

Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 2
Darrell Ferguson | Forum Activity | Posted: Wed, Aug 24 2016 7:00 PM

I upgraded to Logos 7 today, and now the feature that allowed me to import Bible passages from Microsoft Word no longer works. (It used to be called Smart Tags, but now Microsoft calls it Additional Actions). In Word, in the Autocorrect settings, you can check "Enable Additional Actions on Right Click Menu" and one of the options is "Logos Bible Software (Bible References)." I have that box checked so that in a Word document I can right click on a Bible reference, then select "Additional Actions," and one of the options was to replace the reference with the Bible passage. That worked until I did the Logos 7 upgrade, and now it no longer works. 

Is there any way to make this work with Logos 7? 

Posts 612
Bill Shewmaker | Forum Activity | Replied: Thu, Aug 25 2016 8:50 AM

Darrell Ferguson:

I upgraded to Logos 7 today, and now the feature that allowed me to import Bible passages from Microsoft Word no longer works. (It used to be called Smart Tags, but now Microsoft calls it Additional Actions). In Word, in the Autocorrect settings, you can check "Enable Additional Actions on Right Click Menu" and one of the options is "Logos Bible Software (Bible References)." I have that box checked so that in a Word document I can right click on a Bible reference, then select "Additional Actions," and one of the options was to replace the reference with the Bible passage. That worked until I did the Logos 7 upgrade, and now it no longer works. 

Is there any way to make this work with Logos 7? 

Hi Darrell, I just tried to do this with MS Word and had no problem. Quick question...do you have Logos 7 open when trying to import the Bible passage(s) into MS Word? I think that was, at one time, a prerequisite for the Smart Tags to work...I have always made sure that I have Logos running in the background.

Posts 2
Darrell Ferguson | Forum Activity | Replied: Thu, Aug 25 2016 10:55 AM

Yes, it's open. I have everything set the same as it was before I did the upgrade.


Posts 29128
Forum MVP
MJ. Smith | Forum Activity | Replied: Thu, Aug 25 2016 12:16 PM

See https://wiki.logos.com/Smart_Tags for instructions

Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."

Posts 3
Christopher R. Graber | Forum Activity | Replied: Thu, Aug 25 2016 6:49 PM

I am having the same issue.  Logos support was no help.  Please let me know if you get it figured out.  

Posts 3
Christopher R. Graber | Forum Activity | Replied: Thu, Aug 25 2016 6:50 PM

These instructions did not help me.  

Posts 3
Christopher R. Graber | Forum Activity | Replied: Thu, Aug 25 2016 9:47 PM

I had the same issue. Even the copy and paste option from Copy Bible Verses was not communicating with Word. I tried all sorts of stuff. Eventually I decided to just restart my computer.  When I did this, Logos did another update and then it was working fine. 

Posts 15805
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Thu, Aug 25 2016 11:08 PM

Darrell Ferguson:
I upgraded to Logos 7 today, and now the feature that allowed me to import Bible passages from Microsoft Word no longer works. (It used to be called Smart Tags, but now Microsoft calls it Additional Actions).

What version of Word ?

Apologies since can replace with passage in 64 bit Word 2010 from Logos 7.0.0.0074 on Windows 10, but did encounter a space being needed between book abbreviation and verse number for additional action to work in Word.

Keep Smiling Smile

Posts 6
Chad McFadden | Forum Activity | Replied: Fri, Jul 17 2020 11:15 AM

Using Powershell to fix Smart Tags

Logos 6 and higher are 64-bit programs so you will experience problems if you recently upgraded from 32-bit Logos 4 or Logos 5 on a 64-bit Windows system.
You may also experience problems after upgrading to a higher version e.g. from v7 to v8.

On most Windows versions, PowerShell comes with script execution disabled by default, so you should set the PowerShell execution policy to allow script execution:

  1. Run PowerShell as Administrator (Windows+S key, type PowerShell, right-click on Windows PowerShell in the list and choose Run as administrator.
  2. In the PowerShell window, type Set-ExecutionPolicy RemoteSigned <Enter>. Type Y <Enter> to make the change.

Run the Powershell script:

  1. Download the RegisterSmartTags.ps1 script from http://downloads.logoscdn.com/LBS6/Support/RegisterSmartTags.ps1.
  2. In Windows Explorer, find the script in your downloads folder (e.g. C:\Users\Dave\Downloads), right-click on the script and choose Run with PowerShell. Since the script is signed by Logos Bible Software, choose Open from the Open File – Security Warning dialog, if displayed.
  3. Note: if you do not see Run with PowerShell in the context menu, open a PowerShell window as described below under Verbum and Noet but run the script without any switches i.e. type .\RegisterSmartTags.ps1 <Enter>
  4. The script calls RegSvr32.exe to register the Logos Smart Tags dll, L4SmrtTg.dll, which should display a RegSvr32 dialog message similar to, “DllRegisterServer in C:\Users\Dave\AppData\Local\Logos\System\L4SmrtTg.dll succeeded.”, click OK.
  5. The PowerShell window should list details about registering, ending with the message “Finished successfully. Hit a key to exit...”.
    Logos Smart Tags for 32-bit Office should now be registered.
  6. If you see an error message, such as “Failed to...”, please create a bug thread in the appropriate forum e.g. Logos 8.
Page 1 of 1 (9 items) | RSS