[Closed] moodle 2.0 & R0.4

antonio wrote:

Sorry again, doing many things at once

I double-checked and in fact the code is still there. Just set auto-height to No in wrapper config, and it should not appear.

Please test and tell me if it solves it. If not, I will take a deeper look.

i set auto-height to No and it works but as you know auto-height is essential for correct display of moodle contents inside the wrapper. Setting auto height to no results in hiding lots of stuff from Joomla...

what shall be done in order to hide all alerts and set autoheight back to yes?

The problem is that auto-height feature DOES NOT WORK with Moodle 2.0.

I am far from a Javasccript expert, so I really don't know how to make it work.

In fact, auto-height code was ported "as is" from JFusion, I did not develop it myself. This same code, does not work with Moodle 2.0.
As for my debugging, it seems it can't read the wrapper height correctly....but as I said, I know almost nothing about JS

The error you reported (xmlrpc coding eror) happened to me.
It was difficult to trigger, as only happened when tring to update a non-existant user session in Moodle.

Fixed now, thank you!

antonio wrote:

The error you reported (xmlrpc coding eror) happened to me.
It was difficult to trigger, as only happened when tring to update a non-existant user session in Moodle.

Fixed now, thank you!

great . one more bug fixed then .

was it a bug caused by an rpc call by the component?
which means that if i update the component to the latest verison you sent me won't happen again?

yes, it should not appear if you upgrade.

The error was in the new code to sync sessions, as this have changed totally from 1.9.

OK antonio. one more xml-rpc call error:
XML-RPC Error (623): Calling parameters do not match signature

and it happened all of a sudden when i tried to login with a username and password which was working fine till that moment. And in fact now the whole site does not open. The error triggers every time you try to open the site.
This probably means that is triggered by an active module.

any ideas?

Hi.

We are about to release R0.4 today, so I am more than interested in knowing what happens.

Is your site public? If you want I can try to work with you to diagnose the problem. Send me a private email, and we will work on it.