Dear FireBoard users,
In order to further develope the need of Joomla for a robust forum, FireBoard component has been moved to its own new home and new name. You can find more information regarding the Kunena, the successor of FireBoard, at kunena.com. The current forum here will stay for some time more for referencing needs. You can find the FireBoard files under joomlacode.org and other files
Upgrading to Kunena is highly recommended!

Kunena! - To Speak!

A revolution is coming... Kunena - Swahili for: To Speak! THE Next generation of native Joomla based Forum ultra component. Forget what you know about Joomla based forums...
Amazingly Simple Lean and Clean Easier Customization
Kunena is about to redefine the world of Joomla! with the most simplistic ultra component out there. For ultimate performance based on state of the art development techniques, Kunena! is about to bring you... With an integrated plugin system that will allow you to extend Kunena beyond your wildest imaginations...
New announcement -> Hacking attempt
TOPIC: New announcement -> Hacking attempt
#37136
New announcement -> Hacking attempt 9 Years, 10 Months ago  
I\'m testing on latest SVN of Joomla 1.5 and FireBoard 1.0.4 Stable and when i try to add new announcement as administrator
[code:1]index.php?option=com_fireboard&func=announcement&Itemid=55&do=add[/code:1]
i get this error:
[quote]Hacking attempt[/quote]


Here is the problem - announcement.php
[code:1] if ($do == \"add\"«») {
if (!$editor) {
die (\"Hacking attempt\"«»);
}
[/code:1]

if i add this line, it works OK !
[code:1]
$editor =& JFactory::getEditor();
[/code:1]
#37136
New announcement -> Hacking attempt 9 Years, 10 Months ago  
I\'m testing on latest SVN of Joomla 1.5 and FireBoard 1.0.4 Stable and when i try to add new announcement as administrator
[code:1]index.php?option=com_fireboard&func=announcement&Itemid=55&do=add[/code:1]
i get this error:
[quote]Hacking attempt[/quote]


Here is the problem - announcement.php
[code:1] if ($do == \"add\"«») {
if (!$editor) {
die (\"Hacking attempt\"«»);
}
[/code:1]

if i add this line, it works OK !
[code:1]
$editor =& JFactory::getEditor();
[/code:1]
#43987
Re:New announcement -> Hacking attempt 9 Years, 9 Months ago  
This hack worked for me as well. Thanks for posting it. I\'ve read all of the posts about the evils of WYSIWYG editors and have concluded that this should be an admin\'s decision. My users are \'trusted\' but not \'techie\' and no matter how you slice it, bb code is just too difficult for them. They are familiar with MS-Word and nice editors like FCKeditor have been very well received by them. Hope we\'ll see hooks in Fireboard for these in the future.

All told though, Fireboard rocks.
#49106
Re:New announcement -> Hacking attempt 9 Years, 7 Months ago  
:( I tried both ways by changing code. It is not working. I am new to coding business. I mace changes in notepad, saved as the same name & extension & uploaded the php file by ftp. But it is not working.
#49956
Re:New announcement -> Hacking attempt 9 Years, 6 Months ago  
Try change the code block to this:

[code]
if ($do == \"add\") {
$editor =& JFactory::getEditor();
if (!$editor) {
die (\"Hacking attempt\");
}
[/code]
TBK
#54920
Re:New announcement -> Hacking attempt 9 Years, 3 Months ago  
Hi, i\'m try to this solitions, but its working only for hacking attempt warning. When i puss the add button, hacking attempt not shownig any more. But i can\'t still access any editing page or adding page. Help?
#54935
Re:New announcement -> Hacking attempt 9 Years, 3 Months ago  
fixed in FB1.0.5
#54941
Re:New announcement -> Hacking attempt 9 Years, 3 Months ago  
Ok, but i cant find 1.0.5 download. where can i find it or upgrade my 1.0.4 stable to 1.0.5?
Tnx.
#54942
Re:New announcement -> Hacking attempt 9 Years, 3 Months ago  
Sorry, but only the Nightly Builds are available at this moment. Please look [url=http://www.bestofjoomla.com/component/option,com_fireboard/Itemid,38/func,view/id,54379/catid,78/]here[/url].
#62845
Re:New announcement -> Hacking attempt 8 Years, 11 Months ago  
Actually the fix is to change:

if (!$editor) {

to

if (!$is_editor) {


It was just a typo.
Page: 1