PDA

View Full Version : SOS WysiwygPro and JA Submit Issues


SandraCristovao
07-24-2006, 08:11 PM
Hi,

Thank you for an excellent (JA Submit) component!

I am experiencing several problems with the WysiwygPro.

a) it will not save any new submitted content, only images.
b) it exposes all the image folders to anyone submiting content.

My Setup:

Joomla! 1.0.10
jasubmit 2.1


HAS ANYONE HAD THIS ISSUE, SHOULD I RECOMMEND A REFUND on the PAID EDITOR? :confused:

This is a a post I put up on the WysiwygPro forums.

Hi,

Your editor does not work with the JA Submit component, it fails
to deliver the promised goods. It is a shortfall for any joomla website that requires such an important feature.

Problem A: WysiwygPro fails to parse the content, typed in the editor.

The content comes up blank, only images are shown.

Problem B: WysiwygPro editor exposes the image folder to anyone who is submitting content on the frontend.

I have tried to implement a suggested workaround found in this forum.

Maybe I am not following the thread correctly.

For example

"You'll need support in your account management code to create a unique directory when you add a user. A good name to use for the dir would be the username (as usernames are unique - or at least should be if you know what you are doing!). You'll need to ensure that the username is a legal unix filename - if needs be restrict usernames to being merely upper or lowercase characters, numbers and the following characters _-.

Now, in the page that actually houses the editor you need to make an addition to the code that sets it up, namely:"

***********************
*Code from the forum *
***********************

$path="/path/to/image/parent/dir/";
$editor->set_img_dir($path.$session->username);


So I assume the intructions require me to find the file that contains the code to start the editor.

In my case it is located in the file of ja_submit.html.php (JA Submit joomla component).

******************************
*Code that starts the editor *
******************************
Line 222

if (!(hasInit()&&$my->id)){
initEditor();


*********************************************

Is this correct


***********************
*Code from the forums *
***********************

Line 222

if (!(hasInit()&&$my->id)){
initEditor();

$path="/****/****/public_html/image/stories/users/";
$editor->set_img_dir($path.$session->username);

Result, the image is put into the user folder but not in the actual
named user.


What can i do? Is this a weakness in WysiwygPro in the frontend.

What is causing the content not being published ie javascript?

How do you stop your editor exposing your joomla image folders to everyone in the frontend?

What needs to be modified JA Submit code or WysiwygPro?

If no solutions can be found, can you get a refund on WysiwygPro?

No point of paying for something when the free options work!

Thanks

JC

nathanbohn
07-25-2006, 09:05 PM
what version of wysiwyg pro?

jamief
02-20-2007, 10:31 AM
I have the same problem. I submitted a support ticket with WYSIWYGPRO and 8 hours later I have a reply. They are now working on it, and if we get an answer, I will post it here. The problem is CLEARLY not just Wysiwygpro, because in all other cases (JCE, MOSCE, My Content, etc.) WYSIWYGPRO holds up. The issue is with JA submit.

I for one, prefer to pay 45 US for a mambot like wysiwygpro that comes with unbelievable support from the source. Incredible detailed, courteous support.

cbolt
02-20-2007, 07:42 PM
A quick comparison of the code between JA Submit and Joomla’s built in Submit article component (com_content) confirms that JA Submit is where the problem is regarding content.

Open [Joomla Folder]/components/com_ja_submit/ja_submit.html.php

Find the javascript funtion called function submitbutton(pressbutton){

Within this function find this line of code:

submitform(pressbutton);

Replace it with this:

<?php
getEditorContents( 'editor1', 'introtext' );
getEditorContents( 'editor2', 'fulltext' );
?>
submitform(pressbutton);

It will then work fine.
And this fix works for all editors, not just WysiwygPro

The issue with WysiwygPro allowing users to see the contents of your image folders probably isn't a big deal, it allows them to select an image to insert into their article, but does not allow them to upload, edit, delete, rename or do anything dangerous... unless you turn this on in the WysiwygPro settings, and even then they need to be at least an author.