This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.
Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.
Before posting questions here you might want to review the developer documentation.
Hi all,
I have inherited a site which has a graphic across the top of each and every page. It's not located on the master page or in the skin. It shows on the page as if it it was an added feature instance in the top pane of the page.
The kicker is that it shows across every page of the website (and is editable), yet when I choose "Edit This Page" it doesn't show as a component. (In other words, it wasn't added manually to each page. ). I have also looked in the Content Manager at this particular feature and it doesn't show as being published on ANY page.
Where is the page content coming from?
Thanks!
Look in the skin's layout.master for a ModuleWrapper control.
HTH, Joe D.
Hi Joe,
The layout.master files are identical as I just copied over the skin and master files from the existing site to the new one. The only thing that we didn't copy was the database files, so I'm led to believe that it's a feature instance within the site but I'm not seeing anywhere in the app where it says that it's actually posted.
You need to look carefully in your layout.master file for <portal:ModuleWrapper ,if the content is editable but does not show up under edit this page and it appears on every page then it is most likely using this ModuleWrapper control to embed some existing content instance or else a custom feature. See the documentation on ModuleWrapper to understand better.
Hope that helps,
Joe