CMS Made Simple Forums

Hi,

I have recently installed CMS MS and its working fine. Now I uploaded the Comments module to the modules directory and it shows up under "Extensions" -> "Modules" where I activated it.

I followed the instructions and inserted the tag {cms_module module="comments"} somewhere on a page. This creates a link labelled "Add A Comment". Thats nice but when I click on it - just nothing happens. My browser (Firefox 1.5.0.1) reloads the page, displays the following link

../index.php?mact=Comments,m3,addcomment,1&m3action=default&m3returnid=29&m3returnid=29&page=29

but no further action.

Whats going wrong? Did I misunderstand something?

Thanks for any hint.

Oliver

Oliver wrote: I followed the instructions and inserted the tag {cms_module module="comments"} somewhere on a page. This creates a link labelled "Add A Comment". Thats nice but when I click on it - just nothing happens. My browser (Firefox 1.5.0.1) reloads the page, displays the following link

Hmm, works fine for me with CMSms 0.11.2, Comments 1.3 and Firefox 1.5.0.1  .

Have you checked the source code ? Some editors breaks this sign " to an entity ...

Thanx cyberman for the help (in english this time...) but source is clean. The fact it does display "Add A Comment" seems to indicate some other reason, doesn't it?

The only difference with your configuration is version: I have 0.12 "Fiji". Are there some known issues with that version? Is there a reason for you not to upgrade?

Oliver wrote: The fact it does display "Add A Comment" seems to indicate some other reason, doesn't it?

Hmm, think this would be a bug - same error on Firefox and IE with 0.12 here.

Are there some known issues with that version? Is there a reason for you not to upgrade?

Please look here and decide  ...

i have the same prob here.. 

I think that this is a confirmed bug, and wishy Ted willl have it fixed in 0.12.1

thanx, the bug is fixed in 0.12.1. Great job!

Aggghhhh! (© Black beast of aggghhh)

I had just made another pleading post here: http://forum.cmsmadesimple.org/index.ph ... 861.0.html

Then I decided to see if there were any mesages on the board I could help with, then I found this! Looks like a similar problem to me. I guess I'll just have to upgrade and hope for the best.

Update: Alas no, that didn't solve it. Sorry for the interruption.

Clear your cache.  The upgrade should've fixed the problem.

Hi Ted,

I've tried clearing my browser cache and then even tried clearing all of my private data - I'm still seeing the same problem.

Just to be clear this thread http://forum.cmsmadesimple.org/index.ph ... 862.0.html says that running an "upgrade.php" is not required as there are no DB changes. Should I run the install/install.php file included in the upgrade package?

I was a little scared to run it incase it reverted my site back to a default install.

Thanks for your help.

Oh, sorry.  Not the browser cache.  The CMSMS cache.  Site Admin->Global Settings in the admin.  Click the Clear Cache button.  Normally upgrade.php will do this for you automatically, but since you dont' have it, this is the workaround.

I'd never been in that part of the admin, very cool.

I was pretty excited about getting this solved, but it didn't seem to fix things. I cleared the cache and got the message "cache cleared" and I then clicked submit down the bottom, but the problem still exists.

I have instant messaged you a link to the site in case it might help for you to see the problem first hand.

You can see the version number in the footer is "12.1"

Thanks for your time, Ted. You're very kind.

I just downloaded CMSMS for the first time yesterday so my version is definitely the latest.  I have the same problem.

You'll have to get the latest svn version of the comments module (not the snapshot, as these fixes are red-hot).  or wait  till tomorrow, when the snapshots are updated overnight.... and this problem will be fixed.

Hi Calguy,

Do you have any suggetions as to how I might fix this for piFaq and Glossary? It's pretty much the exact same problem described here, but it involves those two modules instead of Module Comments.

Should I just rebuild the site on a Scarsborough release? Or is there a more recent release that didn't have this issue? What do you recommend?