Hi everyone, I'm not certain if this should go in here or into the bugs section, but on the chance that I am just being naive, I will post it here.
I am liking this extension (it wouldn't work with loading prototype but after i switched to slimbox everything is behaving again and works like a charm) but I have one very big problem with it. The javascript section that declares the variables is repeated once per article on every category blog, even for categories / sections where commenting is diabled. That makes for about 15kb of redundant code on my front page, where I show ten blog entries (even though the "show comments link in blog view" is disabled!). I haven't been able to figure out how to fix this, and I haven't seen anything about this in the forums.
So my question is, is there a way to fix this (short of uncommenting the injection code - wherever it is - and adding this stuff to my template), or am I missing something, or is this a known bug that's going to get fixed eventually (hopefully)? Or is this (gasp) working as expected?
I am liking this extension (it wouldn't work with loading prototype but after i switched to slimbox everything is behaving again and works like a charm) but I have one very big problem with it. The javascript section that declares the variables is repeated once per article on every category blog, even for categories / sections where commenting is diabled. That makes for about 15kb of redundant code on my front page, where I show ten blog entries (even though the "show comments link in blog view" is disabled!). I haven't been able to figure out how to fix this, and I haven't seen anything about this in the forums.
So my question is, is there a way to fix this (short of uncommenting the injection code - wherever it is - and adding this stuff to my template), or am I missing something, or is this a known bug that's going to get fixed eventually (hopefully)? Or is this (gasp) working as expected?
Hi stani,
This has come up before and I think (not certain) that Max has posted a fix - if not, then he's said that it will be fixed in the next release. Sorry, I can't find the post right now.
Bob
This has come up before and I think (not certain) that Max has posted a fix - if not, then he's said that it will be fixed in the next release. Sorry, I can't find the post right now.
Bob
This topic is locked and no more replies can be posted.