Geeklog Forums

On my site 80% of the time there seems to be a problem posting comments. see http://www.slashfilm.com/article.php/20051027214500662 and click the reply on the comment form on the bottom. It just redirects to the main page... any ideas whats wrong?

Make sure you have updated theme templates.

---

Geeklog Polish Support Team

It's the most updated version of Project_XU1, anyone else have any ideas?

Just out of curiosity, where did you get this "most updated version"?

---

Geeklog Polish Support Team

http://www.axonz.com/

If you are on Geeklog 1.3.11 the layout you downloaded from axonz.com is defenitely not up-to-date.

---

Geeklog Polish Support Team

okay then what I'm asking is what changes in the geeklog versions would cause this error, how can I fix it?

To prove it wasn't the theme causing the issues, I've now uploaded the comments directory from the PROFESSIONAL theme. We still experience the same issue where we just get sent to the main page when we hit reply...

Anyone have any idea why??? How can I fix this?

That's good news. You eliminated one possible reason.
Now tell us what changes have you introduced recently because it looks like comments still worked on Thursday, October 27 2005 @ 11:15 PM, look here

---

Geeklog Polish Support Team

Well thats the thing... the comments work sometimes. I think they can be access by pressing the post a comment link on the index page. But most of the time they don't work on the article page. I don't believe this is a new issue, it's been happening for a while.

Anyone? PLEASE? At this point I would like to just make a link to put in the commentbar.thtml file that says Reply and brings up the comment reply form. What html code would i use for this.... the form from the professional theme isn't working... I tried using the story id call in the url and that doesn't work... anyone????

It's a theme issue. That theme uses a few tricks here that don't seem to work in 1.3.11 any more.

For example, that Reply button isn't a real button - it's only a link. And if you hover over it, you'll see that all the parameters are empty.

Try adapting the commentbar.thtml from the Professional theme.

bye, Dirk

I think that helped as I was able to leave a comment.
However, the question remains "Is it or isn't it a theme issue ...?"
Anyone else have any ideas?

PS
BTW I hate when people just forget their problems the moment someone gives them a solution on a silver platter.

---

Geeklog Polish Support Team

Nothing was fixed, I just got busy with other issues.

I was able to issolate the problem to the


It doesn't refresh and shows a blank page. I fixed this with the hack included in the TinyMCE discussion. This hack usually works great but in this situation for some reason it reloads the main index page instead of the comment page. I can't figure out why. And before anyone suggests it, going back to the old refresh doesn't fix anything, you still can't get to the comments in firefox, so I need to find a better solution. Anyone?

I was able to add a link to the $url in the body of the old refresh:



But this isn't that professional looking, having a blank in between page where you have to click a link...

I just couldn't resist and installed the Project XU theme to see whether the trouble is the theme.
Looks like it isn't
I'm running a demo site based on Geeklog 1.3.11. I installed Project XU, after adding the missing files, as this is originally for GL 1.3.9.
I would like to make a statement: Comments do work in Project XU and Geeklog 1.3.11
Ergo, looks like you've done some customization resulting in malfunctioning comments. In this case I can hardly see anyone who could help you with this issue
You can see it in action here

Peace

---

Geeklog Polish Support Team

Wow, if you read my last 2 replies you would have already known this. It appears that I didn't explain it well enough, so here goes...

I installed a WYSIWYG editor into geeklog (tinymce). It has been well written about that any of these WYSIWYG editors cause a problem with the page refresh code in firefox (something having to do with the javascript, idunno) Anyways, a lot of the time you're greeted with a blank page (this is a com_refresh gone wrong). The fix to this problem was posted in the TinyMCE thread, it was a modification to the refresh code in libcommon which somehow told firefox to refresh in this situation. This fix worked great, with exception to the comment form call. Why I have no idea? If anyone could help me out with this (check the tinymce thread for the refresh hack and tell me why it doesn't work with the comment form Reply button... and how can it be changed to work.... I mean other than this, that hack was a great fix to this problem. I'm sure a lot of people are installing WYSIWYG editors into geeklog and coming up with the same problem).

What I did (as i stated in my last post) to temporarily fix this problem was I changed the refresh call back to unmodified. In the unmodified version it calls up a page which uses a meta refresh, but the page has no content. I added a link to the content of the page which basically says click here to continue and is linked with the $url call. This seems to fix the problem (like I said) however it looks a bit unprofessional to have this white page inbetween saying "click here to continue".

I liked the fix that was posted in the tinymce thread and am wondering how I could further fix that fix to work with the comments form.

Also why don't you guys add a body to the refresh page with a link (like I did) just incase someone encounters this type of situation (which I assume since a lot of people are upgrading to WYSIWYG editors, will happen). It's only an extra line of code and won't effect geeklog at all.

OK here we go again.
First of all I read all your posts very carefully.

So we eventually got to the bottom of the problem.
When anybody will experience the issue with comments that's the issue described below.
To summarize, the issue is with the additional line of code that is added to the lib-common.php after installing TinyMCE editor.

Comments by and large work the only thing that doesn't work is the Reply button and this applies to all layouts with TinyMCE editor installed plus the additional line in lib-common.php.

And last but not least, sorry to say but this thread is the good example of How-NOT-to report a problem.
You should state in the very first post that you installed TinyMCE, etc. But I guess by the time you found out there was a problem with comments you forgot about TinyMCE.
Thanks to our discussion here I've just found that there are problems with comments on my site now

---

Geeklog Polish Support Team

Is there a way to simply remove the "Reply" button until the issue is resolved?

Anyone?