Thread: Re: [pLog-General] 0.3
Brought to you by:
jondaley
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-25 22:26:39
|
on 26/10/03 7:18 AM, Oscar Renalias at os...@re... wrote: > Anything you're missing from > 0.2 and that you'd like to see implemented? 1. Auto making links and stuff. So I can just paste text, with http:// links and *@yomcat.geek.nz ones without having to worry about putting in any HTML code. <br> and <a> would be the best two tags. 2. Better stats. I installed the package from http://htmlfixit.com/free.php and its pretty cool. Complimenting your current one, of course. 3. Spell Checker 4. Get rid of the "target=_blank thing from link tracker. I'm sure I could think of more. -- Mike Welsh Proud to be 98% Microsoft Free |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-25 22:58:12
|
on 26/10/03 11:27 AM, Mike "yomcat" Welsh at yo...@pa... wrote: > I'm sure I could think of more. I can ;) 5. Timezone support. -- Mike Welsh Proud to be 98% Microsoft Free |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-26 04:35:58
|
on 26/10/03 11:27 AM, Mike "yomcat" Welsh at yo...@pa... wrote: > I'm sure I could think of more. Just one more (at the moment): 6. Allow https:// links to be posted in the Links section without adding a http://. -- |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-26 18:07:11
|
on 27/10/03 12:00 AM, Oscar Renalias at os...@re... wrote: > Hi! > >>> Anything you're missing from >>> 0.2 and that you'd like to see implemented? >> >> 1. Auto making links and stuff. So I can just paste text, with http:// >> links and *@yomcat.geek.nz ones without having to worry about putting in >> any HTML code. <br> and <a> would be the best two tags. > > Then I think we should define an additional mode for editing posts, so that we > would have visual editing with htmarea, plain normal text editing where the > user would have to type all the html code, and a third one where newlines > would be converted to <p> tags, links would be automatically converted to <a> > tags and so on... Shouldn't be too difficult to implement. > Okay, sweet. I don't use the htmlarea one because Safari gives me Mozilla area messages and IE chokes. >> 2. Better stats. I installed the package from http://htmlfixit.com/free.php >> and its pretty cool. Complimenting your current one, of course. > > I know our stats are crappy but we never intended to get anything else other > than the referers. If you need better statistics, I'd suggest the php-based > package called phpOpenTracker. It's great, supports keeping track of multiple > websites/pages with only one db, has daily stats, weekly stats, monthly > stats, yearly stats, referer tracking, and many more: > http://www.phpopentracker.de. > > Also, once 0.2 comes out I will release a plugin that integrates pLog and > phpOpenTracker. Since pOT supports statistics for more than one site with one > installation, we can keep separate statistics for different blogs, which > makes it suitable for places where pLog is serving more than one blog. > > In the beginning I thought about integrating it in the core of pLog but after > a short discussion here, it was decided that we could offer such > functionality as a plugin because not everybody was interested in something > like that. And I also agree. I'll take a gander. It sounds interesting. PIty I already installed the other one (its made by my host, so I get free copies for testing. Sorta like a CVS) > >> 3. Spell Checker > > That's also something I've been considering but it would require of a tool > such as pspell/aspeel in Linux. And don't even know if it works in Windows... > > We'll think about it :) > I could get a JS one that might work. Its from phpBB, so you'll need to reprogram it. >> 4. Get rid of the "target=_blank thing from link tracker. > > That's an easy one... You can edit yourself the linktracker.template file and > remove it! ;) yay! But thats the wrong thing (I think). Look at my link tracker <http://yomcat.geek.nz/plog/index.php?op=LinkTracker&blogId=1&PHPSESSID=dd45 092d7c5a21792d86fe676e123c6a> you should see what I mean. > >> 5. Timezone support. > > At the moment I don't think we can offer support for timezones, because of the > simple fact that all the dates stored in the database are in the timezone in > where the db server is. In other words, the dates stored in the db are not in > GMT and applying a timezone to those dates would be quite difficult. > > What we can do is give the user the possibility of specifying a time > difference, so that the correct dates would be calculated based on that time > difference. That is, if your server is in Perth and you post something at > 18:30, you could tell pLog that you're 5h behind that time and pLog should > then automatically substract 5h from the original date. Same diff. I was thinking of checking the time to a databsae time servers somewhere in GMT, then doing the difference thing, but this is fine. > >> 6. Allow https:// links to be posted in the Links section without adding a > http://. > > That was a bug (thanks for spotting it :)) that I have just fixed in CVS. Will > be there for 0.2. > > If you come up with anything else, let us know! > > Oscar. -- Mike Welsh IT Manager Bruce Welsh Architect |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-26 18:43:54
|
on 27/10/03 7:08 AM, Mike "yomcat" Welsh at yo...@pa... wrote: > I could get a JS one that might work. Its from phpBB, so you'll need to > reprogram it. I've got in here on my HD. I'll put a download link up. If you get this right away, they may not be up. Mac users: http://yomcat.geek.nz/spell.sit Windows users: http://yomcat.geek.nz/spell.zip *nix users: http://yomcat.geek.nz/spell.tgz Yes, I am bored. -- Mike Welsh IT Manager Bruce Welsh Architect |
From: Oscar R. <os...@re...> - 2003-10-27 18:52:21
|
I'll have a look at it. Hope I'm not making you feel disappointed if I say that it's not a top priority at the moment, but I can promise we'll have a look at it because I also have to admin that would be nice to have ;) One just needs to find the time to do everything... Cheers, Oscar. > on 27/10/03 7:08 AM, Mike "yomcat" Welsh at yo...@pa... wrote: > > I could get a JS one that might work. Its from phpBB, so you'll need to > > reprogram it. > > I've got in here on my HD. I'll put a download link up. > > If you get this right away, they may not be up. > Mac users: http://yomcat.geek.nz/spell.sit > Windows users: http://yomcat.geek.nz/spell.zip > *nix users: http://yomcat.geek.nz/spell.tgz > > Yes, I am bored. |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-26 18:48:18
|
> I'm sure I could think of more. whatever: Put the admin files in a seperate /admin directory etc. Having that many files in the base directory is unsettling... -- Mike Welsh Proud to be 98% Microsoft Free |
From: Oscar R. <os...@re...> - 2003-10-27 18:52:30
|
> whatever: Put the admin files in a seperate /admin directory etc. Having > that many files in the base directory is unsettling... Yeah, that was really ugly, I know :D Development for 0.3 has started and amongst other things, we've already reorganized the mess of files into which 0.1/0.2 had turned. You can have a look at how the new folder structure looks like from CVS: http://cvs.sourceforge.net/viewcvs.py/plog/plog/ I think it looks nicer :) Oscar. |
From: Mike \yomcat\ W. <yo...@pa...> - 2003-10-28 04:23:46
|
on 27/10/03 10:00 PM, Oscar Renalias at os...@re... wrote: > http://cvs.sourceforge.net/viewcvs.py/plog/plog/ > > I think it looks nicer :) Yes, thats much nicer. -- Mike Welsh IT Manager Bruce Welsh Architect |
From: <pl...@so...> - 2003-10-28 23:38:48
|
Hey all, anyone who wants to play with my Basic Documents Plugin, feel free. If you find any bugs, etc, please let me know: http://someblog.com (Take a look in the Files section on the right column for a file called plugindocuments.class.phps) -Just rename the .phps to .php in your base plog directory. This is a beta, so hopefully it won't screw you up :) Darren |
From: <pl...@so...> - 2003-10-29 20:10:56
|
Ok, there was a security bug, which Oscar found, I have updated the file, and it is available at the same location: > http://someblog.com (Take a look in the Files section on the right column > for a file called plugindocuments.class.phps) > -Just rename the .phps to .php in your base plog directory. Darren |
From: Brian M R. <bm...@ch...> - 2003-11-03 22:33:26
|
Hadn't heard anything from the list in a few days.... everything ok? Oscar: I was testing the possible length bug as brought up here: http://www.plogworld.org/forums/viewtopic.php?t=67 and I'm finding that it's not the topic, but there is a bit of a problem with the display you might wanna look at. ;) I stuffed the hell out of the Topic: field and it held up ok, even with a slightly older version of CVS (I haven't updated in at least a week...). I tried twice, once at 256 chars, once at about 200k chars and the server is still handling it, but it looks messy. ;) http://wolfwood.chipshot.net/post/1/10 |
From: Oscar R. <os...@re...> - 2003-11-06 17:25:47
|
Hi! > Hadn't heard anything from the list in a few days.... everything ok? Yes, we're all here. Tired and busy, but still alive and kicking :) Sorry for the lack of communication, but there hasn't been much going on anyway lately... > Oscar: > > I was testing the possible length bug as brought up here: > http://www.plogworld.org/forums/viewtopic.php?t=67 and I'm finding that > it's not the topic, but there is a bit of a problem with the display you > might wanna look at. ;) > > I stuffed the hell out of the Topic: field and it held up ok, even with > a slightly older version of CVS (I haven't updated in at least a > week...). I tried twice, once at 256 chars, once at about 200k chars and > the server is still handling it, but it looks messy. ;) > > http://wolfwood.chipshot.net/post/1/10 It takes my browser an eternity to render that :D (Konqueror running on my Celeron-700 laptop) The thing here is, what is the problem with that? The topic field for a comment is of type TEXT in the db, so you can stuff as many characters as you can in there... Another thing is wether there should be an option to determine how long topic/text can be. The problem with the "mess" there is the browser. For example in Konqueror, I see the page "correctly", that is, the topic is wrapped in something like countless different lines, but the text always stays within the frame. OTOH, in Firebird it stretches "ad infinitum"... And I am afraid that there's nothing we can do at the presentation level because it has much more to do with the style/browser than with the software itself. If anything, you could use a Smarty trick in the postandcomments.template file to truncate the string: {$comment->getTopic()|truncate:80} where 80 is the maximum length that the string will have. As I wrote here (http://plog.bliang.com/forums/viewtopic.php?p=288#288) we have already implemented a security subsystem for 0.3 which will take care of filtering things like that (and blocking ips, and many more things), and which is already capable of blocking comments that have a text/topic bigger than X bytes. I think that could do as a possible solution. What does everybody else think? Oscar. |
From: Brian M R. <bm...@ch...> - 2003-11-06 17:45:01
|
I'm all for limiting the length of the Topic field on comments. Makes sense to do so, since technically someone can eventually break the DB by overflowing it's disk space with useless crap. Given that we're going to be taking care of that in 0.3 do we put the temp hack in to just cut the Topic field down to size for 0.2 and then remove it with 0.3 when we have the security in place or just leave it as-is for now? Oscar Renalias wrote: >It takes my browser an eternity to render that :D (Konqueror running on my >Celeron-700 laptop) > >The thing here is, what is the problem with that? The topic field for a >comment is of type TEXT in the db, so you can stuff as many characters as you >can in there... Another thing is wether there should be an option to >determine how long topic/text can be. > >The problem with the "mess" there is the browser. For example in Konqueror, I >see the page "correctly", that is, the topic is wrapped in something like >countless different lines, but the text always stays within the frame. OTOH, >in Firebird it stretches "ad infinitum"... And I am afraid that there's >nothing we can do at the presentation level because it has much more to do >with the style/browser than with the software itself. If anything, you could >use a Smarty trick in the postandcomments.template file to truncate the >string: > >{$comment->getTopic()|truncate:80} > >where 80 is the maximum length that the string will have. > >As I wrote here (http://plog.bliang.com/forums/viewtopic.php?p=288#288) we >have already implemented a security subsystem for 0.3 which will take care of >filtering things like that (and blocking ips, and many more things), and >which is already capable of blocking comments that have a text/topic bigger >than X bytes. I think that could do as a possible solution. > >What does everybody else think? > >Oscar. > > |
From: Oscar R. <os...@re...> - 2003-11-06 18:33:57
|
Hi! > I'm all for limiting the length of the Topic field on comments. Makes > sense to do so, since technically someone can eventually break the DB by > overflowing it's disk space with useless crap. Given that we're going to > be taking care of that in 0.3 do we put the temp hack in to just cut the > Topic field down to size for 0.2 and then remove it with 0.3 when we > have the security in place or just leave it as-is for now? I could easily add some sort of "hard" limit for the length of the topic, at least in 0.2. Something like... what? 100 characters? 256 characters? Hopefully we'll improve that with 0.3 :) Oscar. > Oscar Renalias wrote: > >It takes my browser an eternity to render that :D (Konqueror running on my > >Celeron-700 laptop) > > > >The thing here is, what is the problem with that? The topic field for a > >comment is of type TEXT in the db, so you can stuff as many characters as > > you can in there... Another thing is wether there should be an option to > > determine how long topic/text can be. > > > >The problem with the "mess" there is the browser. For example in > > Konqueror, I see the page "correctly", that is, the topic is wrapped in > > something like countless different lines, but the text always stays > > within the frame. OTOH, in Firebird it stretches "ad infinitum"... And I > > am afraid that there's nothing we can do at the presentation level > > because it has much more to do with the style/browser than with the > > software itself. If anything, you could use a Smarty trick in the > > postandcomments.template file to truncate the string: > > > >{$comment->getTopic()|truncate:80} > > > >where 80 is the maximum length that the string will have. > > > >As I wrote here (http://plog.bliang.com/forums/viewtopic.php?p=288#288) we > >have already implemented a security subsystem for 0.3 which will take care > > of filtering things like that (and blocking ips, and many more things), > > and which is already capable of blocking comments that have a text/topic > > bigger than X bytes. I think that could do as a possible solution. > > > >What does everybody else think? > > > >Oscar. > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > pLog-General mailing list > pLo...@li... > https://lists.sourceforge.net/lists/listinfo/plog-general |
From: Oscar R. <os...@re...> - 2003-10-26 12:03:38
|
Hi! > > Anything you're missing from > > 0.2 and that you'd like to see implemented? > > 1. Auto making links and stuff. So I can just paste text, with http:// > links and *@yomcat.geek.nz ones without having to worry about putting in > any HTML code. <br> and <a> would be the best two tags. Then I think we should define an additional mode for editing posts, so that we would have visual editing with htmarea, plain normal text editing where the user would have to type all the html code, and a third one where newlines would be converted to <p> tags, links would be automatically converted to <a> tags and so on... Shouldn't be too difficult to implement. > 2. Better stats. I installed the package from http://htmlfixit.com/free.php > and its pretty cool. Complimenting your current one, of course. I know our stats are crappy but we never intended to get anything else other than the referers. If you need better statistics, I'd suggest the php-based package called phpOpenTracker. It's great, supports keeping track of multiple websites/pages with only one db, has daily stats, weekly stats, monthly stats, yearly stats, referer tracking, and many more: http://www.phpopentracker.de. Also, once 0.2 comes out I will release a plugin that integrates pLog and phpOpenTracker. Since pOT supports statistics for more than one site with one installation, we can keep separate statistics for different blogs, which makes it suitable for places where pLog is serving more than one blog. In the beginning I thought about integrating it in the core of pLog but after a short discussion here, it was decided that we could offer such functionality as a plugin because not everybody was interested in something like that. And I also agree. > 3. Spell Checker That's also something I've been considering but it would require of a tool such as pspell/aspeel in Linux. And don't even know if it works in Windows... We'll think about it :) > 4. Get rid of the "target=_blank thing from link tracker. That's an easy one... You can edit yourself the linktracker.template file and remove it! ;) > 5. Timezone support. At the moment I don't think we can offer support for timezones, because of the simple fact that all the dates stored in the database are in the timezone in where the db server is. In other words, the dates stored in the db are not in GMT and applying a timezone to those dates would be quite difficult. What we can do is give the user the possibility of specifying a time difference, so that the correct dates would be calculated based on that time difference. That is, if your server is in Perth and you post something at 18:30, you could tell pLog that you're 5h behind that time and pLog should then automatically substract 5h from the original date. > 6. Allow https:// links to be posted in the Links section without adding a http://. That was a bug (thanks for spotting it :)) that I have just fixed in CVS. Will be there for 0.2. If you come up with anything else, let us know! Oscar. |