text in text-area gets deleted with each safe

Hi,

I just now installed the ninja-journal.
I find it is working on the admin site okay.
However, there is a problem:
Each time I type some text to put additional info in it gets deleted on save!
For instance with a project: inside the text-area down below in the admin-page for a project I see "1" as a text. I delete that and type in some sentences, and save the page: all text inside the text area is deleted, and again there appears this mysterious "1"???

I am using the latest template of bamboo, with a jquery plugin that loads some stuff in the head of the template. Bit with a standard joomla template I get the same bug. (And also I am on the admin site, with the classic template for it: Kephri.)
The plugins that are added are active, its now sqli for sql.

Any advice?

Best regards,

Paul

Hi Paul,

We've never experienced that issue before, and I just tested again to be sure.
I've tried using save, apply, no matter what I do it's not turned into '1'.

What kind of text editor are you using? tinyMCE or something else?
Also, when you change to khepri, are you making sure that the possible system plugins you got running are disabled as well?

If not, try disabling one by one to find out wether there's a conflicting one.

Thanks,
Stian

Hello Stian,

Thanks for your quick response: much appreciated.

I went looking for bad system plugins: could not find any. I de-activated the lot (those that can be de-activated that is). Made no difference at all. (Also not after flushing cash memories where I could.)

Bit the way: I get the bug using tiny, but also using jce.

I tried re-installing everything ninja-journal again: but than I saw that the nooku component Koowa was not activated: so I activated the Koowa component.

The same bug: mysterious 1, again.

When I went looking to the Koowa compoinent I read this errot-message:
"Warning: rsort() expects parameter 1 to be array, null given in /home/praktij1/public_html/administrator/components/com_koowa/views/html.php on line 29"

So there is our 1! It is a parameter 1.

I did re-install the ninja component but this did not solve the problem.

Howerver I suspect the error-message tells you stuff?
For me: I do not understand it at all.

Any advice?

Cheers,

Paul

That error is fixed, it's just a warning that don't cause any errors in overall.

Also, Koowa component are not meant to be used until Nooku FW turns stable, it's currently alpha.
It's an extension that handles installing Nooku FW in one go, and the second feature is one click updating.
But obviously with Nooku FW being in rapid development, we do not advice you to upgrade to the latest nightly of it as chances are it'll break our code.

So here's one more thing you could do.
Use a browser like Google Chrome.

Right click anywhere on the page and click "Inspect Element". This will bring up the web inspector.
I want you to click "Console". Console will show you any and all errors and warnings in the javascript on the page.

I have a hunch that the error in your case are javascript related. So doing so, and pasting your errors and warnings in here, will really help us finding out what's wrong.

Otherwise it'll be like trying to follow a map without a compass if you understand what I'm saying :)

If the error are indeed a js one, then reinstalling everything wont change it. So the fact that it don't further indicate it.

One more thing, do you have any script related plugins running? Like "System - Mootools Upgrade", "System Mootools 12"?
NinjaJournal are using Mootools 1.2 in the admin, and we make sure that the joomla js continues working.

However, since we started doing that before any of these other mootools related plugins got here, chances are we might be in conflict.
Same goes with potential jquery plugins, or hacks in the menu manager.
By hacks, I mean stuff like extended query paramaters, like RokNavMenu got. We're compatible with that one, but I hope you understand what I mean by that.

All in all what I'm saying is what do you have installed on your site, that differ from a vanilla install?
We collaborate tightly with most template clubs, so chances are I'm able to install the same software as you in order to resolve things much faster.

Telling us your server and joomla specs could also help.
Things like your php version, joomla version etc.

Thanks,
Stian

Hi Stian,

I did try to find something useful, but had no success I think:

"Right click anywhere on the page and click "Inspect Element". This will bring up the web inspector.
I want you to click "Console". Console will show you any and all errors and warnings in the javascript on the page.

I have a hunch that the error in your case are javascript related. So doing so, and pasting your errors and warnings in here, will really help us finding out what's wrong."

I did as you asked: no error, no message, no anything.

"One more thing, do you have any script related plugins running? Like "System - Mootools Upgrade", "System Mootools 12"?
NinjaJournal are using Mootools 1.2 in the admin, and we make sure that the joomla js continues working.

However, since we started doing that before any of these other mootools related plugins got here, chances are we might be in conflict."

I do have a template with javascript activated: so I de-activated these: no change.

"All in all what I'm saying is what do you have installed on your site, that differ from a vanilla install?"

