Hi all
back to my previous post just to put the solution may be it will be helpful
to someone in the community, so after returning to focus on '2.1.6 ==> 2.6
upgrade' we still having the encoding problem after authentification, the
problem was in our DB data and exactly in the test username dat
Hi Khaled,
Do you still have this problem?
Regards,
Lukasz
On 07/09/2012 04:22 PM, Khaled--enda-TN wrote:
hi Lucasz
i tried the recomanded environement but always the same problem, a
white page after typing login and pwd. With tomcat 7 i got the same
prob too
attached the log file
---
hi Lucasz
i tried the recomanded environement but always the same problem, a white
page after typing login and pwd. With tomcat 7 i got the same prob too
attached the log file
--
---
2012-07-09/12:41:45.546/WAT INFO, org.mifos
Thank you Lukasz for your answer, i will try this recomendations and i'ill
keep you updated.
Le vendredi 6 juillet 2012 10:52:07 UTC+1, Lukasz Chudy a écrit :
>
> Hi Khaled,
>
> I am still trying to reproduce issue that you described but I am not able
> to. I noticed that you are using *Jetty 7
Hi Khaled,
I am still trying to reproduce issue that you described but I am not
able to. I noticed that you are using *Jetty 7.6.4.v20120524* and also
*java-1.6.0-openjdk-1.6.0.0.x86_64*. It would be good if you change
Jetty *7.6.4* to recomended version *7.3.x*
(http://archive.eclipse.org/je
Hi
Thankyou John for your help, now i am able to post on the group i was
confused about which adress must i use to post my gmail adress or my enda's
adress (used to subscribe).
ready to send you more details if needed
thanks
Le jeudi 5 juillet 2012 12:20:13 UTC+1, John Woodlock a écrit :
Sorry, I missed this bit from Khaled:
the test DB is a fresh dump of our prod DB and i followed this tut to
setup jetty in our centos server
http://www.tinhtruong.me/2011/08/setting-up-jetty-74x-on-centos-5x-as.html
[9:24:15 PM] Khaled Jamel: because we are running 2.1.6 under tomcat 7
[9:24:33 PM
Khaled also wrote:
just for information, we are now runing 2.1.6 V, i tried to apply
upgrades from 2.1.6 ==> 2.2.1 => 2.2.2 => 2.2.3 => 2.3.0 => 2.3.1 =>
2.3.2 => 2.4.0 because i thought that the problem because we are
moving from 2.1.6 to 2.4 directly, but still got the same result
On Thu, Jul 5
