I have been trying to get select2 to work on an existing xPages application with no luck. I keep getting errors saying select2() is not a function. I must have something messed up with my files/folders for the required code.
I am not sure what files I need to incorporate into the Web-Inf folder. I am using Domino 9.0.1 FP3
Does anyone have a sample db I could get to pick apart and see what I am missing?
I've updated the Select2 demo on Bootstrap4XPages.com. That site is powered using the Bootstrap version in the ExtLib and no longer relies on the Bootstrap4XPages plugin. Select2 was added to the demo database in the WebContent folder and is loaded through a theme.
I've created the following examples:
Enabling Select2 on a ComboBox control, including a handler for the 'onchange' event that refreshes another section of the page.
Enabling Select2 on a ListBox control with multi-select.
A Select2 field that is attached to a (hidden) input and uses Ajax to get JSON search results from a second XPage.
Good luck picking it apart :-) The source is on GitHub
Related
I am trying to figure out why my global object selection is no longer available when I am using server side javascript. Also my data sources are blank when looking at the side panel on right but the xpage does have a data source assigned. If I removed the data source from the panel and re-add the data source, then my data source shows correctly(with all the fields available).
This just started happening recently. I am running 9.0.1 FP10 SHF380.
Any help would be appreciated.
Kevin
I have one Notes Template ntf in which the Openntf Domino API plugins do not appear in 'Plug-in Dependencies' library, eg. org.openntf.domino.xsp etc. They are installed on both the server and the local machine, as we use XPiNC. They appear in any a new application created from the template and they appear in other templates and other nsfs. The plugin xml references them but they are still not in there.
<import optional="true" plugin="org.openntf.domino.xsp"/>
The Notes template is on a server. How do I get them in there or solve the problem, I have tried various import methods to no avail, this area is not a strong point for me.
Thanks for any help.
You cannot use an NTF with XPinc. The status bar will show a message about it not running. You can have an NSF with a TEMPLATE NAME that will refresh other database that inherit from that template. If you need the NTF for database creation purposes, develop in an NSF that has a TEMPLATE NAME from which the NTF inherits. (EG: MyAppDev). THe NTF then has a TEMPLATE NAME from whihc other databases inherit (EG: MyApp)
If you're getting an error that you cannot import a class in Domino Designer, there are two places to look.
The library needs "ticking" on the Xsp Properties. This tells the application that it needs that particular plugin at runtime. If it's missing on the server, you'll get an error.
The library needs installing for every Domino Designer that's going to be used to work on the application. Upgrading Notes to a new version will invariably disable previously installed plugins, so you need to go to File > Application > Application Management.... Custom plugins are in the second category, and if they have a red circle crossed through, it's disabled and needs re-enabling.
I am having a problem with Domino Designer and, to be honest, am not sure if the question belongs here or not...
When I create a new XPage, then drag the Single Page Application from the Mobile panel to the XPage I am not getting the Wizard?
I am using Designer 9.0.1, have installed the current OpenNTF ExtLib (901v00_03.20140120-0650) from OpenNTF and made sure that the correct version is referenced on both the Server (using the tell http osgi ss com.ibm.xsp.extlib command) and in Designer (About / Designer / Plug-in Details).
Does anybody have an idea what I am doing incorrectly?
Thanking you in advance
Ursus
The Extension Library release comes with a couple of updateSite zips inside of it:
updateSiteOpenNTF.zip
updateSiteOpenNTF-designer.zip
updateSiteOpenTNTFExtended.zip
updateSiteOpenNTFSamples.zip
Be sure you are using the updateSiteOpenNTF-designer.zip, and not the standard updateSiteOpenNTF.zip. The designer zip, as the name suggests, contains the extlib content specifically for Designer, such as the Single App Wizard, as well as the rest of the extlib plugins that come in the first zip file listed above.
I have a new XPages app with Domino 9 but I don't see an option to have OneUI3 there. I got also the XPages Demo App 2.0 from OpenNTF where this option exists, however I could not find where does it come from. If I just copy the demo app xsp.properties source code to my application, it does not work. Do I have to do something special with my application to get this theme?
There is no predefined choice or option for that.
Just edit the source of your XSP properties file OR create and use a theme. Extend the theme from the "oneuiv3.0.2" theme to get this working. Details here: http://mardou.dyndns.org/Privat/osnippets.nsf/snippet.xsp?documentId=96AB51B29A4F4369C1257B1D0064D05F
Server: Domino 8.5.3 / Window 2003 5.2
We have a strange Problem. Since a few days, we cannot apply changes to our XPage application. Even, if we make some few text changes and open the application, the changes are not displayed. We looked into the generated XPage-Java-classes, here we can see, that the changes were applied to these classes.
Also, we tried to create a new Test-XPage, but if we open this xpage, the error "404 item not found" is displayed.
We also tried this http://www-01.ibm.com/support/docview.wss?uid=swg21327454 but it doesn't help....
We have already restarted the http task and the server.
It looks very much like your XPages don't compile anymore. You can check that by opening the Navigator view in the Domino Designer and check webContent/web-inf/classes. Every XPage translates into a Java class and it seems that has stopped. You can try the Project menu option "clean" and you want to right click on the nsf and check the project properties if a builder has been disabled or is missing.
Next stop: reinstall Designer. Since the compilation happens in Designer, that's where you need to look