Welcome to Geeklog, Anonymous Friday, March 31 2023 @ 09:29 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: Robin on Tuesday, February 28 2006 @ 09:43 am EST

"- I'm still getting "read more (1 word)" on all of my stories despite having nothing in the body."

I suspect this is caused by some default html tags that are preloded in FCK. If you, before saving a story, cklick on source in the main body text you should see the default tags. Try removing them before saving

---
Geeklog Polish Support Team

Geeklog's Advanced Editor

Authored by: Agent X20 on Tuesday, February 28 2006 @ 02:16 pm EST

I'd already tried that. It looks like it injects a couple of br tags but they're not evident in the source.

Geeklog's Advanced Editor

Authored by: Blaine on Wednesday, March 01 2006 @ 04:36 pm EST

Try adding this option to your public_html/fckeditor/fckconfig.js file.

FCKConfig.IgnoreEmptyParagraphValue = true;

---
Geeklog components by PortalParts -- www.portalparts.com

---
Geeklog components by PortalParts -- www.portalparts.com

Geeklog's Advanced Editor

Authored by: Agent X20 on Friday, March 03 2006 @ 04:51 pm EST

That value is already set.

Geeklog's Advanced Editor

Authored by: geKow on Sunday, March 05 2006 @ 07:31 am EST

that didn't help :(

---
I am not a dev. Use my rants at your own risk!

Geeklog's Advanced Editor

Authored by: Agent X20 on Monday, May 29 2006 @ 07:13 am EDT

This "read more (1 words)" problem is still apparent in SR3.

Any chance of a fix to this? Makes my GL site look silly with every story not containing a body (which is most of them) all listing "read more (1 word)"...

Geeklog's Advanced Editor

Authored by: LWC on Monday, May 29 2006 @ 10:01 am EDT

I suppose you mean v1.4sr3...

Anyway, what does it have to do with this problem? Not only did Dirk not claim to have upgraded FCKEditor but he actually mentioned he didn't upgrade it...

I would have said to upgrade it yourself like Dirk suggested, but I'm not sure that would solve this problem as this is a Geeklog problem. All I can say is that it sometimes happens and sometimes doesn't, so if only someone told us what triggers it, it would have been nice.

Geeklog's Advanced Editor

Authored by: Agent X20 on Monday, May 29 2006 @ 05:29 pm EDT

Of course I meant sr3 - what else would I mean?!

What does it have to do with this problem? I posted this issue a ways back as the *parent* of this post.

Dirk didn't suggest upgrading in this part of the comment thread.

You say it sometimes happens and sometimes doesn't - well I'm saying it happens most of the time if not all of the time. Every story on the front of my GL site has it.

As for telling you what causes it - seems logical to me to ask if it's been fixed before I go trawling around in the code for hours and hours.

Thanks for the attitude. Thankfully Dirk has posted a most helpful response below.

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).

Geeklog's Advanced Editor

Authored by: Dirk on Monday, May 29 2006 @ 02:02 pm EDT

We have a workaround in CVS. It's more of a kludge, really: It checks if the bodytext contains only that BR tag and removes it if that is the case.

We will probably ship Geeklog 1.4.1 with FCKeditor 2.3 and either that upgrade fixes the problem or the kludge will have to stay in.

bye, Dirk

Geeklog's Advanced Editor

Authored by: Agent X20 on Monday, May 29 2006 @ 05:35 pm EDT

Thanks for the prompt response Dirk!

Very pleasing to see that this has been looked at and that if FCK 2.3 doesn't resolve the problem you've got it in hand.

Been running a GL site for over three years now - and am always impressed by the work you do.

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