Well it is almost a vanilla install:
components: jce, joomla update manager (Sam Moffats one, the dutch version) and Ninja journal
template: Joomlabamboo template Rasa v. 1.0 (with Zen Grid Framework, v. 1.0.5.3)
Plugins: joomla bamboo plugin jb-library (I de-activated this one but that did not change a thing); I did have the plugin (and the module) cache cleaner by NoNumber, I de-installed that one and got no change at all.

"We collaborate tightly with most template clubs, so chances are I'm able to install the same software as you in order to resolve things much faster."

I can give you via pm an inlog as superadmin to the site if you wish.

"Telling us your server and joomla specs could also help.
Things like your php version, joomla version etc."

php: 5.2.14
apache: 2.2.16
joomla: 1.5.21

The site runs on one of Rochen's servers.

Hope this helps,

Best regards,

Paul

Hi Stian,

I installed a new Joomla site to test a complete vanilla version: I installed the ninja journal component, I get told all is well.

I get exactly the same error: I make a new project at the back-end; I type in a text in the textarea, and save this: it gets changed for the mysterious cyfer 1!.

I have downloaded a new copy of the component; I made a brand new test site: does not change anything.

So I reluctantly have to stop trying this out.

Sorry and good luck.

Paul

ok, sorry it didn't work out for you.

Regards,
Stian

Hey, you guys ever get anywhere with this issue? I have the same problem. When adding todos or logs it replaces the description with the number 1. Here are my server specs and I'm using TinyMCE. Mootools Upgrade plugin is all I have in the way of Mootools

PHP 5.2.13
Joomal 1.5.22
Mysql 5.0.77
Apache 2.2.3
Firefox 3.6.13 (although I have the same problem in Internet Explorer)

Shows up in the frontend as a 1 also. I did look under the Content tab of Firebug's Inspect Element and no errors show up. All I have for Mootools showing up in my plugins is System-Mootools Upgrade. Does Mootools 1.2 come as a core plugin that wouldn't normally show up in my plugins? I like the look and feel of NinjaJournal...would love to be able to use it. Thanks.

Update: Actually I've noticed this under the Tasks tab also. It's always in the TinyMCE editor when composing descriptions. Should I just try to install a different editor, like JCK?

Hi,

We're scheduling the Stable release of Ninjaboard next week, and since Ninjaboard and NinjaJournal runs the same framework, we'll also release a new version of NinjaJournal.

We havent tested NinjaJournal with that plugin on, so there's likely a conflict happening.

And to answer your question, yes the MooTools Upgrade plugin were introduced in Joomla! 1.5.18 and is now part of the Joomla CMS.

Could you also try and test with Google Chrome?
Might be worth a shot to also try the "No editor" option just to see if it's really an editor issue, or a saving issue in our code on the server side.

Thanks

Well, I tried Google Chrome and the same thing happens. I tried setting my default editor in my Global Configuration to No Editor and the same thing happens. I tried installing the JCK Editor and the same thing happens. I know that the first time I tried to use NinjaJournal I also had NinjaBoard installed and it didn't react well in the backend either, as I recall. It had some errors and quirks pop up, but without reinstalling it I couldn't say what they were. As I indicated, I uninstalled it due to all its errors. I'll try the stable release of both when they come out and report back. Obviously there's something whacky and if some other plugin were causing the problem I can't say which one it would be. I doubt it's another plugin at this point, but you're the experts, not me. I'll try other stuff if you have anything to recommend. I know I've been using ninjaXplorer this past week because eXtplorer had problems where NinjaXplorer has been working for me thus far. Your stuff is nice; I really like the look, feel and overall performance if I could get past the quirks. Thanks for your help guys. Good stuff really.

Hi,

Yeah Ninjaboard have been using a more recent version of NAPI, our mini framework for extensions.
I'll let you know once both are out, that will resolve any issues with using different versions of NAPI.

I'll also change our editor helper code so that it respects your editor settings. Right now it's hardcoded to using TinyMCE.

I'm glad you like our stuff, I know you'll like the new versions :)

Thanks. So I've got some extensions on my site that won't work with my db server set to mysqli. I don't suppose there's a work around on your side to this is there?

Hi,

Unfortunately we can't run on MySQL without the MySQLi php extension.
This is because we make use of important security and performance features that are only available in MySQL 4.1 or later.
The aged MySQL php extension does not let you use those features.

So the only solution would be to update those extensions to support the Joomla! 1.5 database API, which lets you support MySQL and MySQLi connections both at once with the same code.

If you open a separate thread with a list over those extensions you're having trouble with, I'll be happy to take a look at them and create patches for them that we may send the devs so they can take advantage of being Joomla native :)

Thanks

Hi,

We're just wrapping up NinjaJournal for the stable release.

But before we do, I just want to make sure that it resolves your reported problems.
Here's a nightly up for grabs: http://cl.ly/1A1q2O2p303h343G0d1y

