After updating ExpressionEngine, from 2.3.1 to 2.5.3, clicking on Add-ons > Fieldtypes returns a server error. I used the Updater add-on to run the updates. Has anyone had this issue before? If so, how did you remedy it?
I've just run into this issue. The library for fieldtypes which a few third party fieldtype modules depend on has been moved as of 2.4. You'll need to scan through any third party field type addons and manually update them. Here's a quick list of modules I have had to update
Matrix
Wygwam
Google Mx
Solspace Calendar
Favorites (solspace)
Related
I have an XPages application that has been running quite happily for the last couple of years.
The application uses some Java classes as converters that are used to convert data entry on certain fields to upper case, proper case, etc. This functionality has been present and working since the app was first deployed.
Today I was asked to make a change to one of the pages, adding a new field. The change was made in a test copy of the database, the app rebuilt and tested and all was fine.
The same change was then promoted into the live database, but after being rebuilt the error
Can't instantiate class: 'Cannot find class uk.co.xxx.beans.UpperCase in NSF'.
is being returned.
I have tried rebuilding the app and cleaning the project numerous times without success. I have also tried amending the code in the Java class and rebuilding.
If I remove all references to the UpperCase class it then complains about the ProperCase class. It appears as if the app has lost its reference to the Java classes and rebuilding isn't fixing the problem.
As an interim solution I have removed all uses of these classes so that users can at least display the page - but this is obviously not a long term solution. As soon as I reinstate one instance and rebuild, the error returns.
The only change in the app has been the addition of the new field. Removing it makes no difference.
Can you suggest anything else I can try and what may be causing the problem?
Open production db in designer and using Navigator view open WebContent/WEB-INF and delete classes folder. Then rebuild the app or refresh it from template again.
Sometimes classes are not updated correctly. I've seen it few times.
I have seen this too (domino 8.5.3). I recompile until it eventually works. With a restart of the http task thrown in for good measure. How are you deploying the classes within the db or as jar files in lib/ext?
I ran into similar issues with 8.53 FP2 with the same "can't instantiate errors" if accessed by a designer client. I even put a PRD in at IBM for it.
In order to fix this problem we had to update to the server and clients to FP5. We had a work around before we could update the FP5. We had to modify how the application was rolled out. Once the database was updated from a template we had to do a clean then a build while use our Application ID used for signing applications.
http://www-01.ibm.com/support/docview.wss?uid=swg21639571
JDAE8ZV2CX
XPage With Java Design Element Breaks When Domino Designer opens after applying 8.5.3 Fix Pack 2 interim fix of any 853 Fix Pack 2/Fix Pack 3 hotfix
I'm trying to install Nwazet Commerce with Orchard 1.7.2.
Suddenly, nothing happens. No new menus, no errors, nothing in the logs, nothing. It is just as if I hadn't installed it.
Before you ask... yes I've enabled the modules.
I can't find even a single scrap of documentation. What is supposed to happen? I would expect to see some extra menus or something on my dashboard or perhaps some extra content types, but there's nothing.
Help please :-|
You can't. The current version in the source repository is only compatible with the 1.x branch. See https://bitbucket.org/bleroy/nwazet.commerce/issue/20/update-to-17
I have a version for 1.7.2 unfortunately I don't know what fork it was from so I don't know what bugs or issues were included.
I found it in my saved orchard files and tested quickly you will get the admin options.
Download available here
I have a XPage application where I use JavaMail in one of my managed beans. Currently I have added the jar-file C:\Programme\IBM\Notes\framework\shared\eclipse\plugins\com.ibm.designer.lib.javamail_9.0.0.20130301-1431\lib\mail.jarto the build-path of the manged bean. This works well. But now I want to use a newer version of JavaMail as the Domino server uses version 1.3 but I need version 1.4.x.
I have downloaded the new JavaMail jar-files from Oracle. In Domino Designer (version 9) I add this jar-file to the new design element "Code / Jars" and remove the old jar-files from the build path.
My managed bean is still compiling and running as desired, but if I check the version the bean is using it reports still version 1.3. To check the version number I use the debug property of JavaMail and it's reporting version 1.3 to the domino server console.
Is there a way to tell the domino server to use the jar-files in the application (i.e. the nsf) and not his own? Is there another approach to update the JavaMail version?
The reason I want to use a newer version of JavaMail is as follows: I want to read mails from an imap server with ssl. To avoid the problem of importing ssl-certificates I simply want to trust all hosts. This can be be done via MailSSLSocketFactory, but this is only available since version 1.4.2. Therefore I want to use a newer version of JavaMail.
Another reason I want to use a newer version is as follows: the method "getSortedMessages" of "IMAPFolder" is only available since version 1.4.4. (and so are some other features of JavaMail).
This may be a little too late for you... I think the right approach may be to include the jar file as an OSGi plugin.
I have spent some time to figure out how to do that - and recently succeeded :-) I have described the steps to perform to make this work in two articles. The first is about wrapping a JAR into a plug-in: http://www.dalsgaard-data.eu/blog/wrap-an-existing-jar-file-into-a-plug-in/ - the second is about deployment (and there is a link in the first one).
/John
You can solve the problem by creating an OSGi plug-in that supersedes the one that sports the JavaMail library: com.ibm.designer.lib.javamail.
In order to do that do the following:
Create an OSGi plugin whose id is com.ibm.designer.lib.javamail (Dalsgaard's tutorial on how to do it)
Set its version to a higher number than the one the Domino server is shipped with (to know the version type tell http osgi ss com.ibm.designer.lib.javamail). As of now using 9.0.1.qualifier should be fine
Deploy the plugin either through an update site or by directly copying it under the domino\workspace\applications\eclipse\plugins folder.
Restart the HTTP service. The higher version - the one you created - will now be used
I've got the same problem here, but found a solution. Be warned, this is not the best answer but it will work. Simply download the latest javamail jar here and rename the jar file to 'mail.jar'. Just replace the current file in IBM\Notes\framework\shared\eclipse\plugins\com.ibm.designer.lib.javamail_9.0.0.20130301-1431\lib\mail.jar with this file. Quit the http task and restart it. The code will now work with the latest version.
I have a remote operations tool made in python and I have distributed it to my friend and he is using it good.
Now, whenever I add a feature to my app i would have to text him the link of my app (manual update type thing) which is bugging for a while.
So is there anyway I could add a auto-update feature a.k.a. check for update to my application for a automated update???
I googled about this but I couldn't find anything related and so I am stuck
Thank you in advance
There is a library called esky in which if you freeze with it, it can check for updates on a certain website, get a list of avaliable versions on a certain website, distribute patch files, and much more. check out here: esky p.s. I dont know if there is a version for 3.x though.
I have just upgraded a site from 1.0.6 to 1.0.9 and now am unable to add new users. I go through the process in the back end and all seems ok but they do not appear in the user list under Manager Users.
However, checking in the database they do appear in the modx_manager_users table, but not in the modx_active_users table.
Would anyone know what I can do to fix this?
Turns out it is a commone issue with 1.0.9 and is able to be fixed by installing 1.0.10
http://forums.modx.com/thread/83325/modx-1-0-10-rc-need-testers