JavaScript Errors in Admin-Interface

cybermat · Post by **cybermat** » Wed Jan 10, 2007 8:05 am

Hi,

i dont't know what happend. I and the other authors of the blog, don't unsing IE at any time. We are writing our entries, on windows, linux and OS X machines, using firefox.

The errors occured to me and a second author at the same time, on 2 independent machines, one windows and the other os x. We talked about it, and tested our serendipity-installation at work, with windows and linux, and got the same behaviour. So the same errors occured on 4 different machines, with 3 different operating-systems. We testet firefox, ie and safari. For that i don't think, we did something wrong.

Perhaps it's magic....

Greetings,

Mat

Post by **garvinhicking** » Wed Jan 10, 2007 10:35 am

Hi!

Okay, that's a good note. It definitely means that it should be client-unrelated, so that only leaves the server and involved scripts.

Maybe zorans guess is the right one, that Google changed their JavaScript of the geotagging-plugin, which lead to new problems. I myself don't use the Google-JS script, is there a chance to get knowledge if they changed their script?

Best regards,
Garvin

zoran · Post by **zoran** » Wed Jan 10, 2007 10:42 am

garvinhicking wrote:Maybe zorans guess is the right one, that Google changed their JavaScript of the geotagging-plugin, which lead to new problems. I myself don't use the Google-JS script, is there a chance to get knowledge if they changed their script?

It was not my guess

I have just now installed the autosave plugin, which works fine next to geotag. I guess Google need not to have changed their code then ...

Perhaps a conflict with another plugin?

cybermat · Post by **cybermat** » Thu Jan 11, 2007 8:53 am

It's really magic. Now it's doesen't work anymore. When i want to edit an article, i still have to deactivate the geotag plugin, that the buttons work fine. Then i edit the article, save it, and activate the geotag plugin once again...

The autosave plugin is removed. The other plugins are:

* Geotag
* Textformatierung: Serendipity
* Textformatierung: NL2BR
* Browser-Kompatibilität
* Spamschutz
* Spartacus
* Freie Artikel-Tags
* Lange Einträge aufteilen
* Sonderzeichen/Erweiterte Buttons für Non-WYSIWYG
* Benutzerprofile
* Statistiken
* Nächster/Voriger Artikel
* Karma
* Einträge ankündigen
* Spamschutz (SURBL)
* Spamschutz (RBL)
* Lightbox/Thickbox JS

No problems with the other plugins installed an activated. Perhaps i have to remove all of them, and make tests with each plugin together with the geotag plugin, to find the combination that doesn't work...

Post by **garvinhicking** » Thu Jan 11, 2007 8:58 am

Hi!

Wow, this is getting weird. Let's go through the plugins:

* Textformatierung: Serendipity
* Textformatierung: NL2BR

Those two should be absolutely uncritical as they do not emit any Javascript

* Spamschutz
* Spartacus
* Lange Einträge aufteilen
* Statistiken
* Nächster/Voriger Artikel
* Karma
* Einträge ankündigen
* Spamschutz (SURBL)
* Spamschutz (RBL)

Those should also be uncritical

* Browser-Kompatibilität
* Sonderzeichen/Erweiterte Buttons für Non-WYSIWYG
* Freie Artikel-Tags

Those also emit JS in the backend and could be a possible culprit!

* Benutzerprofile
* Lightbox/Thickbox JS

I don't know about those two, but I believe they don't deal with the backend.

HTH,
Garvin

cybermat · Post by **cybermat** » Fri Jan 12, 2007 8:45 am

I haven't found the time jet, to remove some plugins and test again. What i have done, i have compared wich plugins i have installed on my other blog.

I have 2 serendipity-blogs running, both on the same webspace. i have compared the event-plugins, and found out, that i have the same plugins, on both installations, but the geotag-plugin only on one of them.

And i have no problems with the installation, without the geotag-plugin, all works fine.

At the weekend i will make some more tests...