Welcome to Geeklog, Anonymous Friday, September 29 2023 @ 05:35 am EDT

Comments for Geeklog's Advanced Editor

Geeklog's Advanced Editor | 47 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Geeklog's Advanced Editor

Authored by: LWC on Monday, May 29 2006 @ 06:29 pm EDT

Relax, I just pointed out that your problem had nothing to do with SR3 (which full name I stressed so you'd release each Geeklog version has SRXs...) as SR3 didn't touch the subject. In SR3 Dirk suggested to upgrade FCKEditor.

And it's funny you find it logical that others would look for it for hours and hours. I mean, at least say "I don't find it logical when I know others probably know exactly what's wrong".

Geeklog's Advanced Editor

Authored by: LWC on Monday, May 29 2006 @ 06:30 pm EDT

release=realize

Geeklog's Advanced Editor

Authored by: Agent X20 on Tuesday, May 30 2006 @ 05:42 am EDT

I fully appreciate SR3 is a security release. However I mentioned it simply to state clearly that I was running the latest version. I've been running a GL site for well over three years so I know how the patches work - but that's not gonna stop me hoping optimistically that wee fixes might not find their way in. The updated files didn't suggest any changes in the suspected areas so naturally I came here to ask around and see if it was on anyone's radar.

I've seen people talking about updating the editor ever since it was released, but having dug around in the code in the past it struck me as being reasonably heavily modified by Blaine so I was naturally reluctant to delve into that myself. Plus I see that 1.4.1 isn't all that far away...

Re hours and hours, I said it was logical to ASK if the problem had been fixed first, before I went looking at code, IN CASE someone else has already nutted it out. Frankly to not ask before diving in would be daft - well unless you've got oodles of free time and some of us don't.

Seems to me that Dirk summed things up nicely. He clearly stated the problem lay in the FCKEditor, that he had a workaround in GL, and that an upcoming release of GL with the newer editor should fix it, and if not the fallback is there just in case. Short, succint, and brimming with nuggets of information. Very nice and exactly the feedback I was hoping for.

If it reads like I'm harping on about this, well from where I'm sitting this is something that's plastered across my site and isn't working right. It's certainly one of the most visible bugs I've seen in my three years plus running GL so I was hoping it wasn't just me getting the problem (another reason to ask again). And if no-one was aware of it I was fully prepared to put some time into it to try to work out just what was going on. The fact that Dirk came straight back with a classy response just reaffirms just how good he and his team is and how worthy they are of our applause and support.

Geeklog's Advanced Editor

Authored by: LWC on Tuesday, May 30 2006 @ 10:08 am EDT

Actually, we've had a whole discussion about this:
http://www.geeklog.net/forum/viewtopic.php?showtopic=65522
and we feel Blaine was smart enough to barely touch FCKEditor and even more so, most of what he did modify was just changing the defaults to his likes.

Truth be told, the only 100% Geeklog related thing he did (the custom Javascripts aside because they're not part of FCKEditor) was modifying FCKEditor's config.php to catch Geeklog's config.php's $_CONF_FCK['imagelibrary'], which kind of wastes resources (see my post in that topic) but I admit I didn't find a better way.

I say smart enough because this is exactly the reason it's relatively easy to upgrade (full instructions by samstone and by myself are provided in the aforementioned topic).

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks