# Ignition 8.0 Upgrade - Inaccessible Shared Project Scripts

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-0-upgrade-inaccessible-shared-project-scripts/24305>\
**Category:** Ignition\
**Tags:** scripting, ignition80\
**Created:** [April 22, 2019, 10:33pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-upgrade-inaccessible-shared-project-scripts/24305 "2019-04-22T22:33:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [April 22, 2019, 10:33pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-upgrade-inaccessible-shared-project-scripts/24305/1 "2019-04-22T22:33:30Z")

</div>

I had a client recently upgrade their Gateway from Ignition 7.9.10 to 8.0

Before the upgrade, there existed several shared project scripts for handling critical functionality for both the server and the clients. Since upgrading, the scripts have become grayed out in the project browser and are inaccessible.

Other than that, they seem to still be functioning fine.  
What’s going on here?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/ca22a3bd4c739cd57db0e5f9dfa0ba3af216f047.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 22, 2019, 10:35pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-upgrade-inaccessible-shared-project-scripts/24305/2 "2019-04-22T22:35:48Z")

</div>

Those projects are defined in a parent project. To edit them, open the parent project (probably called `global`). In 8.0.1 you’ll be able to open them in a read-only view.

In either case, you can also make local changes by right clicking them to ‘override’ - however, this is strictly a local-to-the-current-project override - you’re not editing the actual resource definition on the parent.

Some more context on how this all works: [Version 8 Shared Vision Templates](http://forum.inductiveautomation.com/t/version-8-shared-vision-templates/24239/11?u=pgriffith)

---

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [April 22, 2019, 10:41pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-upgrade-inaccessible-shared-project-scripts/24305/3 "2019-04-22T22:41:41Z")

</div>

Makes perfect sense, I should have RTFM [https://docs.inductiveautomation.com/display/DOC80/Ignition+8+Upgrade+Guide#Ignition8UpgradeGuide-ProjectInheritance&“global”upgradelogic](https://docs.inductiveautomation.com/display/DOC80/Ignition+8+Upgrade+Guide#Ignition8UpgradeGuide-ProjectInheritance&%E2%80%9Cglobal%E2%80%9Dupgradelogic)

Thanks!