After a new Domino Designer Installation (newest Trail) I created a simple, simple Xpage and try to open it in a Browser (FF). The Xpage was loaded but has not HTML code. In other words its a blank page.
What did I do wrong ?
Update :
This is the XPage source code , very simple
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core" rendered="true">
Hello World
<xp:br></xp:br>
<xp:comboBox id="comboBox1" style="width:82.0px">
<xp:selectItem itemLabel="Eis"></xp:selectItem>
</xp:comboBox>
</xp:view>
UPDATE :
The solution to my question was answered by stwissel givving a hint to the viewport. Indeed the viewport 80 was blocked by another program. Can' remember which one. Then I changed the viewport under preferences->Domino Designer -> Web View Port to 8080 and it works. But I doubt that this is a permanent solution.
Check if "Build automatically" is turned off. If so (recommended setting btw) just build the project manually after every change you made.
Also check if the page has the "rendered" property set to "false". This will result in an empty response though you won't get an error message.
I answer my question myself, because there are different behaviours with FireFox and Edge Browser. In another try with Edge the browser shows a 404 Eror, while FireFox did not do that. So the question finally has to be why is there a 404 Error coming up
Have you tried cleaning the project? Project >>> Clean (from the top toolbar in designer)
Related
I am using a navigator control from the extension library. I want to use the default styling where only the selected item is highlighted and all the others are not highlighted and show the pointer cursor. For some reason it is applying the class "lotusSelected" to all the navigator nodes which are rendered as list items <li>.
I know that the "selected" property of tree nodes controls this. It does the same whether the property is set to true, false, or nothing. I am not trying to do anything fancy here, just use the default behavior. There is nothing in the custom css or theme to override this.
This happens on all browsers. Using Chrome tools I can see that removing the class causes the behavior I want. The navigation opens an XPage and changes a dynamic content control, this all works. This is used inside of the application layout control.
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core"
xmlns:xe="http://www.ibm.com/xsp/coreex">
<xe:navigator id="navigator1" expandable="false">
<xe:this.treeNodes>
<xe:pageTreeNode label="Add New ATM"
page="/xpSupervisor.xsp" queryString="content=newATM">
</xe:pageTreeNode>
<xe:pageTreeNode label="Update ATM Information"
page="/xpSupervisor.xsp" queryString="content=updateATM"
selected="false">
</xe:pageTreeNode>
<xe:pageTreeNode label="One Time Settlement Amount Change"
page="/xpSupervisor.xsp" queryString="content=changeSettlementAmt"
selected="false">
</xe:pageTreeNode>
</xe:this.treeNodes>
</xe:navigator></xp:view>
UPDATE: It seems to be some conflict between the pageTreeNode and the way I created the dynamic content control. It only messes up when on that one Xpage. Here is the code for that:
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core"
xmlns:xe="http://www.ibm.com/xsp/coreex"
xmlns:xc="http://www.ibm.com/xsp/custom">
<xe:dynamicContent id="dynamicContent1" useHash="true"
defaultFacet="default">
<xp:this.facets>
<xc:ccSupervisorHelp xp:key="default"></xc:ccSupervisorHelp>
<xc:ccNewATM xp:key="newATM"></xc:ccNewATM>
<xc:ccUpdateATM xp:key="updateATM"></xc:ccUpdateATM>
<xc:ccChangeSettlementAmt xp:key="changeSettlementAmt"></xc:ccChangeSettlementAmt>
</xp:this.facets>
</xe:dynamicContent>
</xp:view>
If I'am right, all nodes are selected because all nodes has the same page page="/xpSupervisor.xsp" as aim.
So if the page xpSupervisor.xsp is open, the navigator renders the nodes as select.
The property selected is only a boolean value, indicating whether the pageTreeNode is selected or not.
You should take a look at the property selection. This property is used in conjunction with navigationPath in the applicationLayout control. The property selection can take regular expressions to determine the selection state.
Despite two good answers which go me closer, I could not get the menu to work using the pageTreeNode. The fix was to switch to using a basicLeafNode and use a submittedValue and open the correct page in the onItemClick event of the navigator. I also added code in the 'selected' property to calculate which menu item was selected.
I could not get the context.getSubmittedValue() method to work in the selected property. I overcame this by setting it to a sessionScope var in the event. (viewScope didn't work for some reason)
<xe:basicLeafNode label="Update ATM Information" submitValue="updateATM">
<xe:this.selected><![CDATA[#{javascript:if(sessionScope.menuValue == "updateATM"){
return true;
} else {
return false;
}}]]></xe:this.selected></xe:basicLeafNode>
This is the code in the onItemClick that opens the correct link:
sessionScope.menuValue = context.getSubmittedValue();
if (sessionScope.menuValue == "newATM") {
context.redirectToPage("xpSupervisor.xsp?content=newATM");
} else...
The bottom of page 244 of the Extension Library book confirms this problem without offering a fix. Even though I have the book, hopefully this searchable answer will help others avoid the hassle I went through.
may be someone helps :)
I don't know much about Apache-Reverse-Server
I have a simple X-Page, see the code bellow.
If I open the xpage via
http: //domain1.de/e.nsf/test.xsp
and press the button, in log.nsf i see my print-out "Button is clicked"
If I open the xpage via
https: //example1.someproxy/rp/sproxy/http$domain1.de$80$/e.nsf/test.xsp
and press the button, in log.nsf i DON'T see my print-out "Button is clicked"
The Proxy-Server is installed and configured not by me.
<?xml version="1.0" encoding="UTF-8"?><xp:view xmlns:xp="http://www.ibm.com/xsp/core">
<xp:link escape="true" id="link1" disableTheme="true">
<xp:image id="image1" url="/btn.jpg"></xp:image>
<xp:eventHandler event="onclick" submit="true" refreshMode="complete" >
<xp:this.action><![CDATA[#{javascript:print("Button is clicked");}]]></xp:this.action>
</xp:eventHandler>
</xp:link>
What could be the problem, that the SSJS-code is not started via Reverse-Proxy at all?
Is reverse proxy the problem? Or is the problem that your code is not triggering?
I can't tell from your user id how experienced with XPages you are, but bear in mind a number of steps are performed on the server before it gets to your print statement. One of the key ones is conversion and validation. So if anything on your XPage throws a validation error, it won't run SSJS code.
Do you have a Display Errors control on the XPage and, more importantly, inside the refresh area? If not, add one. We've all spent hours in our early XPages life because validation or data conversion has failed and we didn't add anything to let us know. Once you get more confident, a PhaseListener is another useful tool for checking any or all lifecycle phases are running.
I have to create a simple XPages application for iOS devices so want to use the XPages Mobile Controls which come with the Extension Library in 8.5.3 UP1.
On one of the pages, I need the users to be able to open links in new tabs, but I've found that even with the link target set to _blank, the links are opening in the same tab when opened on the iPad. It works fine using Chrome on my laptop - opening in a new tab. If I just create a simple XPage (not using the Single Page App control) with the same link control on it, the link opens ok in a separate tab on the iPad.
Is there any way to try and force the link into a new tab if I use the Mobile controls?
This is code from a simple test xpage - which results in the link opening in the same tab when I test it on an iPad:
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core"
xmlns:xe="http://www.ibm.com/xsp/coreex" defaultLinkTarget="_blank">
<xe:singlePageApp id="singlePageApp1" selectedPageName="homePage">
<xe:appPage id="appPage1" pageName="homePage">
<xe:djxmRoundRectList id="djxmRoundRectList1">
<xp:label value="File Link:" id="FileLinkLabel"></xp:label>
<xp:br></xp:br>
<xp:link escape="true" text="Link" id="link1"
value="http://www.stackoverflow.com/" target="_blank">
</xp:link>
</xe:djxmRoundRectList>
<xe:djxmHeading id="djxmHeading1" label="Home">
</xe:djxmHeading>
</xe:appPage>
</xe:singlePageApp>
</xp:view>
I tried this out on an iPad with Domino v9.0.1 and on v8.5.3 (with ExtLib v853.20130315-0724 installed). In both cases the link opened in a new tab as expectedusing the code you posted.
Would you be able to upgrade to a newer version of the Extension Library, and try that?
http://extlib.openntf.org/?r=project/XPages%20Extension%20Library/releases/56832E9BD6A0615186257B4300349C59
The v853.20130315-0724 release was the final one released for 8.5.3, so I would try that.
Is there any issue with namepicker of Extension Library version 9.0.0.v00_01_20130415-0518?
It does not display popup window for address book, here is my code:
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core" xmlns:xe="http://www.ibm.com/xsp/coreex">
<xp:panel>
<xp:panel>
<xe:namePicker id="namePicker1" for="djName">
<xe:this.dataProvider>
<xe:dominoNABNamePicker addressBookDb="names.nsf" addressBookSel="all">
</xe:dominoNABNamePicker>
</xe:this.dataProvider>
</xe:namePicker>
<xp:br></xp:br>
<xp:br></xp:br>
<xe:djextNameTextBox id="djName" multipleSeparator="," multipleTrim="true">
</xe:djextNameTextBox>
</xp:panel>
</xp:panel>
</xp:view>
And also, I have manager's rights on names.nsf database.
Edit:
strange behavior! I change <xe:djextNameTextBox control to <xp:inputText and its works fine. How to debug xe:djextNameTextBox control to figure out the problem?
Edit 2:
Following error display when xsp page load:
Uncaught Error: Could not load 'dijit.form._FormValueWidget'; last tried '../dijit/form/_FormValueWidget.js' dojo.js:14
dojo._loadModule.dojo.require dojo.js:14
(anonymous function) #Fi&#Ez&#EOf&#Ek.js:107
Uncaught Error: Could not load class 'extlib.dijit.NameTextBox #Fi&#Ez&#EOf&#Ek.js:20
(anonymous function) #Fi&#Ez&#EOf&#Ek.js:20
$DBrH_ dojo.js:14
$DBpd_ #Fi&#Ez&#EOf&#Ek.js:20
$DBpe_ #Fi&#Ez&#EOf&#Ek.js:20
_4c #Fi&#Ez&#EOf&#Ek.js:20
dojo.loaded dojo.js:14
dojo._callLoaded dojo.js:14
dojo._modulesLoaded dojo.js:14
dojo._loadInit
After page load, when I click on name picker button another error display:
Uncaught TypeError: Object # has no method 'selectValue'
Your xe:djextNameTextBox control is not bound to a value. Try binding to e.g. a viewScope variable or a field on a document datasource:
<xe:djextNameTextBox id="djName" value="#{viewScope.nameField}" multipleSeparator="," multipleTrim="true">
</xe:djextNameTextBox>
Notes/Domino 9 now comes with Extension Library built in as standard. You do not need to install the extlib from OpenNTF.
I tested your source code in a default install of Notes 9. I get the following output:
Clicking the icon gets me this (I added the Admin + clicked OK).
The output of the page is now this:
My observation are below:
I uninstall Extension Library version 9.0.0.v00_01_20130415-0518 and upgrade to 900v00_02.20130515-2200, but the problem did not resolved. Then I install 8.5.3.20130315-0724 after uninstalling version 900v00_02.20130515-2200 and it works.
One more thing is that, at first after installing version 8.5.3.20130315-0724 it did not work in chrome browser (which was already opened on my laptop) then I open firefox and surprisingly it shows the address book, I mean that xe:djextNameTextBox control works with name picker control as expected. Then I switch to Chrome and clear all the history and reload the page .....!!! yes its work here too.
I repeat all the above stuff for Extension Library version 9.0.0.v00_01_20130415-0518 and Extension Library version 9.0.0.v00_01_20130415-2200 but xe:djextNameTextBox control not working with that versions.
-mak
Another hopefully simple issue from an xpages beginner.
I am trying to use the Navigator control from the Extension Library. No matter what I do with it, I cannot get it to render on any of the pages I try it on. Code is below. Thanks for any assistance.
<xp:view xmlns:xp="http://www.ibm.com/xsp/core"
xmlns:xe="http://www.ibm.com/xsp/coreex"
xmlns:xc="http://www.ibm.com/xsp/custom">
<xe:navigator id="outline" expandable="true">
<xe:this.treeNodes>
<xe:pageTreeNode page="/bcbsarequirements.xsp" selection="/bcbsarequirements" label="BCBSA Requirements" role="navigation"/>
<xe:pageTreeNode page="/compliance.xsp" selection="/compliance" role="navigation" label="Compliance"/>
<xe:pageTreeNode page="/finance.xsp" selection="/finance" label="Finance" role="navigation"/>
</xe:this.treeNodes>
</xe:navigator>
</xp:view>
This will happen at least if your view tag is missing the extension library attribute. Make sure the view tag looks like this: <xp:view xmlns:xp="http://www.ibm.com/xsp/core" xmlns:xe="http://www.ibm.com/xsp/coreex">. If the attribute is missing there is an error visible in the source.
Make sure there is no error in XPage source.
Make sure the application is built (sometimes project -> clean is needed).
Make sure extension library is checked in application properties (you should get errors if not).
Check for any error messages in the server console/log when loading the XPage on browser.
Do other extension library controls render for you? If not there is a problem in ExtLib installation.
Make sure your Designer and server have the same and preferably the latest (20121217) ExtLib version.
If you are using the Upgrade Pack then you can open an SPR with IBM.