# \[BUG-12388\] Custom library visibility

**URL:** <https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809>\
**Category:** Ignition Early Access\
**Tags:** scripting\
**Created:** [January 11, 2019, 9:13am UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809 "2019-01-11T09:13:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrea.morando](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.morando/32/8039_2.png) [@andrea.morando](https://forum.inductiveautomation.com/u/andrea.morando)\
**Post date:** [January 11, 2019, 9:13am UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809/1 "2019-01-11T09:13:11Z")

</div>

Hi,  
in the beta build b2019010702, I found an error in using the binding script of a component.  
As an example, in the binding of a label component I use the following script:

 ![11-01-2019%2009-57-16](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/59a05f8225937a39cfe60c9ef0b09f9097e68e63.png)  
I call the class “Label” written in the module “menu” (shared\>persp\>model\>system\>menu the complete path of the script) and I get the expected object: “\<menu.Label instance at 0xa\>”.  
Then, if I make a modification in the “Label” class, after the commit I get the following error:

“Traceback (most recent call last):  
File “”, line 4, in transform  
AttributeError: ‘com.inductiveautomation.ignition.common.script.Scr’ object has no attribute ‘persp’”

It seems like the custom package is no longer visible.  
In order to run again the script, I have to close and re-open the designer session.

In the earlier beta versions I tested, this error was not present.

---

<div class="post-metadata">

**Author:** ![andrea.morando](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.morando/32/8039_2.png) [@andrea.morando](https://forum.inductiveautomation.com/u/andrea.morando)\
**Post date:** [January 16, 2019, 12:21pm UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809/2 "2019-01-16T12:21:52Z")

</div>

The problem still remains for build **b2019011502**.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [January 22, 2019, 10:35pm UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809/3 "2019-01-22T22:35:22Z")

</div>

This does indeed seem to be happening and can be replicated on our end rather easily. Right now it looks like open Sessions are failing to utilize the newest commits/saves of any global resources.

The quick workaround is to open a new Session anytime you modify those global resources, but this is something we’ll obviously work to get fixed before 8.0.

---

<div class="post-metadata">

**Author:** ![andrea.morando](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrea.morando/32/8039_2.png) [@andrea.morando](https://forum.inductiveautomation.com/u/andrea.morando)\
**Post date:** [January 24, 2019, 2:41pm UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809/4 "2019-01-24T14:41:07Z")

</div>

Thank you so much for your reply.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [March 27, 2019, 11:09pm UTC](https://forum.inductiveautomation.com/t/bug-12388-custom-library-visibility/21809/5 "2019-03-27T23:09:05Z")

</div>

This issue should be fixed in the newest build. Let us know if you continue to see this behavior after upgrading.