You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some conditions for some page optional properties include looking at the value of properties at project level.
For example, in basicPages.xwd the disableGlossary option uses the condition "parent.glossary!=undefined" to check whether a glossary has been added at project level.
This condition will not work when the page is in a chapter as the parent is now the chapter and not the project.
@torinfo - I have had a look at the code in toolbox.js that deals with conditions but am struggling to work out how it works. It would be good to be able to use something like project.glossary which would always look at the project level data. Any ideas?
The text was updated successfully, but these errors were encountered:
Some conditions for some page optional properties include looking at the value of properties at project level.
For example, in basicPages.xwd the disableGlossary option uses the condition "parent.glossary!=undefined" to check whether a glossary has been added at project level.
This condition will not work when the page is in a chapter as the parent is now the chapter and not the project.
@torinfo - I have had a look at the code in toolbox.js that deals with conditions but am struggling to work out how it works. It would be good to be able to use something like project.glossary which would always look at the project level data. Any ideas?
The text was updated successfully, but these errors were encountered: