Title: Error &#8211; shortcode should be
Last modified: November 8, 2019

---

# Error – shortcode should be

 *  Resolved [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/)
 * (@stefanlochner)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/)
 * Glossary shows the following error:
    “The shortcode [lwpglsTermsArchive] should
   be added to the glossary archive page”
 * The shortcode is already inserted and working. But it is inserted via pagebuilder.
   
   Plugin is working, but the error message is disturbing.
    -  This topic was modified 6 years, 7 months ago by [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/).

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [LuckyWP](https://wordpress.org/support/users/theluckywp/)
 * (@theluckywp)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12113843)
 * Hello! Which page builder do you use?
 *  Thread Starter [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/)
 * (@stefanlochner)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12113866)
 * Live Composer
 *  Plugin Author [LuckyWP](https://wordpress.org/support/users/theluckywp/)
 * (@theluckywp)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12113999)
 * We studied this problem. In the next version option “Don’t check shortcode [lwpglsTermsArchive]
   on glossary archive page” will be added.
 *  Thread Starter [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/)
 * (@stefanlochner)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12114004)
 * Thanks! Looking forward to test it.
    -  This reply was modified 6 years, 7 months ago by [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/).
 *  Plugin Author [LuckyWP](https://wordpress.org/support/users/theluckywp/)
 * (@theluckywp)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12114224)
 * We make this. Try new version 1.0.7.
 *  Thread Starter [Stefan Lochner](https://wordpress.org/support/users/stefanlochner/)
 * (@stefanlochner)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12114299)
 * It works! Thanks for the quick solution!
 *  Plugin Author [LuckyWP](https://wordpress.org/support/users/theluckywp/)
 * (@theluckywp)
 * [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12114307)
 * Fine 🙂

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Error – shortcode should be’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/luckywp-glossary_373e47.svg)
 * [LuckyWP Glossary](https://wordpress.org/plugins/luckywp-glossary/)
 * [Support Threads](https://wordpress.org/support/plugin/luckywp-glossary/)
 * [Active Topics](https://wordpress.org/support/plugin/luckywp-glossary/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/luckywp-glossary/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/luckywp-glossary/reviews/)

 * 7 replies
 * 2 participants
 * Last reply from: [LuckyWP](https://wordpress.org/support/users/theluckywp/)
 * Last activity: [6 years, 7 months ago](https://wordpress.org/support/topic/error-shortcode-should-be/#post-12114307)
 * Status: resolved