I can't find the post again. I'll keep looking, but the changed file was:

components/com_fireboard/template/default/plugin/announcement/announcement.php

Around line 242 (get JFactory::GetEditor) it died because it was not retrieving an editor. The suggested fix was to insert a line of code that accessed a different editor.

That's only the first problem, though. Fixing it lets you edit and post, which apparently worked in one of the J1.5 RC candidates. But in the stable the post doesn't display (blank fields) and you can't access it to re-edit. So there's obviously another problem (database?).

Hope that helps you to get started -- I'll keep looking for that missing post.

Here is the problem - announcement.php

Code:

if ($do == "add" {
if (!$editor) {
die ("Hacking attempt";
}

if i add this line, it works OK !

Code:

$editor =& JFactory::getEditor();

Here is the URL:

www.bestofjoomla.com/component/option,co...w/id,37136/catid,83/

That's the post with the fix. I can't figure out how to implement it. The instructions aren't very specific. If anyone knows how or can describe in better detail how to edit the code, I and many others I am sure would really appreciate it.

BTW announcement.php is in /components/com_fireboard/template/default/plugin/announcement.



PLEASE SOMEONE HELP US!!! My wife is going cracked with this problem on her site.

I changed one line of code to fix the problem.

In the components/com_fireboard/template/default/plugin/announcement/announcement.php file around line 246 the code reads:



Change this statement to read:




That should do it.

That seems to work just as well as adding the line mentioned 2 posts above somewhere around the top of announcement.php... However, I'm getting a white editor, only buttons are visible, the text is white on white... Which stylesheet do i have to edit in order to be able to see what I'm announcing?

TIA
Best regards
x

AWESOME!

Thanks Steve. How did you ever figure that out. I've been working on it for hours.

Great work and thanks for the help. I'm sure this will help a lot of people. Is there some way to mark this issue as resolved?

Cheers!

FIXED FIXED FIXED!!!

This bug has been around seemingly forever. Thank you, SHoward!