I've found it. Must be something with XOOPS though. I'm not sure. I've had a look at the line that caused the problem and found out that the language argument 'nl' caused the problem.

Originally, Spaw used language definitions located in the /spaw/lib/lang/ folder. But because of the integration with Xoops, it seems it now uses the XOOPS system for language definition, meaning the actual language definitons are made in files in the /spaw/language/ folder.

By replacing the 'nl' argument with an empty string ('') in the line I mentioned earlier, the Spaw class refers to the default language set in the spaw_control.config.php file. In my case this was 'en'. This solved the problem.

It might have something to do with XOOPS obligating the use of the XOOPS languaging system? I don't have a clue why all of a sudden it stopped working, when it had been working for weeks... Maybe someone else upgraded some XOOPS files.

Hope this helps!
Thanx again!

Hmmm maybe... or perhaps the PHP include virus? Strange...
Don't have any other leads at the moment.
It might be useful to try Spaw outside of Xoops, to see if that works. If it does, we know it's a XOOPS problem. Otherwise, it's a Spaw problem.
Thanx!

Quote:

I'm not sure if this is the correct place for this post, but here goes anyway...

About 6-8 weeks ago I installed the Spaw editor module and adapted a couple of lines in the form of the submit page (storyform.inc.php) of the News module so I could use it. All worked fine, untill today. I haven't changed anything, but all of a sudden, the submit.php page returns blank.

I turned on PHP debugging, but no errors are returned. In fact, nothing, not a single bit, is returned to the browser.

I did some tracing and found that the following line causes the blank page:



If I comment this line out (and the following lines dealing with Spaw editor), all is fine. The problem starts with this line. The include to the Spaw code, which comes just before this line, doesn't cause a problem. t.

It seems to me like there's a die() or exit() statement somewhere. Why else would a blank page be returned all of a sudden? Does anyone have any ideas?

Thanx heaps!

fortunately, a team is working on a lotto/sweakstakes/prize/giveaway kind of XOOPS module called XOOPS Lotto.

http://kittin.dynu.com/modules/news/article.php?storyid=24&com_id=2&com_rootid=1&com_mode=thread

Quote:

Hi there,

did some searching on this and other XOOPS sites' forums, but was unable to find what I needed. I was wondering...

I grabbed the cascade menu javascript from javascriptsource.com (http://javascript.internet.com/navigation/cascade-menu.html) to make a nice cascading/mouseover menu on a couple of images, but unfortunately, I found out that our xcgal scrolling photo module javascript (http://www.dordtrocks.nl/tmp/modules/xcgal/) was interfering, as the cascade menu seemed to work on every page but the ones that had that scrolling photo block on it...

my question is if anyone has any experience with cascading menus in XOOPS and if there is a sollution to this problem or some javascript/DHTML out there that works well in xoops. any comments suggestions greatly appreciated!