Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

since installing 3.6.9 my Joomla content editor pop-up windows no longer return the URLs selected

  • 4 antwoorde
  • 25 hierdie probleem
  • 1 view
  • Laaste antwoord deur jayemmee

more options

I recently upgraded to Firefox 3.6.9 and found that when using the editor in a Joomla 1.0.15 website , the content editor pop-up windows no longer return URLs selected (eg: image or file URL to be used in a link). I have been using the site with no problems for many years, and the problem was cured when I reinstalled 3.6.8

I recently upgraded to Firefox 3.6.9 and found that when using the editor in a Joomla 1.0.15 website , the content editor pop-up windows no longer return URLs selected (eg: image or file URL to be used in a link). I have been using the site with no problems for many years, and the problem was cured when I reinstalled 3.6.8

All Replies (4)

more options

So far I have had absolutely no response to this Forum post, but I can tell you that this is still a problem in the new release (3.6.10). So once again I am forced to revert to 3.6.8

Gewysig op deur jayemmee

more options

Not impressed with this forum - absolutely no response!!!!

more options

A good place to ask questions and advice about web development is at the mozillaZine Web Development/Standards Evangelism forum.

The helpers at that forum are more knowledgeable about web development issues.

You need to register at the mozillaZine forum site in order to post at that forum.

See http://forums.mozillazine.org/viewforum.php?f=25

more options

Thanks cor-el but the problem is not in my web development but is a new issue/problem in FireFox which was not present in all versions up to and including version 3.6.8 and was only introduced in version 3.6.9. I have also established that the same problem also exists in FireFox version 4 beta 6 and have therefore also raised a second question today.

My understanding was that I should raise these issues in this forum, but I will also check out the other forum.