Hello All,
I've just learned that the final dotcomments distribution (from 2001)
can be exploited to send outgoing spam. The hosting company I use has
disabled my /comments directory until I resolve this problem. The
related posts here seem to refer to spam appearing within comments or
email harvesting, not the exploit I'm getting hit with (perhaps I've
mis-understood the posts?).
Anyway, has anyone else experienced this problem? Is there a fix?
Thanks for your time.
Will this work for the 2.5 code as well? Impatient clickers (or people who don't
have the
capacity to understand SINGLE CLICK double post all the time. (and my server is
relatively
fast).
--- In dotcomments-support@yahoogroups.com, "meekut" <yahoo@w...> wrote:
> I wrote a quick addition to the 2.4 code that provides at least a tiny
> measure of protection against spam by making sure that any comment
> that's submitted is different from the last comment. This would also
> stop the accidental double posts that happen from time to time when
> someone reloads the comments page after posting.
>
> I'm pretty sure that this won't cause problems on any server that
> dotcomments already runs on, but it might, so make sure you have
> backups. :)
>
> My code replaces:
>
> --- Line 45ish ---
> if($banIPMode != 2) {
> $file = @fopen("comments/$commentID.comment", 'a');
> fwrite($file, $thisComment);
> fclose($file);
> }
> ---
>
> with:
>
> ---
> if($banIPMode != 2) {
> // dupe check \\
> $lastComment = @file("comments/$commentID.last.comment");
> if ($lastComment[0] == $dupeCheckComment) {
> $duplicateComment = 1;
> } else {
> $file = @fopen("comments/$commentID.last.comment", "w");
> fwrite($file, $dupeCheckComment);
> fclose($file);
> $file = @fopen("comments/$commentID.comment", 'a');
> fwrite($file, $thisComment);
> fclose($file);
>
> } // end dupecheck
> }
> --
>
> Very simple, and at least mildly effective. I'm working on a Slashdot
> style lameness filter as well. I'll let you know how that progresses.
> Feedback is very much appreciated.
>
> Thanks,
> Mike West
I realize that this post is old, but the number count problem seems to be a
common issue.
in the past I have used FTP to upload comments to old posts (like I did when I
switched
hosts). And it worked great.
I am wondering how well this wil work if I attempt it again (deleting and
uploading the
comments files and folder again), then changing the permissions to 777.
I don't really want to lose all of the comments, and wondered how much luck
anyone else
has had with this process. (thanks)
--- In dotcomments-support@yahoogroups.com, "boltyboy69" <matthew@m...> wrote:
> This works fine BUT you MUST delete the old comments files first.
>
> matthew Holt
> --- In dotcomments-support@yahoogroups.com, Listas <listas@o...>
> wrote:
> > Hello dotcomments-support,
> >
> > i was almost pulling my hair out, because the countcomments was not
> > working.
> >
> > then i discovered that the problem is on the readme file, line 204
> >
> > when you read:
> > <a href="javascript:viewComments(<$BlogItemNumber$>)"><? echo
> commentCount(<$BlogItemNumber$>); ?></a>
> >
> > should be:
> > <a href="javascript:viewComments('<$BlogItemNumber$>')"><? echo
> commentCount('<$BlogItemNumber$>'); ?></a>
> >
> > what's the big deal, you might ask.
> >
> > The big deal are the single quotes. If you use this line without
> > quotes, javascript will convert the huge number to another one, and
> > when PHP tries to open the file javascript funcion as passing to
> it,
> > the file doesn't exist.
> >
> > example: my postid was: javascript:viewComments
> (106147597912476108).
> > when the first user created a comment, PHP recorded a file
> > called "106147597912476110.comment". Since You use a
> nonquoted
> > number through javascript, you comment engine will work.
> But
> > not the counter. PHP will try to open the file
> > 1.0614759791248E+017.comment, and get a 404.
> >
> > But i could post and read, because javascript was passing
> > 106147597912476110 to the file comments.php.
> >
> > Then, when i figured out (after a bunch of alert()
> debugs), i
> > quoted the numbers and everything started to work. but i
> had
> > to rename my old comment files.
> >
> > It's a great comment system, simple and powerfull, with only a bug
> on
> > the installation instructions. great work.
> >
> > Oh; i also made the form a little more beatiful adding a line in
> the
> > style section (line 93), comments.php:
> >
> > input, textarea {font-family: <?php echo $font_face; ?>; font-
> size: <?echo $font_size; ?>}
> >
> > that's all folks. happy coding.
> >
> > system: msie 5.5, mozilla firebird, win2k sp4
How possible is it that this following change to my domain (this was an
announcment by
my domain host) is causing it?
<i>
<b>PHP Configuration Change, allow_url_fopen Disabled (Policy Change)</b>
Posted: Mar 16th, 2005 - 11:42:06 AM PST (1 day 5 hours ago)
PHP provides a feature allowing a programmer to open, include or otherwise use a
remote
file using a URL rather than a local file path. Unfortunately, that feature is
the source of a
large number of security holes in PHP web applications running on our servers
and we
have been spending an increasing amount of time handling issues resulting from
those
security exploits. In the interest of overall system security, we have decided
to disable this
feature as of now. We apologize for any inconvenience this may cause. Please
contact our
support team if you have any questions.
</i>
--- In dotcomments-support@yahoogroups.com, "peromedic" <peromedic@y...> wrote:
>
> http://www.perotheus.com/
>
> I am not sure what happened. I originally backed up my template code, edited
some
stuff with Greyduck's assistance in an attempt to not publish the email
addresses. I was
having problems with it (at some point I made the email field NON-Mandatory and
I don't
remember how I did that. And the code changes using his sample generated a parse
error
> in the php. So I put the original code back. (Which worked before).
>
> When the comment count didn't work, I searched the support boards for help and
now
my comments are all 0 (not just reading 0... literally the files are in the
directory but they
are not transferring. Quick version of the questions:
>
> - How do I upgrade all of the script code in the template and still keep the
old
comments?
I can use FtP to dowload all of my comment files before I change things, but I
can't figure
> out what went wrong when I made the above changes.
http://www.perotheus.com/
I am not sure what happened. I originally backed up my template code, edited
some stuff
with Greyduck's assistance in an attempt to not publish the email addresses. I
was having
problems with it (at some point I made the email field NON-Mandatory and I don't
remember how I did that. And the code changes using his sample generated a parse
error
in the php. So I put the original code back. (Which worked before).
When the comment count didn't work, I searched the support boards for help and
now my
comments are all 0 (not just reading 0... literally the files are in the
directory but they are
not transferring.
Quick version of the questions:
- How do I upgrade all of the script code in the template and still keep the old
comments?
I can use FtP to dowload all of my comment files before I change things, but I
can't figure
out what went wrong when I made the above changes.
Need to change permissions (chmod 777) on the script, the comment
folder, and possibly the folder containing the script. I had this same
set of errors a couple days ago...
--- In dotcomments-support@yahoogroups.com, "sexee_thugette"
<sexee_thugette@y...> wrote:
>
> hi this is my blog comments page http://www.pimp-
> vibes.net/comments/comments.php for some reason i get these errors
>
> Warning: fwrite(): supplied argument is not a valid stream resource
> in /home/pimpsnet/public_html/comments/comments.php on line 39
>
> Warning: fclose(): supplied argument is not a valid stream resource
> in /home/pimpsnet/public_html/comments/comments.php on line 40
>
> Warning: Cannot modify header information - headers already sent by
> (output started
> at /home/pimpsnet/public_html/comments/comments.php:39)
> in /home/pimpsnet/public_html/comments/comments.php on line 43
hi this is my blog comments page http://www.pimp-
vibes.net/comments/comments.php for some reason i get these errors
Warning: fwrite(): supplied argument is not a valid stream resource
in /home/pimpsnet/public_html/comments/comments.php on line 39
Warning: fclose(): supplied argument is not a valid stream resource
in /home/pimpsnet/public_html/comments/comments.php on line 40
Warning: Cannot modify header information - headers already sent by
(output started
at /home/pimpsnet/public_html/comments/comments.php:39)
in /home/pimpsnet/public_html/comments/comments.php on line 43
http://dailybugle.net/blog/testcomment.php
Ok, I've got everything working nicely now. Comments show up, the
count is accurate. Admin controls work. Spam protection is solid.
The only thing lacking right now is that the cookie doesn't seem to be
retaining the user info. I think usaf_angela mentioned the same issue.
Haven't found any good explanation for it yet, but I did notice that
it seems to be broken (dissabled?) on mobiustrip44's site as well.
Anybody have some ideas?
Heya, Mobius...been trying to get your Uber-script to work on my site, and I'm so close (and yet so far)!
I've tweaked it to "work" (meaning, look like it's working) on my site, in that the window will pop up and contain the previously-made comments that were submitted with the basic dotcomments script -- which I had working flawlessly. I integrated my customized code from the original script into yours to suit my preferred layout.
When I try to post a comment or login, however, I get nothing. Submitting the comment form results in a refresh of the comments window -- I get no comment added, no "comment status" messages, nothing. Also, the cookie doesn't seem to be "sticking," since I have to retype my info every time the window opens.
And ALSO (*whew*), when I try to click the "admin" link to enter my username and password, the script refuses to accept the username and password I enter, even though they match my variable values in comments.php. (When I set the $admin variable to "true," I can see the ban/delete links just fine, but I'm prompted for a username and password when I click on one, and, of course, the username and password I enter are rejected.)
Even when I ONLY change the form code and the variables at the top, it's doing the same thing. I've double-checked my form code to make sure I didn't leave anything out versus your version of the form, and the only variables I omitted from the top of the script are the style variables (since all my styles are done through classes on a stylesheet anyway).
Any thoughts? I've checked all the obvious stuff, like permissions and whether or not my caps lock was on. :p
Let me know if you need me to post my code... This will be pretty handy if I can get it working!
just added to the file library a tweaked-out version of dotcomments w/ comment deletion, IP banning, blogger post-page support, spammer checking, and url & lengthy-text truncation!
not for remote setups. may require additional tweaking to work on your server. doesn't seem to be compatible with dreamhost atm, but we're trying to work that out.
In case anyone was curious, I did figure out how to do some basic form
validation. At least, someone has to enter something resembling a
valid-looking email address to leave comments on my site, now. On the
other hand, I long ago tweaked the script so that email addys aren't
displayed on the page (by popular request).
If you're horribly curious, the source is here:
http://greyduck.net/comments.phps
I did have cgicomments setup a little while back. I'm hoping that once
I get this incarnation working that I'll be able to modify my old
comment files to the new format so that I can bring all the old
comments back.
Anyway, I'm currently testing the script stand-alone
(http://dailybugle.net/comments.php?12345) and have changed it to use
the absolute path the comments dir as you suggested. No luck there.
$comments_path = "/home/myaccount/public_html/comments";
Thanks!
--- In dotcomments-support@yahoogroups.com, "Angela Allen"
<angela@l...> wrote:
> Well, looks like your blog files are in /blog...your comments
directory and comments.php should be in there as well, according to
the dotcomments setup.
>
> Did you have the "normal" dotcomments version set up before? If
not, it might help if you use the system path to your /blog directory
instead of a URL in your $comments_path variable in both comments.php
and the PHP script at the beginning of your blog template. Doing that
solved all my installation problems. ;)
>
> Give it a shot and let us know how you get on...
>
>
> ~ Angela ~
> Proud wife of USAF SSgt Kerry Allen ~ 11 October 1999
> Proud big sister of USAF SrA "Dewey" Taylor
>
> --------------------------------------------------------------
> LunaClick.net ~ About Me ~ Albums ~ BlogSpace
> ECHS Alumni ~ Forum ~ LunaShoppe ~ PSP Goodies
> --------------------------------------------------------------
> RAF Mildenhall Spouses | Goodfellow AFB Spouses
> Pagan Military Spouses | PCS PSP | Mad About Tags
>
>
>
>
--------------------------------------------------------------------------------
>
> ----- Original Message -----
> From: Paul
> To: dotcomments-support@yahoogroups.com
> Sent: Monday, March 14, 2005 11:05 AM
> Subject: [dotcomments-support] Re: Überdotcomments
>
>
>
>
> Hi, thanks for the reply. I have the script and the comments directory
> located in the root of my public_html directory. Both script and
> comments.php are set to 755.
>
> I have the script edited to include my URL and the location of the
> scripts. I also have the tags from the template.txt file added to the
> page I have been testing with. In trying to narrow down the problem,
> I've been skipping the page itself and trying to get just the script
> to work by itself (http://dailybugle.net/comments.php?12345) and still
> can't seem to get it. Using the script by itself in this manner seems
> to work on your installation, so I figured this was a decent test.
>
> Looks to be an excelent comment system, so I'd love to get it working.
>
> Thanks again!
> -Paul
>
>
>
>
>
>
> Yahoo! Groups Links
--- In dotcomments-support@yahoogroups.com, "Paul" <w_stalions@y...>
wrote:
>
> --- In dotcomments-support@yahoogroups.com, "Dan \"Mobius\" Sieradski"
> <mobiustrip@t...> wrote:
> > paul -- did you follow the directions for previous dot comments
> > installations?
> >
> > you need to create a comments directory chmodded to 755 as as
subfolder
> > of the folder you're executing the script from
> >
> > then try again
>
> Hi, thanks for the reply. I have the script and the comments directory
> located in the root of my public_html directory. Both script and
> comments.php are set to 755.
>
> I have the script edited to include my URL and the location of the
> scripts. I also have the tags from the template.txt file added to the
> page I have been testing with. In trying to narrow down the problem,
> I've been skipping the page itself and trying to get just the script
> to work by itself (http://dailybugle.net/comments.php?12345) and still
> can't seem to get it. Using the script by itself in this manner seems
> to work on your installation, so I figured this was a decent test.
>
> Looks to be an excelent comment system, so I'd love to get it working.
>
> Thanks again!
> -Paul
An attempt at posting returns the following:
--------------------------------------------
Warning: flock(): supplied argument is not a valid stream resource in
/home/dailybug/public_html/comments.php on line 218
Warning: fclose(): supplied argument is not a valid stream resource in
/home/dailybug/public_html/comments.php on line 222
Warning: Cannot modify header information - headers already sent by
(output started at /home/dailybug/public_html/comments.php:218) in
/home/dailybug/public_html/comments.php on line 225
No comments found.
Add your comment: (Auto-line breaks enabled.)
Post successful.
--------------------------------------------
Host System info:
--------------------------------------------
FreeBSD 4.10-SATA-RELEASE
perl, v5.8.3
PHP 4.3.10
Well, looks like your blog files are in /blog...your comments directory and comments.php should be in there as well, according to the dotcomments setup.
Did you have the "normal" dotcomments version set up before? If not, it might help if you use the system path to your /blog directory instead of a URL in your $comments_path variable in both comments.php and the PHP script at the beginning of your blog template. Doing that solved all my installation problems. ;)
Hi, thanks for the reply. I have the script and the comments directory located in the root of my public_html directory. Both script and comments.php are set to 755.
I have the script edited to include my URL and the location of the scripts. I also have the tags from the template.txt file added to the page I have been testing with. In trying to narrow down the problem, I've been skipping the page itself and trying to get just the script to work by itself (http://dailybugle.net/comments.php?12345) and still can't seem to get it. Using the script by itself in this manner seems to work on your installation, so I figured this was a decent test.
Looks to be an excelent comment system, so I'd love to get it working.
--- In dotcomments-support@yahoogroups.com, "Dan \"Mobius\" Sieradski"
<mobiustrip@t...> wrote:
> paul -- did you follow the directions for previous dot comments
> installations?
>
> you need to create a comments directory chmodded to 755 as as subfolder
> of the folder you're executing the script from
>
> then try again
Hi, thanks for the reply. I have the script and the comments directory
located in the root of my public_html directory. Both script and
comments.php are set to 755.
I have the script edited to include my URL and the location of the
scripts. I also have the tags from the template.txt file added to the
page I have been testing with. In trying to narrow down the problem,
I've been skipping the page itself and trying to get just the script
to work by itself (http://dailybugle.net/comments.php?12345) and still
can't seem to get it. Using the script by itself in this manner seems
to work on your installation, so I figured this was a decent test.
Looks to be an excelent comment system, so I'd love to get it working.
Thanks again!
-Paul
paul -- did you follow the directions for previous dot comments
installations?
you need to create a comments directory chmodded to 755 as as subfolder
of the folder you're executing the script from
then try again
My comments were working properly and today the window width is
resizable in some browsers (ie / firefox on Windows and firefox on
mac) the window is not resizable on Safari for Mac.
It was working properly before-- and up until it was broken I had not
been editing my comments.php file.
I don't remember where that configuration is. ?
Checked out the site and tried out the script. I'm trying to get it to
work on my site and am having 0 luck.
http://dailybugle.net/blog/testcomment.html
Any input would be really welcome!!
-Paul
--- In dotcomments-support@yahoogroups.com, "mobiustrip44"
<mobiustrip@t...> wrote:
>
> just added to the file library a tweaked-out version of dotcomments w/
> comment deletion, IP banning, blogger post-page support, spammer
> checking, and url & lengthy-text truncation!
>
> not for remote setups. may require additional tweaking to work on
> your server. doesn't seem to be compatible with dreamhost atm, but
> we're trying to work that out.
>
> see it in action at jewschool.com.
just added to the file library a tweaked-out version of dotcomments w/
comment deletion, IP banning, blogger post-page support, spammer
checking, and url & lengthy-text truncation!
not for remote setups. may require additional tweaking to work on
your server. doesn't seem to be compatible with dreamhost atm, but
we're trying to work that out.
see it in action at jewschool.com.
Thanks angela - this got me most of the way there, everything seems to be
working now,
except the comment numbering system.
If you could, just have another look at:
http://feltron.com/
and tell me if anything still looks fishy.
cheers, nicholas.
--- In dotcomments-support@yahoogroups.com, "Angela Allen" <angela@l...> wrote:
> Just looking at the source code on your index page, and I'm seeing two things
that look
fishy...
>
> 1. Do your entry ID numbers typically have angle brackets (< >) around them?
If not,
you may want to fix that in your template code...
>
> 2. You're attempting to parse PHP code on a non-PHP page. :) Change your
generated
file extensions to .php, and your comment count should display correctly. I'm
seeing the
<? echo > and <? php > tags in your source code, which shouldn't happen.
>
> Double check those two things, and give us a shout if you receive any errors
after
republishing. ;)
>
> (I'm by no means a PHP guru, but I'm happy to help when I can...)
>
>
> ~ Angela ~
> Proud wife of USAF SSgt Kerry Allen ~ 11 October 1999
> Proud big sister of USAF SrA "Dewey" Taylor
>
> --------------------------------------------------------------
> LunaClick.net ~ About Me ~ Albums ~ BlogSpace
> ECHS Alumni ~ Forum ~ LunaShoppe ~ PSP Goodies
> --------------------------------------------------------------
> RAF Mildenhall Spouses | Goodfellow AFB Spouses
> Pagan Military Spouses | PCS PSP | Mad About Tags
>
>
>
>
----------------------------------------------------------------------------
----
>
> ----- Original Message -----
> From: ionclash77
> To: dotcomments-support@yahoogroups.com
> Sent: Tuesday, March 01, 2005 2:30 AM
> Subject: [dotcomments-support] Implementing problems
>
>
>
>
>
> Trying to implement comments into the news section of my design site.
Familiar with
> HTML, and PHP test has worked on the site, permissions seem to be set
correctly, but
the
> script seems to go nowhere - can someone please advise.
>
> http://feltron.com/index_test.html
>
> http://feltron.com/test.php
>
> thanks, nicholas
Just looking at the source code on your index page, and I'm seeing two things that look fishy...
1. Do your entry ID numbers typically have angle brackets (< >) around them? If not, you may want to fix that in your template code...
2. You're attempting to parse PHP code on a non-PHP page. :) Change your generated file extensions to .php, and your comment count should display correctly. I'm seeing the <? echo > and <? php > tags in your source code, which shouldn't happen.
Double check those two things, and give us a shout if you receive any errors after republishing. ;)
(I'm by no means a PHP guru, but I'm happy to help when I can...)
Trying to implement comments into the news section of my design site. Familiar with HTML, and PHP test has worked on the site, permissions seem to be set correctly, but the script seems to go nowhere - can someone please advise.
Trying to implement comments into the news section of my design site. Familiar
with
HTML, and PHP test has worked on the site, permissions seem to be set correctly,
but the
script seems to go nowhere - can someone please advise.
http://feltron.com/index_test.htmlhttp://feltron.com/test.php
thanks, nicholas
[ Phil, sorry about mangling your last name below...forgot the second 'n'! :-/ ]
I seriously considered scrapping the whole comments idea after going through Haloscan, dotcomments, remotedotcomments, and cgicomments.
Haloscan just plain ticked me off, (I like being able to tinker with my own code, but it's not worth $12 for the 'privilege'...IMO it's a right, doggone it!) and I couldn't get any of the three comments scripts to work for me to save my life.
Just when I was about to lose all hope (and throw my 'puter out my second story window), I thought of something I hadn't tried before... Instead of putting my URL as the $comments_path value, why not take a cue from the variable name (and NOT the documentation) and put in the actual server path?
Worked like a charm, first try!! ;-D
After a few more bumps and the accompanied swearing (for good measure, I guess), I was able to get everything working exactly the way I hoped I could. Now, the original dotcomments script is running flawlessly on my site, and I can actually devote time to posting in my blog, rather than wrestling with it!
Thanks for all your help, patience, and sound-boarding...feel free to check out my blog (although it's still a work-in-progress, and I'll undoubtedly be adding more links and stuff later). :)
Subject: Re: [dotcomments-support] Comments page not loading...
Alrighty, I tried Phil Ringalda's "Remote dotcomments" script (*waves to Phil*), and it works. :) I'm not sure why one would work and not the other, but hey, not looking in any gift horses' mouths lately...
Now the only problem is that my comment count under each entry isn't updating after the page loads. I'm still working the issue, but I may need to enlist you lovely folks' assistance again. :)
Alrighty, I tried Phil Ringalda's "Remote dotcomments" script (*waves to Phil*), and it works. :) I'm not sure why one would work and not the other, but hey, not looking in any gift horses' mouths lately...
Now the only problem is that my comment count under each entry isn't updating after the page loads. I'm still working the issue, but I may need to enlist you lovely folks' assistance again. :)
Subject: Re: [dotcomments-support] Comments page not loading...
John, I tried setting the permissions on comments.php to both 777 and 755, but no change. :(
Any other ideas?
I've been banging my head against this thing for days, and I'm not seeing any reason why it shouldn't work... I've half a mind to try the CGI version. :-/
John, I tried setting the permissions on comments.php to both 777 and 755, but no change. :(
Any other ideas?
I've been banging my head against this thing for days, and I'm not seeing any reason why it shouldn't work... I've half a mind to try the CGI version. :-/
Subject: Re: [dotcomments-support] Comments page not loading...
Hey Angela,
I recently started using dotcomments and I found I got some sort of error when everything should have been working right. What I was not doing was not setting the comments.php page (or whatever you named it) to access 777. In fact, 755 should work to, but try 777 and if your system doesnt work, do 755.
Dont know what I'm talking about? Whatever ftp client you use (i use SmartFTP), it should have access options in a properties part of each file that you can set. This sets read, write, execute access from different parties. I believe the UNIX command is CHCOM, but dont quote me on that, I use SmartFTP to make it easy. If you do get that perticular program, right click on the file you want to change access to, click properties, and change the access options in the text box with the three numbers in it (you can also select click boxes for each read/write/execute, but the numbers is easier for me.)
Anyway, thats the problem I encountered, and I hope it helps you.
I think you're asking why you're receiving email from me... Well, we're both a member of a mailing list on Yahoo Groups, and you're receiving emails from there. ;) I see it's been quiet for a while, so that might explain your confusion.
If you want to leave, all you have to do is send a blank email to
oi! he forgives me but.... I do not know of whom that you I stops. I am of Brazil, florianópolis and not entendu what you write much less why that you order as much email for me, forgives me... you could explains me why of this?
oi! he forgives me but.... I do not know of whom that you I stops. I am of Brazil, florianópolis and not entendu what you write much less why that you order as much email for me, forgives me... you could explains me why of this?
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador do Yahoo! agora.
Subject: Re: [dotcomments-support] Comments page not loading...
Hey Angela,
I recently started using dotcomments and I found I got some sort of error when everything should have been working right. What I was not doing was not setting the comments.php page (or whatever you named it) to access 777. In fact, 755 should work to, but try 777 and if your system doesnt work, do 755.
Dont know what I'm talking about? Whatever ftp client you use (i use SmartFTP), it should have access options in a properties part of each file that you can set. This sets read, write, execute access from different parties. I believe the UNIX command is CHCOM, but dont quote me on that, I use SmartFTP to make it easy. If you do get that perticular program, right click on the file you want to change access to, click properties, and change the access options in the text box with the three numbers in it (you can also select click boxes for each read/write/execute, but the numbers is easier for me.)
Anyway, thats the problem I encountered, and I hope it helps you.
Hey Angela,
I recently started using dotcomments and I found I got some sort of error
when everything should have been working right. What I was not doing was
not setting the comments.php page (or whatever you named it) to access
777. In fact, 755 should work to, but try 777 and if your system doesnt
work, do 755.
Dont know what I'm talking about? Whatever ftp client you use (i use
SmartFTP), it should have access options in a properties part of each file
that you can set. This sets read, write, execute access from different
parties. I believe the UNIX command is CHCOM, but dont quote me on that,
I use SmartFTP to make it easy. If you do get that perticular program,
right click on the file you want to change access to, click properties,
and change the access options in the text box with the three numbers in it
(you can also select click boxes for each read/write/execute, but the
numbers is easier for me.)
Anyway, thats the problem I encountered, and I hope it helps you.
-Jon, Jonz0r.com
> Hi, all. :)
>
> I've searched the message archives and couldn't find a solution to this
> problem, so I'm hoping someone who's figured it out can give me a hand.
>
> First, I'm not an HTML newbie, but I'm fairly new to PHP and am still
> feeling my way around it, for the most part. That being said, sometimes I
> can't see the forest for the trees, and it's often stupid little mistakes
> (like forgetting a quotation mark or semicolon) that kill me. :p I'm
> hoping another set of eyes might spot what I can't see... I usually use
> 1st Page as an editor, but I downloaded tsWebEditor for its error-finding
> tool...nothing turned up when I used it.
>
> My blog site is set up at http://blog.lunaclick.net (it's a work in
> progress, and the category archives aren't templated yet). I'm using Blog
> (http://www.farook.org) to publish, and as it's a Blogger emulator, a lot
> of the <insert content here> tags are the same or similar.
>
> The count seems to be ok so far (being that I have no comments on
> anything, and every comments link shows "No Comments," just like I want it
> to, LOL). When I click on the link, though, the comments window pops up,
> but it takes FOREVER to load, and when it loads, I get a "cannot find
> server/page cannot be displayed" error.
>
> I've tried different configurations -- even using the original
> "straight-out-of-the-box" versions, changing only my URLs and paths -- but
> no changes I make seem to be in a positive direction. :-/ I'm going to
> keep playing around with it, but here is the code that I'm using right
> now:
I've searched the message archives and couldn't find a solution to this problem, so I'm hoping someone who's figured it out can give me a hand.
First, I'm not an HTML newbie, but I'm fairly new to PHP and am still feeling my way around it, for the most part. That being said, sometimes I can't see the forest for the trees, and it's often stupid little mistakes (like forgetting a quotation mark or semicolon) that kill me. :p I'm hoping another set of eyes might spot what I can't see... I usually use 1st Page as an editor, but I downloaded tsWebEditor for its error-finding tool...nothing turned up when I used it.
My blog site is set up at http://blog.lunaclick.net (it's a work in progress, and the category archives aren't templated yet). I'm using Blog (http://www.farook.org) to publish, and as it's a Blogger emulator, a lot of the <insert content here> tags are the same or similar.
The count seems to be ok so far (being that I have no comments on anything, and every comments link shows "No Comments," just like I want it to, LOL). When I click on the link, though, the comments window pops up, but it takes FOREVER to load, and when it loads, I get a "cannot find server/page cannot be displayed" error.
I've tried different configurations -- even using the original "straight-out-of-the-box" versions, changing only my URLs and paths -- but no changes I make seem to be in a positive direction. :-/ I'm going to keep playing around with it, but here is the code that I'm using right now:
Before headers in template_journal.php (/www/x/xxxxx/ replaces my actual path):
<?
function commentCount($n) { $comments_path = "http://blog.lunaclick.net/comments/"; $filesystem_path = "/www/x/xxxx/blog/htdocs/comments/";
In <head> tags in template_journal.php (within <script> tags, of course):
function viewComments(n) { window.open('/comments.php?' + n, 'Comments' + n, 'directories=0,height=480,location=0,resizable=1,scrollbars=1,toolbar=0,width=515'); }
I was wondering if there is another way to disable comments for a particular
post/
comment file (such as changing the permissions on the ####.comment file) - is
that the
best way to do it and affect ONLY that comment file from further posts?
(I want to close a particular discussion before they start drawing blood)