This article defines the different methods to identify the master module of a shared module. This is essential as any edits must be performed on the master module.
- Access to an Administrator or SuperUser account.
To identify a master module is quite simple. If you are editing any page currently on the shared module, you will receive this message above the shared module:
"This module does not belong to the page. Please, move to its master page to change the module".
If you click the master page hyperlink, you should be able to be routed directly to the page of your master module.
But there are times where the message will not appear, and you need to find which page is the master page for the shared module through the backend.
You will need to access the SQL console via Settings > SQL Console and run the following queries:
- Find the specific module ID from the shared module on the page. You can go into edit mode and hover over the module settings.
The URL displayed at the bottom of the screen will contain the module ID.
- You can see the module ID in the above example image is 363. Using this ID, run the following query:
SELECT * FROM ContentItems WHERE ModuleID = 363
- Using the output from the above query, you can find the
TabID. With the
TabID, you can then run:
SELECT * FROM Tabs WHERE TabID = #
This query will provide the name of the page where the master module is currently located.
To test that you have identified the master module:
- Access the page the master module is.
- Make a content change on the master module.
- Browse to another page where the module is deployed and see if the change has persisted.