Please let me know how it goes.

Thanks

Installed it and the other extension (without you giving code to them) will not work with mysqli in the configuration. This is not to mention that creating todos and tasks in the component still pops a number 1 instead of the text in the description field. I know I've posted under the Ninjajournal category of the forum describing this also. Thanks for working on it though. Can I ask why you include the Koowa plugin that requires the mysqli when it's not used in the Ninjajournal component?

Dirk

Hi,

Since I'm unable to reproduce this issue on my localhost, could you give me an temporary super admin account?
Send it to stian at ninjaforge dot com.

As for your mysqli question, it's not that simple unfortunately.
I can perfectly understand your frustration.

Let me just explain a couple of things.

# What's Koowa

Koowa is just a system plugin that loads the Nooku Framework.
Nooku Framework is a RAD (Rapid Application Development) framework on PHP.
It's similar to Codeigniter, cakePHP, Zend Framework.
The difference however is that Nooku Framework is made by Johan Janssens and the Nooku community with the needs of Joomla developers in mind.

# Is NinjaJournal using mysqli or Koowa?

Yes it does, but we don't render an message telling you to turn on mysqli, we do it for you when needed and only notify you when we can't.

# Why are NinjaJournal and Nooku Framework requiring the MySQLi PHP extension?

Both extensions connect with a MySQL database. The difference between the two PHP extensions is comparable with PHP4 vs PHP5. MySQL is going to be deprecated in favor of MySQLi in PHP6. And Joomla! 1.6 have MySQLi as the default option when you install it.

So MySQLi really is the future. Asking why we're not just using MySQL just because a few extensions that don't use native Joomla APIs isn't compatible when the site is configured to MySQLi is the same as asking us why we're not PHP4 compatible just because some extensions are unable to function on PHP5.

Hope that answers your question :)

Hi,

Any news on this?

I'm not frustrated, just bummed I can't implement your stuff. I'm not exactly sure what giving you super admin privilege entails. Can there be 2 super admins because as it stands I've been the only one? I know you're trying to help me out, but is it a wise thing to give strangers a super admin account? Is this something we need to schedule so I know when I can remove the temporary super admin account when your done? It seems from the Joomla forums like that's not necessarily an easy thing to do. Just trying to get some clarity and the warm and fuzzies over giving out a super admin account. Thanks.

Dirk

Hi Dirk,

The benefit of giving me temporary super admin access is that I don't have to spend time trying to reproduce this issue.
Actually, I have already spent hours trying to reproduce this issue but no success.
You have the problem right on your site, so if I had access there, I could've identified and started working on a fix within minutes.
Without access I might not even be able to fix it at all, not if it's server related or a 3rd party extension conflict of some sort.

Like Mark says, you definitely shouldn't give access to strangers.

But if you check our reputation, our current posts as well as what people are saying about us you'll discover that not once have we ever abused a super admin account. I don't even know what gain we could have from doing anything that would harm your site or business, because things like that would ruin our business entirely the second it goes public.

Thanks

OK, I sent you an email stian. Thanks for your help.

Dirk

Hi everyone,

Just an update, thanks to Dirk's help with lending us his server, we were able to identify, resolve and release a fix to this problem within hours.
The latest version no longer have this issue :)

Cheers!

No, I need to be thanking you, Stian. You not only got the mysqli issue resolved with implementing Ninjajournal and the LMS app, but you also resolved the issue I was having with the descriptions being rewritten in Ninjajournal to the number one. I'll say it again...you're the best Stian!

Dirk

Thanks! :)

Hi!

I just installed NinjaJournal 1.0.0 rev 466 and am also getting this issue - all log description values are changed to "1" for new logs and updating the description on existing logs.

What was the fix you performed manually on Dirk's site to get this working?

Hi,

The problem where the Tidy filter being used. It should be using 'html' instead of both 'html' and 'tidy'.

You do this by running the upgrade script.
Run it by clearing your com_ninjajournal cache and visiting the dashboard afterwards.

You may need to upgrade to 1.0.1 first. You can find the whole upgrade script in /administrator/components/com_ninjajournal/install/upgrade.php

Hope this helps.

The link on the NJ components page is still giving me com_ninjajournal_v1.0.0rc_rev466. Can you provide a link to 1.0.1?

Also - the upgrade script does not appear to be present in rev466.

Whoops, sorry.
Making a new build right away!

It must've been uploaded by mistake when we migrated from Joomla 1.0 to 1.5 here on ninjaforge.com.
The right package is uploaded now. So when you upgrade it should fix the filters automatically.

Sorry for the inconvenience.